Key takeaways
- Rork produces the App Bundle; creating the app, uploading, the policy forms and the release decisions happen in your Play Console.
- Whatever key signs the first uploaded bundle becomes your upload key – know where it lives and whether you can use it outside Rork.
- Testers who installed a shared APK do not count toward Google's closed test; they must opt in to a closed track in Play Console.
- Check target API level, permissions, Data safety, account deletion and Play Billing before the first upload, not after a rejection.
What Rork hands you for Android
Rork turns prompts into mobile apps. According to its documentation, current projects are written as native Android apps in Kotlin with Jetpack Compose, while projects created earlier use React Native and Expo. During development you try the app in Rork's preview – an emulator in the browser or an APK on your phone.
For Google Play, Rork's FAQ describes the hand-off plainly: Rork generates an Android App Bundle (.aab), and you upload it in Play Console yourself. Unlike its App Store flow, nothing goes live on Google Play without you creating the app, uploading the bundle and filling in the forms. That makes Play Console the place where this article mostly happens.
If you are still choosing a builder, our comparison of Rork and Bolt covers how each handles mobile output and exports.
Policies to check before the first upload
A rejection costs days. Most of the usual reasons can be checked in an afternoon before anything is uploaded:
| Policy area | What to check in a Rork app |
|---|---|
| Target API level | The bundle targets Android 16 (API level 36), required for new apps and updates since August 31, 2026 – see our target API guide |
| Permissions | Only permissions the app actually uses; sensitive ones such as location in the background need a declaration and a good reason |
| Data safety | Every data type the app or its services collect – including prompts or photos sent to an AI model |
| Account deletion | If users can sign up: deletion inside the app and a public web page for deletion requests |
| Payments | Digital upgrades and subscriptions through Google Play Billing |
| Functionality | No crashes on launch, no dead screens, AI features that work with a production backend – compare Google's broken functionality policy |
| Listing | Texts and screenshots that match the app, no keyword stuffing, no claims the app cannot keep |
For the Data safety form in particular, our playbook on Data safety with AI agents shows how to build the answers from the code.
Talk to an AI Code Engineer about shipping your app to Google Play.
In a free call we look at what you built, tell you honestly what stands between it and an approved release – and whether you need us at all.
Ownership: account, package name and repository
The Play Console account is the legal home of your app. Choose its type deliberately: a personal account is quick to open but brings the mandatory closed test for new accounts; an organization account needs a D-U-N-S Number and represents the company. Both go through identity verification, and Google's developer verification links each app to a verified developer – Play Console's home page shows the status of your apps.
Then fix two identifiers. The package name inside the bundle is permanent once uploaded, so make sure it is the one you want before the first upload, not a generated placeholder. And connect Rork's GitHub sync, available on paid plans, to a repository the company owns. With a Kotlin project, open it once in Android Studio and build a release bundle yourself – that is your proof that the app does not depend on any single tool.
Signing: whose upload key is in that bundle?
Every bundle you upload is signed. With Play App Signing, which new apps use, Google holds the app signing key that users' devices trust, and the key that signed your first upload becomes your upload key. All later uploads must be signed with that same key.
For a bundle generated by a builder, that raises practical questions to answer before the first upload:
- Which key signs Rork's bundles, and can you export it – for example to build updates in Android Studio later?
- If you build some versions locally and others in Rork, which key and which
versionCodesequence do both use? - Who on your team can reach the key if the person who set it up leaves?
Check Rork's current documentation or support for how it manages the key. If you ever lose access to the upload key, the account owner can request an upload key reset in Play Console; because the app signing key stays with Google, existing users keep receiving updates. It is a recovery path, not a plan – knowing your key from day one is better.
Testers: shared APKs do not count
Sharing an APK from Rork's preview is a fast way to get feedback from friends. It does not count toward Google Play's closed test. For personal developer accounts created after November 13, 2023, at least 12 testers must be opted in to a closed track in Play Console for 14 consecutive days before you can apply for production access.
Move your testers over properly:
- Upload the bundle to the internal testing track for your own team first.
- Create a closed track, add testers by email list or Google Group and share the opt-in link.
- Ask testers to install from Play – not from an old APK – so updates reach them automatically.
- Read the pre-launch report for each closed-track build, and add test credentials if the app requires a login.
- After 14 days, apply for production access and describe honestly how the test went.
Our closed testing playbook for AI-built apps covers recruiting testers who stay engaged.
The upload and the production release
In Play Console, create the app – name, default language, app or game, free or paid – and complete the app content section: privacy policy URL, Data safety, account deletion link, content rating, target audience and ads declaration. Upload the first bundle from Rork, accept Play App Signing, and work through internal, closed and finally production. Release to production as a staged rollout and watch crashes and ANRs before you go to 100%. Every update follows the same path with a higher versionCode.
Our AI Code Engineers can take this over in your own Play Console: account and app setup, signing review, listing, Data safety, the closed test plan and the review conversation. See the Android submission service, and for the iPhone version of your app, Rork app to the App Store.
Rork Android release checklist
- You know whether your project is native Kotlin or React Native with Expo.
- The bundle targets API level 36 and only requests permissions the app uses.
- Data safety answers cover the app, its SDKs and any AI services it uses.
- Account deletion works in the app and through a public web page.
- Digital purchases use Google Play Billing.
- The Play Console account type, identity verification and package name are settled.
- You know which key signs Rork's bundles and whether you can use it elsewhere.
- The project syncs to a company-owned GitHub repository and builds outside Rork.
- New personal accounts: 12 testers stayed opted in to a closed track for 14 days.
- Production starts with a staged rollout.
Frequently asked questions
Can Rork publish my app on Google Play automatically?
Rork's FAQ describes generating the Android App Bundle for you to upload in Play Console. Creating the app, uploading the first bundle, completing the policy forms and releasing to production are steps in your own Play Console account.
Is a Rork Android app native or React Native?
Rork's documentation says current projects are native Kotlin apps with Jetpack Compose. Projects created earlier may still be React Native with Expo – check yours before you plan builds outside Rork.
Do testers using my shared APK count for the closed test?
No. The requirement counts testers who are opted in to a closed testing track in Play Console. Invite them there and ask them to install the app from Google Play.
What happens if I lose the upload key?
With Play App Signing, the account owner can request an upload key reset in Play Console and register a new upload key. Users are not affected, because Google keeps the app signing key – but the reset takes time, so store the key safely from the start.
Can you get our Rork app onto Google Play?
Yes. Book a free call; we look at your bundle, your Play Console and the open policy items together and explain which steps we can take over.
Free, 15 minutes, no obligation
Get your app from agent output to approved release.
Our AI Code Engineers take apps built with Claude Code, Codex, Cursor, Lovable, Base44 and co. through signing, CI/CD, store listings and review – in your own developer accounts.
AI tools, store policies and requirements change quickly – always check the current documentation of the tools and stores you use. This article is independent advice and not affiliated with or endorsed by Apple, Google, Anthropic, OpenAI or any other company or product mentioned; all trademarks belong to their owners.