Privacy-first app publishing service for solo Android devs
Problem
Google Play requires paid-app developers to expose their full legal name and home address publicly, which is unacceptable for hobbyists and students who don't have a company or a mail-forwarding address. Solo devs either give up publishing paid apps or accept doxxing risk; workarounds (incorporating, finding a publisher) are costly or ad-hoc.
Opportunity
A productized service that gives indie Android developers a legitimate privacy shield: registered business address, Play Store publisher entity, and payment routing, at a price accessible to hobbyists shipping their first paid app.
Market analysis
The pain is real, chronic and well-documented: Google has publicly displayed paid developers' legal names and home addresses since 2014, HN threads recur on it, and Google explicitly rejects PO boxes and virtual offices for personal accounts. The real solution is an organization account backed by a real entity, which is exactly what formation services (Doola, Firstbase) already sell to non-US founders. A productized 'Play publisher privacy pack' would mostly be curation and Play-Console-specific hand-holding on top of commodity incorporation, plus payment routing under the org profile.
Market · Hobbyist and student Android developers (and iOS devs facing similar transparency rules) without a company; recurring demand signal on HN, XDA and r/androiddev threads going back a decade.
Pricing · Formation comparables: Doola and Firstbase run roughly $300-400/yr subscriptions, US registered agent add-ons around $125-150/yr, New Mexico LLC about $50 filing with $0 annual fees. A curated solo-dev pack at $150-300/yr fits hobbyist wallets; one-time setup fee plus compliance renewal is the natural shape.
Pros
- + Sharp, identifiable audience reachable in a few subreddits and HN threads; chronic recurring pain.
- + Parts already exist (registered agent, virtual mailbox, org account guidance), so the MVP is curation plus docs.
- + Recurring compliance revenue, not a one-off tool sale.
- + Trust business: once a dev routes payments through you, switching cost is high.
Cons
- − Heavy compliance surface: KYC/AML, payments handling, tax reporting across many jurisdictions.
- − You insert yourself into the dev's revenue stream, which raises liability if payouts or disputes go wrong.
- − Doola/Firstbase/Northwest could add a 'Play Store privacy' landing page overnight; no technical moat.
- − Google may tighten verification (D-U-N-S matching already required for orgs), shifting the rules under you.
Existing / similar tools
Source
Hacker News (Ask HN)
Read the opportunity carefully before building: the defensible version is not another LLC factory, it is becoming the publisher of record. That means you operate the Play Console org account, handle Google’s D-U-N-S and payments-profile verification once, and rent developer slots under it, which is legally closer to a game-publisher model than to a SaaS. That concentrates real responsibility (one policy strike can take down every client app), so the honest MVP is the narrower pack: entity formation plus registered agent plus a verified step-by-step org-account migration guide, sold at a flat hobbyist price. Payment routing, the riskiest piece, should come only after the funnel proves people will pay for the shield at all.