Tattoo Artist BooksTo publish an app on Google Play you first create a Google Play Console developer account, which has a one-time registration fee. At the time of writing (November 2026) it is 25 US dollars with no yearly renewal. Check the official Play Console help pages before you pay, because fees and rules can change.
What is the Google Play Console?
The Google Play Console is the dashboard where you upload your Android app, build the store listing, manage releases and read reviews, crash reports and install statistics. It is the only way to put an app on the Play Store. You open the account once and can publish as many apps as you like under it.
Google Play developer fee and commission
| Item | General picture as of November 2026 |
|---|---|
| Developer registration fee | One time, 25 US dollars |
| Free apps | No commission |
| Paid downloads and in-app purchases | 15 percent on the first 1 million US dollars per year, 30 percent above |
| Subscriptions | Generally 15 percent |
Commission policies change and vary by region. Check Google's service fee page. The table is a rough frame for planning, not an accounting reference.
Requirements to release an app on the Play Store
- Identity verification. Google verifies the developer's identity and contact details. Organization accounts typically need a D-U-N-S number.
- App Bundle (AAB). New apps are uploaded as Android App Bundles.
- Target API level. Google requires apps to target a recent Android version and raises that bar yearly.
- Store listing. Title, short description (80 characters), full description, icon, screenshots.
- Privacy policy and Data safety form. You declare which data you collect.
- Content rating questionnaire and target audience declaration. Apps for children carry extra rules.
- Testing requirement. For newly created personal accounts, Google has required a closed test with a minimum number of testers over a minimum number of days before production. The numbers have changed before, so check the current rule in the Play Console.
The release steps
Roughly: open and verify the account, create the app in the Console, fill in the listing and forms, test it on the internal or closed track, create a production release and send it for review. Review time varies and the first app often takes longer, so do not squeeze your launch date.
After launch, updates follow the same route. Technical quality signals such as crash rate and slowness (Android vitals) can affect your visibility, so think about them together with app store optimization.
Test tracks and staged rollouts
The Console has four tracks: internal testing, closed testing, open testing and production. Internal testing is for quick checks inside your team and is available minutes after upload. Closed testing is a trial with a chosen group of people, and it is the step that new personal accounts must complete. On production you can use a staged rollout: release the new version to a small percentage of users first, and increase the share if nothing breaks. It is the safest way to catch a crashing release before everyone gets it.
Android-specific practical notes
- Signing keys. With Play App Signing Google keeps the app signing key safe, but still back up your upload key.
- Device variety. Android covers many screen sizes, chips and OS versions. Test on real devices with different aspect ratios.
- Version codes. Each upload needs a higher version code than the last; a duplicate is rejected.
- Policy emails. Watch for policy notices by email. A missed warning can turn into a removal. Typical triggers are in app store rejection reasons.
Get ready before you start
Keep these at hand: a Google account, a payment card, an ID document, for companies the legal name and D-U-N-S number, and a public web address for your privacy policy. The Console also asks for a developer name and contact email that users will see, so use a shared support address rather than a personal one. If a development team builds your app, decide in writing who is invited with which role: keep the admin role yourself and give developers only the release and testing permissions. That way you keep control of the app even if the team changes.
iOS and Android together
The two stores differ: Apple charges yearly, Google once. Apple review tends to be stricter and more manual, Google more automated, but policy violations can have account-level consequences. Shipping both from one codebase lowers cost; see iOS vs Android app development. The Apple side is covered in App Store fees for developers.
Frequently asked questions
Is it free to publish on Google Play?
No, but the fee is one time: 25 US dollars as of November 2026. Verify on the official page. There is no extra fee per app.
Can I open a Play Console account as an individual?
Yes. Individual and organization accounts exist. Personal accounts may face more detailed testing and verification steps.
How long until my app goes live?
Review times vary, and account verification plus the testing requirement can extend the total. Plan a buffer of two to three weeks.
What are common reasons a release gets blocked?
A missing Data safety form, an outdated target API level, or a policy mismatch. The "Policy status" section in the Console tells you what to fix.
In short: Google's cost is low, and the work is in verification, forms and testing. We write the app and run the store release under your own account. If you want to talk it through, email us or read about our own release story on the Tattoo Artist Books page.