So you built an app. Now you want real people to download it. Here’s the good news: publishing an app on Google Play store is not hard once you know the steps.
In short, you need a verified developer account, a properly built app, a store listing, a few required forms, and (for some accounts) a short testing period. Then Google reviews your app and it goes live.
Two things are different in 2026, though. First, new apps must now meet a stricter technical rule called API level 36 (Android 16). Second, Google added a brand-new identity check called Android Developer Verification. We’ll explain both in plain language below.
Can you publish an app on Google Play?
Yes, if you meet Google’s rules. Almost anyone can publish an app. But “can I publish” and “will my app get approved” are two different questions.
To publish, you need:
- A verified Google Play developer account
- An app that works and follows Google’s policies
- A complete store listing
- Some required forms filled in correctly
- Testing, if your account needs it
Meeting these doesn’t guarantee approval. Google still reviews your app before it goes live. But if you follow this guide, you’ll avoid the mistakes that cause most delays.
What you need before you start
Don’t open Play Console empty-handed. Here’s your shopping list. Some items apply to everyone. Others only apply to certain apps or account types; we’ve marked those.
| What you need | Why | Who needs it |
|---|---|---|
| Google account | To sign in | Everyone |
| Play developer account | To publish at all | Everyone |
| Identity verification | Google checks who you are | Everyone |
| $25 registration fee | One-time cost to register | Everyone |
| Android App Bundle (AAB) | The file format Google Play uses | Everyone |
| Current target API level | Your app must be built for a recent Android version | Everyone |
| App icon, screenshots, description | For your store listing | Everyone |
| Privacy policy | Explains what data you collect | Apps that collect data (almost all) |
| Data Safety form | Declares your data practices | Everyone |
| Content rating | Tells users if it’s age-appropriate | Everyone |
| Demo login details | Lets Google’s reviewer test locked features | Apps with a login |
| 12 testers for 14 days | A testing rule for some accounts | New personal accounts only |
Play Console walks you through most of this step by step once you create your app. But it helps to have everything ready before you start, so you’re not scrambling mid-setup.
How much does it cost to publish an app on Google Play?
Publishing itself costs a one-time $25 registration fee. That’s it for getting your account set up. Once you’re registered, you can publish as many apps as you like (free or paid) at no extra listing cost.
But there’s a second kind of cost people confuse with this: service fees. These only apply if you sell something inside your app, like a subscription or in-app purchase. Google doesn’t charge these fees just for having an app listed.
As of 2026, Google’s service fees work like this:
| Revenue type | Fee |
|---|---|
| First $1 million per year | 15% |
| Above $1 million per year | 30% |
| Subscriptions | Dropping to 10% by mid-2026 |
| Billing fee (US, UK, EEA) | 5%, if you use Google Play’s billing system |
So the honest, current answer is: $25 to register, plus a percentage of sales if you charge for anything. Google’s fee programs and eligible reduced rates are rolled out by region, so it’s worth checking your market inside Play Console before you price anything.
Can you publish for free? Not entirely. The $25 fee is required for a standard developer account. But if you only want to test an app on a handful of devices, Google now offers a free, limited option capped at 20 devices, aimed at students and hobbyists. More on that in the Android Developer Verification section below.
Personal vs Organization developer account
You’ll be asked to choose one of two account types. Here’s the difference.
Personal account
- Best for solo developers and side projects
- You verify with a government-issued ID
- Your personal name shows as the developer, unless you add a business name later
- If your account was made after November 13, 2023, you must complete a testing requirement before you can publish to production (more below)
Organization account
- Best for registered businesses
- Requires a D-U-N-S number (a business ID number) and company documents
- Your company name shows as the developer
- No 12-tester testing requirement
Which one do you need?
Google requires an organization account for certain app categories, including:
- Financial products and services
- Cryptocurrency wallets or exchanges
- Health apps
- VPN apps
- Government apps
If your app falls into one of these, don’t try to publish it under a personal account; you’ll hit a wall later.
How to create a Google Play developer account
- Sign in with the Google account you want to use for publishing.
- Choose your account type: Personal or Organization.
- Fill in your developer details: name, contact info, and address.
- Verify your identity: Personal accounts need a government ID. Organization accounts need a D-U-N-S number and business documents.
- Pay the $25 fee.
- Complete any extra verification steps Google asks for.
- Access Play Console once approved.
Verification usually takes a day or two, but it can take longer, so don’t leave this to the last minute.
Prepare your Android app before uploading it
Build an Android App Bundle (AAB)
An Android App Bundle (AAB) is the file format Google Play uses to publish your app. It’s not the same as the old APK format.
Here’s the simple version: an AAB isn’t a finished, installable app. It’s more like a blueprint. Google’s servers use it to build a smaller, optimized version of your app for each user’s specific phone. That means faster downloads and better performance for your users, and less work for you.
APKs still exist, but Google Play no longer accepts them for new app submissions. You need an AAB.
Meet the 2026 target API requirement
This is one of the most important (and most missed) technical rules right now.
As of August 31, 2026, new apps and app updates for phones and tablets must target Android 16 (API level 36) or higher. If your app targets an older API level, Google Play will block your upload.
A few exceptions, if your app is a different type:
| App type | Minimum API required |
|---|---|
| Phones, tablets, foldables | API 36 (Android 16) |
| Wear OS | API 35 (Android 15) |
| Android Automotive | API 35 (Android 15) |
| Android TV | API 34 (Android 14) |
| Android XR | API 34 (Android 14) |
One more thing worth knowing: this rule doesn’t just block brand-new apps. If you have an existing app and try to push a small update, Google Play will reject the update too if your target API is out of date. Check this before you try to ship your next release, even for an app that’s already live.
Set up Play App Signing
Every app needs to be signed with a security key before Google will accept it. This proves the update really came from you.
Google can manage this key for you automatically through Play App Signing; and for most developers, that’s the easier choice. If you manage your own signing key instead, keep a safe backup. Lose it, and you could lose the ability to update your app in the future.
Test the app before you submit it
Don’t skip this. Before uploading, check:
- It works on more than one real device, not just an emulator
- Core features don’t crash
- Login and signup flows work properly
- Permissions only ask for what the app actually uses
- The app works with a normal internet connection, not just Wi-Fi in your office
Google’s own Pre-launch Report inside Play Console will also test your build automatically and flag issues before a human ever reviews it.
Create your Google Play store listing
Your store listing is what convinces someone to tap “Install.” Here’s what goes into it.
| Field | Limit | Tip |
|---|---|---|
| App name | 30 characters | Clear and memorable beats clever |
| Short description | 80 characters | Lead with the main benefit |
| Full description | 4,000 characters | Explain what the app does, plainly |
| App icon | 512×512px PNG | No transparent background |
| Screenshots | At least 2, sized per device | Show real screens, not mockups only |
| Feature graphic | 1024×500px | Keep important info away from the edges |
| Category & tags | Up to 5 tags | Pick what’s actually accurate |
| Support email | Required | Users and reviewers will see this |
A quick warning: don’t promise features your app doesn’t have, and don’t stuff keywords into your description. Google checks this, and it’s a common rejection reason.
Complete Google Play’s app content requirements
Before you submit, Google asks you to fill in a set of forms about your app. Here’s what each one actually does.
Data Safety form: You declare what data your app collects and why. This needs to match what your app actually does, including data collected by third-party tools like analytics or ad SDKs.
Privacy policy: A working, public link explaining your data practices. Required for almost every app.
Content rating: A short questionnaire that assigns your app an age rating.
Target audience: Tells Google who your app is built for, which affects what rules apply to you.
App access / demo login: If your app requires a login, give the reviewer working test credentials. Otherwise, they can’t review your app properly.
Other declarations that may apply, depending on your app:
- Ads
- Financial services
- Health features
- VPN functionality
- AI-generated content
Not every app needs every declaration. Only fill in what applies to yours.
The 12-testers, 14-day closed testing rule
This one confuses a lot of new developers, so let’s break it down clearly.
Who needs to do this?
Only personal accounts created after November 13, 2023. If you have an organization account, or a personal account from before that date, you can skip this section.
What’s the actual rule?
You need at least 12 testers, opted into a closed test, for 14 continuous days, before Google will unlock production access. This is not optional and cannot be skipped.
What does “14 continuous days” mean?
It means your 12 testers need to stay opted in the whole time. If someone drops out partway through, it can affect whether your test period counts. Keep an eye on your tester list, not just the calendar.
Testing tracks, explained
| Track | Purpose | Who sees it |
|---|---|---|
| Internal | Fast early testing | A small trusted group |
| Closed | Your official pre-launch test | Testers you choose |
| Open | Broader public test | Anyone who opts in |
| Production | The real launch | Everyone on Google Play |
After the 14 days
You apply for production access. Google reviews your app, your testing activity, and your store listing before unlocking full publishing.
How to avoid this slowing your launch
- Line up testers early. Don’t wait until your app is finished
- Aim for a few more than 12, in case someone drops out
- Give testers a clear, simple way to install and give feedback
- Track who’s actually opted in, not just who you invited
How to submit your app to Google Play
Once everything above is ready, here’s the actual submission process:
- Finish setting up your app in Play Console.
- Upload your signed AAB.
- Complete your store listing.
- Fill in all required declarations.
- Choose your release track (internal, closed, open, or production).
- Fix any warnings or errors Play Console flags.
- Submit and roll out your release.
- Monitor your app’s status in Play Console.
How long does Google Play take to approve an app?
There’s no single guaranteed number, but here’s a realistic breakdown.
| Stage | What happens | Can it delay you? |
|---|---|---|
| Account verification | Google checks your identity | Yes |
| App preparation | Build, listing, forms | Yes |
| Closed testing | 14 days, if it applies to you | Yes |
| Production access review | Google checks your test results | Yes |
| App review | Google checks your submission | Yes |
| Publication | Your app goes live | Sometimes |
Most standard reviews finish within a few days, but Google notes that some reviews can take up to seven days, and occasionally longer in specific cases. Build in a buffer. Don’t announce a launch date the same week you plan to submit.
Why Google Play apps get rejected
Here’s what to check if your app comes back rejected; or better, before you submit at all.
| Problem | What to check |
|---|---|
| Privacy policy broken | Does the link actually load? |
| Data Safety mismatch | Does the form match what your app really collects? |
| Login doesn’t work for reviewers | Give working demo credentials |
| Target API too old | Confirm you’re meeting the current requirement |
| App crashes | Test on real devices, not just an emulator |
| Misleading listing | Do your screenshots and description match the real app? |
| Missing declaration | Did you complete every required form? |
| Testing incomplete | Did you finish the 14-day period, if it applies? |
| Policy violation | Read the specific policy Google cited |
Google tells you exactly what triggered a rejection inside Play Console. Read that message carefully before you change anything. Guessing wastes time.
How to fix a rejected app
- Read the exact reason Google gave you.
- Find the part of your app or listing it applies to.
- Fix that specific issue.
- Test the fix.
- Update any related forms or declarations.
- Resubmit.
- If you genuinely believe the rejection was a mistake, you can appeal; but only do this when you’re sure, not as a first response.
Do you need Play Integrity API to publish an app?
No. Play Integrity API is a security tool, not a publishing requirement. It helps protect your app from tampering and fraud, but Google doesn’t force every developer to use it to get published.
That said, if you’re building anything involving payments, logins, or sensitive user data, it’s worth adding; especially since Google is expanding how much it relies on integrity signals for trust and safety checks.
What is Android Developer Verification in 2026?
This is genuinely new, and separate from everything above, so it deserves its own section.
What it actually is
Android Developer Verification checks who a developer is, not what their app does. It’s an identity check, similar in spirit to the ID verification you already do for Play Console, but it works at the operating system level across all of Android, not just Google Play.
When it starts
Enforcement begins September 30, 2026, starting in four countries: Brazil, Indonesia, Singapore, and Thailand. It covers apps installed from seven major app stores, including Google Play, Samsung’s Galaxy Store, and others. A wider global rollout is planned for 2027 and beyond.
Do you need to do anything?
If you already publish on Google Play, probably not much. Google says it auto-registered the vast majority of existing Play apps and developers back in March 2026, using information already on file. You can check your status from your Play Console home page.
If you distribute apps outside Google Play (sideloading, third-party stores, or direct APK downloads) you’ll need to register separately through the Android Developer Console, a different platform from Play Console.
There’s also a free option now: a Limited Distribution account, capped at 20 devices, aimed at students and hobbyists who just want to share an app without paying the $25 fee or submitting a government ID.
Is this the same as the Play Console $25 fee?
No. They’re related but separate. The $25 Play Console fee registers you as a Play developer. Android Developer Verification registers your identity and app package names at the Android OS level, which matters even if you never touch Google Play at all.
What to do now
- Check your verification status inside Play Console
- Confirm your app’s package names are registered
- If you distribute outside Google Play, sign up for the Android Developer Console
Can you publish an AI-built or no-code app on Google Play?
Yes. Google Play doesn’t care how you built your app… with code, no-code tools, or an AI app builder. It cares whether the finished app meets its requirements.
That means you still need:
- A signed AAB
- The current target API level
- A complete store listing
- Data Safety and privacy declarations
- Testing, if your account requires it
Tools like FlutterFlow, Adalo, and newer AI-based app builders can generate your build for you, which removes a lot of the technical setup. But you’re still the one submitting it, and you’re still responsible for meeting every publishing requirement above.
If your app itself generates content using AI; say, AI-written text or AI images shown to users; you may also need to complete Google’s AI-generated content disclosure. That requirement depends on what your app does, not how it was built.
What happens after your app is published?
Publishing isn’t the finish line. Here’s what to keep an eye on:
- Confirm your release actually rolled out the way you configured it
- Watch for crash reports and negative reviews early
- Respond to reviews, especially negative ones. It signals you’re actively maintaining the app
- Track installs and uninstalls
- Fix policy issues quickly if Google flags any
- Keep your target API level current as Android updates each year
How to update an app already on Google Play
- Make your changes.
- Increase your app’s version number.
- Build a new signed AAB.
- Upload it as a new release.
- Test it properly, not just quickly.
- Choose a rollout method; full release or staged.
- Submit for review.
- Monitor how the rollout goes.
What’s a staged rollout? Instead of releasing an update to 100% of users at once, you release it to a small percentage first (often 1–5%) so you can catch problems before they affect everyone.
Google Play publishing changes to know in 2026
Quick summary of what’s actually new this year, so you’re not caught off guard.
- API 36 (Android 16) is now required for new apps and updates on phones and tablets, effective August 31, 2026.
- Android Developer Verification enforcement begins September 30, 2026 in four countries, with global rollout planned for 2027.
- Service fees now scale by revenue tier (15% under $1M, 30% above), with subscription fees dropping toward 10%, and reduced rates available through Google’s quality-based developer programs.
- AI-generated content now needs disclosure if your app produces user-facing AI content.
Publishing checklist
Save this and work through it before you hit submit.
- [ ] Correct developer account type chosen
- [ ] Identity verification completed
- [ ] $25 registration fee paid
- [ ] AAB built and ready
- [ ] App signed (or Play App Signing enabled)
- [ ] Target API level meets the current requirement
- [ ] App tested on real devices
- [ ] Store listing complete (title, description, screenshots, icon)
- [ ] Privacy policy live and working
- [ ] Data Safety form completed accurately
- [ ] Content rating completed
- [ ] Target audience set
- [ ] Demo login provided, if needed
- [ ] Other required declarations completed
- [ ] Closed testing finished, if it applies to your account
- [ ] Production access obtained, if needed
- [ ] All Play Console warnings resolved
- [ ] App submitted
Building for users beyond your home market?
If your app is going to have users or paying customers outside your own country, you’ll eventually run into the same problem a lot of founders hit: getting paid, and paying for tools, across borders isn’t always simple. That’s the exact problem EverTry’s global accounts and virtual dollar cards are built to solve, so revenue from your app doesn’t get stuck in currency or banking friction on its way to you.
Frequently asked questions
How much does it cost to publish an app on Google Play?
It costs a one-time $25 registration fee to create your developer account. After that, publishing apps whether free or paid; costs nothing extra. If you sell in-app purchases or subscriptions, Google takes a percentage of that revenue separately.
Can I publish an app on Google Play for free?
Not entirely. You still need to pay the $25 registration fee to get a standard account. Google does offer a free, limited testing option capped at 20 devices for students and hobbyists, but it’s not for a full public launch.
How long does Google Play take to approve an app?
Most standard reviews finish within a few days, though Google notes some can take up to seven days or longer. Add extra time if your account needs the 14-day testing period first.
Do I need 12 testers to publish an app on Google Play?
Only if your personal developer account was created after November 13, 2023. Organization accounts and older personal accounts don’t need this step.
What is the 14-day Google Play testing requirement?
It’s a closed test with at least 12 testers, opted in continuously for 14 days, required before certain personal accounts can access production publishing. It cannot be skipped or shortened.
What API level does Google Play require in 2026?
New apps and updates for phones and tablets must target API level 36 (Android 16) as of August 31, 2026. Other device types, like Wear OS and Android TV, have slightly different minimums.
What file do I upload to Google Play?
An Android App Bundle (AAB). Google Play no longer accepts APK files for new app submissions.
Do I need a D-U-N-S number to publish an app?
Only if you’re publishing under an organization account. Personal accounts verify with a government ID instead.
What’s the difference between a personal and organization developer account?
A personal account uses your own identity and is faster to set up, but requires the 12-tester testing rule for newer accounts. An organization account uses a business identity and skips that testing requirement, but takes longer to verify.
Why was my Google Play app rejected?
Common reasons include a broken privacy policy link, a Data Safety form that doesn’t match your app’s real data use, an outdated target API level, crashes during review, or a store listing that doesn’t match the actual app.
Can I update my app after publishing?
Yes. You increase your version number, build a new signed AAB, and submit it as a new release, following the same review process as your first launch.
Can I change my Google Play store listing after publishing?
Yes, at any time. You can update your description, screenshots, icon, and other listing details without submitting a new app version.
Do I need Android Developer Verification?
If you already publish through Google Play, you were most likely auto-registered in March 2026. If you distribute apps outside Google Play, you’ll need to register separately through the Android Developer Console before enforcement begins.
Can I publish an AI-built app on Google Play?
Yes. Google Play judges the finished app against its requirements, not the tool you used to build it. You still need a proper AAB, current target API, and complete store listing and declarations.
Do I need Play Integrity API to publish an app?
No, it’s not a requirement to get published. It’s a security feature worth adding if your app handles sensitive data, logins, or payments.
Final Word
Publishing an app on Google Play Store is only half the job. Once real users start signing up, paying, and using your app from different countries, you’ll run into the next challenge: moving money across borders without losing time or margin to fees and failed transactions. That’s exactly where EverTry comes in.
With EverTry, you get global accounts, virtual dollar cards, and stablecoin wallets built for developers, freelancers, and founders serving users across the Global South; so getting paid is as smooth as getting approved. Publish your app today, and let EverTry handle what happens before and after
Deborah Giwa is a Marketing Associate at EverTry, where she works on content and growth initiatives focused on helping users navigate international payments. She is passionate about simplifying access to global financial tools for people in emerging markets through clear, practical, and user-focused content.