Key takeaways
- Decide whose package name the app uses before the first upload – on Google Play it can never change, and Base44's export fixes it for you.
- An agent-maintained Android project gives you your own upload key with Play App Signing, Play Billing and editable permissions.
- Because Android builds run on Linux, any CI runner and most cloud agents can build and test the project on every pull request.
- Play Console work – closed test, Data safety, deletion URL, production access – stays with a person, but the agent can prepare most of the inputs.
The decision you cannot undo: whose package name?
Every Google Play app is identified by its package name, and once an app is published under one, it keeps it forever. That makes the first Base44 decision on Android a permanent one:
| Base44's Google Play files | Your own Android project | |
|---|---|---|
| Package name | Fixed by Base44 (com.base plus your app ID) | com.yourcompany.yourapp |
| Signing | Set up by Base44, not changeable | Your upload key plus Play App Signing |
| Digital purchases | No Play Billing | Play Billing through a bridge |
| Permissions | Chosen by Base44's scan | Declared in your manifest, reviewed by you |
| Later switch | Means a new store listing, without your installs and ratings | Not needed |
If you only need a quick internal tool on Play, Base44's files are a legitimate shortcut – our post on converting Base44 to an Android app walks through them. If the app is your product, start with your own project, and let a coding agent carry the maintenance that used to make that option expensive.
What a Base44 project looks like to an agent
Turn on GitHub sync in Base44 (Builder plan and up) and let the agent read the repository before it writes anything. It will find a React frontend built with Vite, Tailwind CSS and shadcn/ui, and calls through the Base44 SDK to a managed backend: data entities, built-in authentication and backend functions that run on Deno.
Two conclusions follow, and they belong in the agent's instructions:
- The Android app loads your published Base44 app. It does not bundle the frontend, because the SDK needs the hosted backend anyway.
- Product changes keep happening in Base44's chat. The agent's repository contains only the Android project, its CI and its instruction file. Its rare changes to the web side – a user-agent check for app mode, a delete-account call – go through pull requests you review.
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.
The Android project the agent maintains
A WebView shell in Kotlin is the usual choice. A Trusted Web Activity is possible too – Base44 generates a web app manifest for every app – but it needs a working service worker and a Digital Asset Links file on your domain, and Base44 serves the /.well-known path itself. Confirm with Base44 support that you can publish files there before you rely on App Links or a TWA.
The Base44-specific tasks for the shell:
- Password reset links. Base44's reset emails link to fixed paths such as
/reset-password. With App Links in place they open in the app; without, in the browser – test both. - Push. Firebase Cloud Messaging in the shell, the token handed to the web app, and a Base44 backend function that sends messages through the FCM HTTP v1 API with a service account stored in the backend's secrets.
- Play Billing. The web app requests a purchase through a JavaScript interface that the shell exposes only to your own origin. After the purchase, a backend function verifies it and writes the entitlement to a Base44 entity.
- Google sign-in. It must leave the WebView – a Custom Tab handles it. Test on a real device that the Base44 session actually arrives back in the app; if it does not, offer email sign-in in the app instead.
- The basics. File chooser for uploads, back navigation through web history, edge-to-edge insets, an offline screen, and the notification permission requested in context.
A pipeline that runs on any Linux runner
Unlike iOS, nothing here needs a Mac. Ask the agent for a GitHub Actions workflow on an Ubuntu runner that:
- sets up the JDK version the Gradle build expects and uses the committed Gradle wrapper,
- runs lint and unit tests on every pull request and attaches a debug APK for quick checks,
- on a release tag, builds the App Bundle with
bundleRelease, signed with the upload key from CI secrets, - uploads the bundle to the internal testing track with a Play Console service account.
That pipeline is also what makes cloud agents useful. Codex cloud tasks, the GitHub Copilot coding agent or Jules can pick up an issue and open a pull request; CI proves whether the change builds before you even look at it. Our GitHub Actions playbook has working examples.
The Play Console work that stays human
| Task | Why a person does it | How the agent helps |
|---|---|---|
| Developer account and identity checks | Legal identity; organizations need a D-U-N-S number | – |
| Closed test (new personal accounts) | 12 real testers, opted in for 14 consecutive days | Ships fixes as new builds during the test |
| Data safety form | You declare it and are accountable for it | Lists SDKs, permissions and data sent to Base44 or AI providers |
| Account deletion | The web deletion URL is entered by you | Builds the in-app flow and the public request page |
| App access | Credentials for reviewers | Seeds realistic production data for the review account |
| Production access | Google asks about your testing | Summarises the test feedback and the fixes |
The guides on the closed testing requirement and the Webviews policy cover two of the hurdles Base44 apps meet most often.
Keeping the app current after launch
An Android project needs regular care that Base44 would otherwise do for you. Google raises the required target API level every year – new apps and updates must target API level 36 since August 31, 2026 – and the Play Billing Library has its own deprecation schedule, announced in Play Console. Both are well-defined tasks for an agent: a branch, an upgrade, the tests, a pre-launch report, a staged rollout.
Keep the release discipline too: new features you publish in Base44 should match what the store listing promises, or Play's deceptive behavior policy becomes relevant. If you want this run for you, our AI Code Engineers handle signing, CI/CD, testing tracks and releases in your own account – see the Android submission service. The iOS counterpart is Base44 to the App Store: the agentic route.
Checklist: Base44 to Google Play with an agent
- The package name decision was made before the first upload.
- GitHub sync is on; the Android project lives in a separate repository with an instruction file.
- The shell loads the published Base44 app on your domain.
- Base44 support confirmed whether assetlinks.json can be served from your domain.
- Purchases of digital goods go through Play Billing and are verified by a backend function.
- CI builds a signed App Bundle targeting API level 36; the upload key is backed up outside the repository.
- Closed test, Data safety, deletion URL and App access are complete in Play Console.
Frequently asked questions
Can I move from Base44's Play files to my own project later?
Only as a new app with a new package name and a new listing. Installs, ratings and reviews do not move with it, which is why we recommend deciding before the first upload.
Does the agent need a Mac for the Android app?
No. Android builds run on Linux, Windows or macOS. A Linux CI runner can build, test, sign and upload the App Bundle.
Can I sell subscriptions in a Base44 Android app?
Digital goods and subscriptions sold in the app need Google Play Billing. Base44's own export does not support it; a shell with a billing bridge and a backend function that records the entitlement does.
Can you run the Play Console side for us?
Yes. Book a free call and an AI Code Engineer looks at your Base44 app and your account status. We can take over signing, CI/CD, the closed test set-up, policy forms and releases in your own Play Console.
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.