Skipping Google Play on Purpose

Twelve testers and fourteen days of closed testing before a public listing is a real cost for a one-person hobby app. Photo Sweep skips Google Play deliberately, not by neglect.

Skipping Google Play on Purpose

Photo Sweep isn't on Google Play, and it isn't there because of a decision, not an oversight. It's worth writing down the reasoning, because "just publish it on Play too" is the single most common suggestion for any Android app, and the answer isn't laziness — it's that the specific requirement Play imposes on new apps doesn't fit how this one is built.

Twelve testers, fourteen days, for a hobby project maintained alone
Twelve testers, fourteen days, for a hobby project maintained alone

Days versus a checklist — the same launch, two very different entry costs.

The requirement in question

Before a new app can reach a public listing on Google Play, it has to go through closed testing: a minimum of fourteen days, with at least twelve testers who actually install and use it. That's not a formality that can be satisfied by uploading the APK and waiting — it requires recruiting real people, keeping them engaged for two weeks, and only then submitting for review, with no guarantee the review passes cleanly at the end of that wait.

For a company shipping a product with a marketing budget and a user base to draw testers from, that's a manageable, even useful, quality gate. For a one-person hobby project shipping evenings and weekends, it's a genuine structural cost: finding twelve willing testers for an unfinished build of a photo-deletion tool is not a small ask, and the fourteen days run on a clock that doesn't care how much other work is queued up behind it.

What F-Droid asks for instead

The contrast is sharp. F-Droid's process — covered in more detail in its own post — is an issue with a checklist and a wait measured in volunteer review time, not a mandatory testing period with a headcount requirement. It's slower in the sense that there's no fixed timeline, but it doesn't demand recruiting an audience before the app can be listed at all. Distribution outside either store — a signed APK on GitHub Releases — has no gate whatsoever.

Both of those paths were already part of the plan. Google Play would have been additive distribution, not the primary channel, which made the fourteen-day cost harder to justify: it isn't buying access to users who couldn't otherwise find the app.

Why this isn't "avoiding Google" as a principle

It would be easy to frame this as an ideological stance — self-hosted app, therefore skip the corporate app store on principle. That's not the actual reasoning, and stating it that way would be dishonest. The AGPL license, the absence of Google Play Services and Firebase, and the permission set CI enforces are all decisions made independently of whether the app ends up on Play. Nothing about Photo Sweep's architecture is incompatible with Play distribution.

The decision not to submit is narrower and more mundane: the specific cost of closed testing — recruiting and retaining twelve testers for two weeks — isn't worth paying for a channel this app doesn't structurally need, given that F-Droid and a direct APK already cover the intended audience.

Revisit only if there's a reason to

That's the whole policy, stated as plainly as it was written in the working notes. Not "never," not "eventually" on any particular schedule — just: nothing currently justifies the fourteen-day, twelve-tester cost, so it stays off the list until something does. If Play distribution ever becomes necessary — a partnership, a user base that specifically needs it, anything concrete — the requirement doesn't change, but the calculation might.

Series: Launching Photo Sweep.