--- title: "Publishing on Google Play Solo: What Changed — Survival Apps" description: "Mandatory testers, identity checks, API requirements that keep changing: what to expect today when publishing your first app on Google Play on your own." url: https://survival-apps.com/en/transmissions/004-google-play-solo-developer/ --- TRANSMISSION 004 · 28 JUN 2026 ARCHIVE: [ZONE 2 — MOBILE / ANDROID](https://survival-apps.com/en/zone-2/) · OPINION # Why publishing on Google Play has become so complicated for solo developers The Weaver — report from the city gates ![the by-now-all-too-familiar Play Store](https://survival-apps.com/assets/img/google-play-store-1400x932.webp) Fig.1 — the by-now-all-too-familiar Play Store At the city gates there's a queue that doesn't move. They no longer ask only for the toll: they want to know who you are, where you live, and they ask you to bring twelve witnesses willing to swear that your tools work. Plenty of artisans look at the queue, turn around, and go back to selling in the alleys. This report is for those who want to get in anyway. ## How it used to be, and why it won't come back For years, publishing on Google Play was the easy part: 25 dollars one-off for the developer account, an APK uploaded, a few hours of waiting. That world is gone, and the reasons aren't made up: the Play Store was flooded for years with junk apps, clones and malware, and Google reacted by raising the gates bit by bit. The problem is *who* carries the weight of those gates: big software houses walk through them with a legal department; the solo developer walks through them in the evening, after dinner, alone. ## The three main obstacles For anyone opening a personal account today and wanting to bring their first app to production, the concrete hurdles are essentially three: - **THE MANDATORY CLOSED TEST** — new personal accounts have to run the app in closed testing with a minimum number of testers (the threshold Google asks for was initially twenty, later lowered to twelve) for two consecutive weeks, before you can even ask for production access. For a software house it's routine; for a hobbyist it means recruiting friends, relatives and strangers on developer mutual-aid forums[[1]](https://survival-apps.com/en/transmissions/004-google-play-solo-developer/#nota1) - **IDENTITY VERIFICATION** — ID document, address, verified contact details; organization accounts also need a D-U-N-S number[[2]](https://survival-apps.com/en/transmissions/004-google-play-solo-developer/#nota2). Reasonable on paper, but every step is a point where your application can get stuck for weeks - **THE MOBILE API TARGET** — apps have to target a recent version of Android and stay up to date year after year, or be pulled from search or from the store. Translation: a published app is never "finished", it's a lifetime subscription to maintenance ## My take It would be easy to wrap up with "Google bad, indies good". The reality is more uncomfortable: almost every single rule, taken on its own, has a defensible justification. It's the *sum* that's hostile, because it's calibrated for people who publish for a living and lands identically on people who publish for love. The measurable result is a barrier to entry that selects not on the quality of the app, but on the ability to put up with bureaucracy. For those developing solo, the practical consequences are two. First: **the publishing process has to be designed like a feature**, with the same lead time — the fourteen days of closed testing need to go on the calendar before you've even written the last screen. Second: it's worth asking, project by project, whether the Play Store is really the only channel — between PWAs, direct APK distribution and alternative stores, the monopoly of the main gate is no longer as total as it once was. That's exactly the topic of [the next broadcast in this zone](https://survival-apps.com/en/transmissions/007-pwa-capacitor-or-native/). root@survival:~$ checklist --publish google-play > account: 25$ one-off + identity verification > closed testing: 12+ testers × 14 consecutive days > production request: after the test, with questionnaire > maintenance: API target to update every year > moral: PLAN BEFORE WRITING CODE Zone note This post opens the Zone 2 — Mobile/Android thread. When my first app actually reaches closed testing, every step of this ordeal will be documented here with dates, real timings and hiccups included — so the numbers in this post will stop being theory. ## Frequently asked questions ### What are the three main obstacles to publishing solo on Google Play? The mandatory closed test with at least twelve testers for two consecutive weeks, identity verification (ID document, address, and a D-U-N-S number for organization accounts), and the requirement to update the API target every year. ### How much does a Google Play developer account cost? 25 dollars one-off, unchanged over time — the money isn't the problem: the time required by identity verification and the closed test is. ### Are there alternatives to the Play Store for distributing an Android app? Yes: PWAs, direct APK distribution and alternative stores. The monopoly of the main channel is no longer as total as it once was — it's the topic explored in [the next broadcast](https://survival-apps.com/en/transmissions/007-pwa-capacitor-or-native/). The queue at the gates won't get any shorter. But knowing the guards' questions before you join the line is already half the journey. ### Notes 1. **Closed testing requirement** — introduced by Google for personal accounts created after November 13, 2023. The operational details (thresholds, duration, evaluation criteria) are updated by Google over time: before planning, always check the official Play Console documentation. [↑ back to text](https://survival-apps.com/en/transmissions/004-google-play-solo-developer/#ref1) 2. **D-U-N-S** — a 9-digit business identifier issued by Dun & Bradstreet, required by Google (and by Apple) to register organization-type developer accounts. Free, but the turnaround time is out of your hands. [↑ back to text](https://survival-apps.com/en/transmissions/004-google-play-solo-developer/#ref2) ## // FROM THE SAME ZONE [ TRANSMISSION 038 20 OCT 2026 ZONE 2 — MOBILE / ANDROID · APP PRESENTATION ### Item90: home supplies, room by room Do you know what's in your pantry, how long it lasts and what's about to expire? Item90 is the Android app for planning home supplies, in '90s pixel style. ](https://survival-apps.com/en/transmissions/038-item90-home-supplies/) [ TRANSMISSION 037 18 OCT 2026 ZONE 2 — MOBILE / ANDROID · DECISION GUIDE ### Offline maps: download them before the network is gone Google Maps, Organic Maps or OsmAnd? What really works without internet, what doesn't, and how to prepare your phone in ten minutes, before you need it. ](https://survival-apps.com/en/transmissions/037-offline-maps-android/) [ TRANSMISSION 034 29 SEP 2026 ZONE 2 — MOBILE / ANDROID · DECISION GUIDE ### Your phone already knows how to call for help: turn these features on Emergency SOS and emergency contacts are already built into Android and iPhone. Here's how to switch them on. ](https://survival-apps.com/en/transmissions/034-emergency-sos-already-in-your-phone/)