iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Publishing a Kotlin Multiplatform (KMP) app on Google Play uses the standard Android release process. The extra KMP work is in building and integrating shared code across platforms; Play Console still requires a correctly configured listing, signed release, testing, and review. The first-release challenges are therefore a mix of cross-platform integration and familiar Android release requirements—not a separate KMP publishing pipeline.
Where KMP changes the work—and where it does not
KMP lets a project share code between platforms, but it does not turn the Android app into a special kind of Play submission. Kotlin’s official publishing guide says the Android app and shared Android library are typical Android Gradle modules, and that publishing follows the usual Android process. In other words, the release boundary is the Android app you build, sign, and submit—not the fact that some of its code is shared.
The distinction matters when planning a first launch. Shared code and platform-specific integration are development concerns; the Play listing, release bundle, testing track, and production review are Android publishing concerns. A KMP project may need work on both fronts, but the Android submission itself follows the established Play workflow.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Build and verify each platform integration
Sharing business logic does not eliminate platform integration. On Android, the shared module is consumed through the Android project. On iOS, the shared Kotlin module must be connected to the iOS project as a framework, and the app should be launched and tested at runtime. That iOS integration is a separate task from publishing the Android app to Google Play; it becomes relevant when the project is intended to ship on both platforms.
#1 Best Overall
For a first release, keep the platform checks distinct: confirm the Android app builds and runs as an Android app, then verify the iOS integration in the iOS project if that platform is in scope. A successful build alone is not a substitute for launching the app and checking its runtime behavior.
Prepare the Android release for Play Console
Play Console’s release flow covers app setup and the store listing, release preparation, testing, and launch. Android apps must be digitally signed, and Google Play uses Android App Bundles to generate APKs optimized for users’ devices. Those requirements apply whether the app is written entirely in Kotlin for Android or includes shared KMP code.
Rank #2
- Set up the app and listing. Create the app in Play Console and complete its store listing and required app details.
- Prepare a signed release. Build the Android release and configure signing. Play accepts Android App Bundles for delivery, generating device-optimized APKs from the bundle.
- Choose a testing track. Internal, closed, and open testing provide different levels of access and visibility. Use a track appropriate to the audience and any account-specific eligibility requirements.
- Submit for production when eligible. Complete the applicable testing and production-access steps, then submit the production release and wait for review.
Choose a testing track that fits the release
Testing tracks are stages with different audiences, not interchangeable product options. Internal testing distributes an app to a small selected group. Closed testing limits access to chosen testers. Open testing lets users join through Google Play. Production makes the app available in the countries or regions selected for the release.
| Track | Who can access it | What it is for | Next-stage relevance |
|---|---|---|---|
| Internal testing | A small selected group | Early distribution to a limited audience | Testing stage; it does not replace the closed-test requirement for covered new personal accounts. |
| Closed testing | Chosen testers | Restricted testing and feedback | Required before applying for production access for covered new personal developer accounts. |
| Open testing | Users who join through Google Play | Broader testing with Play-based access | A testing stage; the stated new-personal-account rule specifically calls for a qualifying closed test. |
| Production | Users in selected countries or regions | General availability | The public release stage, subject to Play review and applicable account requirements. |
Check whether your account has a closed-test gate
Google Play requires personal developer accounts created after November 13, 2023 to complete a closed test before they can apply for production access. The test must have at least 12 testers opted in continuously for at least 14 days. The rule is scoped to those newer personal accounts; do not assume it applies to every developer account or present it as a universal KMP requirement.
This changes release planning: the covered developer must recruit testers, keep the required number opted in throughout the full period, and then apply for production access. The 14-day testing period is a minimum continuous duration, not a guaranteed date for public launch; production access and the app release still involve further steps.
Meet the current target Android version requirement
As of August 31, 2026, new Google Play apps and updates generally must target Android 16 (API level 36) or higher. Google lists exceptions for certain form factors, so check the requirement that applies to the app’s category in Play Console before release. This is a dated platform policy rather than a permanent KMP rule, and it should be verified again when preparing a later update.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Allow time for review without assuming a fixed window
Google does not promise one review duration for every submission. It says some developer accounts may receive a more thorough review, which can take up to seven days or longer in exceptional cases. Treat that as a qualified possibility, not a standard turnaround time or a reliable launch-date estimate.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Best Value
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
