IdeaWell

Project ideas from Hacker News discussions.

Play Store blocks AuroraStore, hurting GrapheneOS users

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Google is blocking Aurora Store by flagging its burner accounts

“AuroraStore uses a pool of burner Google Play Store accounts to facilitate anonymous downloads. This is what happens when those burner accounts get flagged.” – iAMkenough

GrapheneOS officially advises against Aurora Store, favoring the sandboxed Play Store

“GrapheneOS actually recommends against using Aurora and instead just using the Play Store, so this shouldn't really hurt users.” – pyrophane

Privacy‑seekers clash with the difficulty of obtaining a truly anonymous Google account

“Isn't that pretty much impossible? You need a phone number for verification, which effectively ties it to that phone number.” – joekrill

Users resort to workarounds and alternative app sources to avoid Google tracking

“You could suck it up and do the phone number verification, it usually costs around $5 for a phone number… Or you could go through the android phone sign‑up process which doesn't require one. Buy a cheap android phone and keep resetting it and making a new account each time.” – megagpt2

🚀 Project Ideas

Aurora Mirror Proxy

Summary

  • A lightweight caching service that pre‑fetches and mirrors popular APKs from the Play Store, reducing reliance on shared anonymous Aurora accounts and mitigating “Server busy” errors.
  • Core value: faster, reliable app installs for privacy‑focused users without needing a Google account.

Details

Key Value
Target Audience GrapheneOS, CalyxOS, and other de‑Googled Android users who rely on Aurora Store for Play Store apps
Core Feature Automated mirroring of top‑N Play Store apps (based on download stats) served via a CDN; fallback to Aurora when mirror unavailable
Tech Stack Go (or Python) for mirror worker, Redis for queue, Nginx/Caddy as reverse proxy, Docker for deployment
Difficulty Medium
Monetization Hobby

Notes

  • HN user everyday7732 suggested: “If it's rate limits, I wonder if Aurora Store could just download and mirror the apk for the top 40 most popular apps … and serve that mirror.” This directly implements that idea.
  • Provides a concrete mitigation for the rate‑limit/account‑sharing problem while preserving Aurora’s anonymity model.

Play Integrity Verifier

Summary

  • A client‑side tool that downloads APKs from the Play Store using a temporary anonymous token, validates the developer signature, and stores a trusted checksum for offline or Aurora‑free installation.
  • Core value: lets users verify that an APK obtained via Aurora (or any source) is genuine, addressing trust concerns around sideloaded apps.

Details

Key Value
Target Audience Privacy‑conscious Android users who want to install Play Store apps without trusting third‑party stores
Core Feature One‑click verification: fetch APK → check Play Store signature → cache SHA256 → allow install via any file manager
Tech Stack Kotlin/Android app, SafetyNet/Play Integrity API (via sandboxed Google Play), BouncyCastle for signature verification, Room DB for cache
Difficulty Medium
Monetization Hobby

Notes

  • Commenters expressed distrust: “I don't, and I really wish there would be a decent way to verify that the installed/provided apps are legit.” (Flip‑per) and discussion of signing keys.
  • Gives users a practical way to achieve the same trust level as the Play Store while staying within a de‑Googled ecosystem.

Burner Account‑as‑a‑Service

Summary

  • A hosted service that creates short‑lived Google accounts using virtual phone numbers (or SIM‑less registration tricks) and provides the credentials via a secure API or QR code for Aurora Store login.
  • Core value: eliminates the manual hassle of obtaining burner SIMs and dealing with phone‑number verification hurdles.

Details

Key Value
Target Audience Aurora Store users who need anonymous Google accounts but find the burner‑SIM process cumbersome (e.g., Linux‑Fan, armadyl)
Core Feature On‑demand account generation, automatic 2FA backup code delivery, optional auto‑renewal, and revocation after use
Tech Stack Node.js/Python backend, Twilio or similar virtual‑number API, Firebase Auth for account creation, Redis for state, HTTPS API
Difficulty High (due to reliance on external SMS providers and Google’s anti‑abuse measures)
Monetization Revenue‑ready: Subscription ($2/month) or pay‑per‑account ($0.10)

Notes

  • Thread highlights the difficulty: “You need a phone number for verification, which effectively ties it to that phone number.” (Linux‑Fan) and the desire for a Google Account “that isn’t tied to anything else.”
  • Provides a streamlined, privacy‑respecting way to keep Aurora functional without manual SIM management.

Unified Alternative App Store Frontend

Summary

  • An aggregator UI that combines Accrescent, Obtainium, Zapstore, F‑roid (via Neo Store), and Aurora mirrors into a single browse/search experience with intelligent fallback and update notifications.
  • Core value: reduces fragmentation, giving users a “one‑stop shop” for de‑Googled apps while leveraging the strengths of each source.

Details

Key Value
Target Audience Android enthusiasts on GrapheneOS, LineageOS, /e/OS, etc., who currently juggle multiple app stores
Core Feature Unified catalog, smart source ranking (official > verified > mirror), background update checks, one‑tap install
Tech Stack Flutter (cross‑platform) or React Native, GraphQL gateway merging APIs from each store, local DB for caching, Firebase Cloud Messaging for update alerts
Difficulty Medium
Monetization Hobby

Notes

  • Users lament F‑roid UX (“shitshow”, xingped) and praise alternatives like Obtainium, Aurora, Zapstore (cyberrock). A unified front‑end would address those pain points.
  • Encourages discussion about app‑store diversity and could become a hub for new decentralized distribution ideas.

Read Later