Fewer than 1 in 54 Apple developers has shipped an app. What stops the rest
The blockers are fees, review rules, testing and upkeep, not writing the code.
Fewer than 1 in 54 registered Apple developers has ever shipped an app. Much of what stands between code and a store listing comes after the code: accounts, fees, review rules, testing periods and the work of keeping an app alive.
We think about this number a lot, because AI has made the first part, building, much easier. It hasn't touched the rest. Here is what the rest actually looks like, as of November 2026.
The account comes before the app
To publish on iPhone you join the Apple Developer Program, which costs $99 a year (Apple). That fee is yearly, not one-time.
If you publish as a company rather than as yourself, enrollment has its own requirements (Apple):
None of this is hard, but each step is a reason to put the project down.
Google Play is a one-time $25 (Google). Identity checks can ask for a government ID and a credit card, and prepaid cards aren't accepted.
Review rejects apps that "work"
The App Store doesn't only check that your app runs. It checks that it deserves to be there. As of the guidelines last updated October 16, 2026 (App Review Guidelines):
For a first-time builder, 4.2 is the painful one. The app you made for yourself, a simple tracker or a calculator for your shop, may be exactly what you need and still read to a reviewer as too thin for the store.
4.2.6 matters more as more apps are built with AI tools: the guideline puts the responsibility on whoever owns the content to submit it.
Android has a waiting room
Google Play's registration rules add a process step instead. Personal developer accounts created after November 13, 2023 must run a closed test with at least 12 testers, opted in for 14 consecutive days, before they get production access (Google).
Twelve testers is easy for a company and hard for one person with a niche app. Two weeks is long enough for the motivation that got you this far to fade.
Shipping is the start of the bill
The steps above are the ones people see. The quieter blocker is maintenance:
For a product with users and revenue, that's normal work. For a personal tool, it's a permanent chore attached to an app you wanted to stop thinking about. We wrote about the same pattern on the AI side in Where AI-built apps get stuck: about 95% of Replit apps never reached production.
What this taught us
We read the 1-in-54 figure as a warning about the gap between "it runs on my machine" and "it's live." Three things in Leanfinit's beta answer it.
Publish to the web first. During the beta, the Publish button puts your app live on the web. There's no store account to create, no fee and no review queue before you can use it. Since iOS 26, a site added to the iPhone Home Screen opens as a web app by default (WebKit), so for many personal apps the web is enough.
Don't submit for you. During the beta we don't submit apps to the App Store or Google Play. That also matches what Guideline 4.2.6 asks: the person or business that owns the app's content submits it.
Keep the way out open. Code export is available, and the app is built on Flutter, which targets iOS and Android, for when a store listing is really needed. If you're building for a client, read whose accounts should publish client apps before you start.
Do you need the store at all?
Ask one question before you open a developer account: does anyone need to find this app, or do they only need to use it?
If it's for you, your household or your team, a link and a Home Screen icon do the job without the fee, the review or the waiting room. Our guide Web, PWA or App Store walks through that decision. If you don't have a Mac, no-code iOS app builders without a Mac covers the options.
If strangers need to discover it, the store is worth it. Go in knowing the steps above, and plan for the account, the review and the upkeep before you plan the launch.
Build the first version and put it on the web: studio.leanfinit.com.