AI makes building an app fast. Publishing it is a different story.
I built and published an Android app, T Wala English, using AI coding tools. Building took days. Publishing took months.
Here is the real cost, the real timeline, and every wall I hit.
What It Costs to Start
- Google Play developer account: $25, paid once, no renewal.
- Apple charges $99 every year instead.
- That is why most solo developers start with Android.
After that $25, the real cost is time, not money.
The Stack I Used
- GitHub Copilot – AI coding assistant, the only paid tool.
- VS Code – free code editor.
- Expo CLI – free, makes React Native easy, updates your phone instantly.
- Expo EAS Build – free tier, builds the APK in the cloud.
- GitHub – free, stores the code and triggers builds automatically.
- Google Play Console – the $25 account, where the real work happens.
- AdMob and AdSense – both free, and you need both.
The same lean-stack approach works for no-code tools for freelancers and AI automation workflows: fewer tools, wired together well.
With this stack, building the app was fast. Publishing it was not.
The Biggest Wall: 12 Testers, 14 Days
- Personal accounts created after November 13, 2023 must run a closed test.
- You need 12 testers, opted in (installed), for 14 continuous days.
- Google lowered this from 20 testers in December 2024. Many guides still say 20.
- Organization accounts are exempt from this rule entirely.
- Do not use fake accounts to hit the number. It risks permanent account suspension.
I found 12 real testers and waited two weeks.
Legal Requirements Before You Publish
- A live privacy policy: a real URL, accurate about what data your app collects (ads and analytics count as data collection).
- Play Console declarations: data safety form, content rating, target audience, ads disclosure.
Getting these wrong is one of the most common rejection reasons.
Ads Took Longer Than Building the App
- AdMob needs AdSense too. AdMob links to AdSense for payments, so you go through two approvals, not one.
- Expo cannot preview ads. Ad code only works in a full build, tested on a real phone.
Every ad change meant: build, wait, install, check, repeat. This step took longer than everything else combined.
What Actually Helped: One Extra Developer
I hired one junior developer to work alongside me. Not a team, just one extra person.
While one build was running, the other person worked on the next fix. This cut the waiting time significantly, and helped avoid the fatigue of watching build logs alone.
Same logic as reducing manual work using AI: find the real bottleneck, then fix that specific thing.
Updates Bring the Same Two Traps
- Any change to data collection (like adding ads) means updating your data safety declaration.
- Your privacy policy must match that declaration, or you risk rejection.
Once I expected this, updates were fast: build, check, ship.
The Simple Workflow Now
Code in VS Code → push to GitHub → Expo EAS builds automatically → test on a real phone with ads live → publish via Play Console.
Next step: turn ads off in development builds and on only for production, to cut rebuild time further.
Where the App Stands Today
T Wala English is live with ads, a working UI, and a tag and revision system. Next up: a real AI feature, a proper backend, and a senior developer review before scaling.
Does AI Actually Help With Publishing an App?
Yes, but only with the build. AI did not speed up the 14-day tester wait, AdSense or AdMob approval, data safety declarations, privacy policy compliance, or ad rendering bugs.
Websites are fast end to end. Apps have a review process, a compliance layer, and a native build step that AI cannot skip.
Every Stage at a Glance
| Stage | Cost | Time | AI Help |
|---|---|---|---|
| Play Console setup | $25 one time | ~1 day | None |
| Building the app | Copilot subscription | Days | High |
| Closed testing | Free | 14 days, 12 testers | None |
| Privacy policy | Free | Half a day | Some |
| Play Console declarations | Free | A few hours per release | None |
| AdSense / AdMob approval | Free | Days to weeks | None |
| Ad implementation | Free | Longest stage | Partial |
| Second update | Free | Fast, once you know the rules | Some |
If you are starting today:
- Register as an organization account if you can. It skips the 12-tester rule.
- Get your privacy policy live early.
- Line up your 12 testers before the app is finished.
Frequently Asked Questions
How much does it cost to publish an app on the Play Store?
$25 one time. No annual renewal. Publishing itself is free.
How many testers do I need for Google Play?
12 testers, opted in for 14 continuous days, for personal accounts created after November 13, 2023. Organization accounts are exempt.
Do I need AdSense to use AdMob?
Yes. AdMob links to AdSense for payments, so you go through two approvals.
Can I test AdMob ads in Expo Go?
No. You need a full build installed on a real device to see ads render.
Can I publish an app without coding experience?
Building is achievable with AI help. Publishing still requires understanding privacy policy and data safety rules.
How long does it take to publish an app solo?
Building can take days. Budget four to eight weeks end to end, including the 14-day test period, review cycles, and ad approvals.
Final Thoughts
AI changed what a solo developer can build. It has not changed what a solo developer has to survive to ship.
I write about the systems behind this kind of work, including using AI for business growth. Building an app solo right now? Tell me which stage you are stuck on in the comments.