WooCommerce Android app: Google Play, APK and App Links
By Abdalla Kamesh · Published November 2, 2026 · 7 min read

You have a WooCommerce store, and you want it on Android phones as a real app. Android gives you something iOS does not: two ways in. A direct download from your own link, and a Google Play listing. This post covers both, in order, and links to the post that covers each step in full.
The WooCommerce iOS app post is the same guide for the iPhone.
What the Android app is
A StoreToNative Android app is built from your WooCommerce store. The catalog, search, cart and account screens are native screens that read your store’s live data. At checkout you choose between your store’s own checkout page inside the app (the default) and a native checkout form (an add-on). Either way, payment runs on your own gateway, with your existing payment plugins.
The app runs on Android 7.0 and newer. A signed Android build takes about seven minutes.
Way 1: a direct APK from your own link
Every Android build leaves an installable APK, the app file Android phones install. Your install page offers your newest one, with a printable QR code and steps for the prompts Android shows the first time someone installs an app from outside Google Play.
- No account, no fee, no review queue. The link works when the build finishes.
- It works on the trial. You can build your app and put it on your own phone and your team’s phones before you pay anything. Publishing to Google Play needs a paid plan.
- Ready for customers. The line under each build says whether its APK is a signed release build. When it is, you can hand it to real customers.
Once your app is live on Google Play and you mark it so, the same link and QR code open your Play listing instead. Direct APK: your app without the Play Store covers when this channel is the right first step.
Way 2: Google Play
The account: $25, once
The Google Play developer account costs $25, one time, paid to Google. It is not part of your StoreToNative plan. Google verifies your identity or business before you can publish. Your app is published under your own account and your own name. Apple and Google developer fees, explained compares the two stores’ costs.
Personal or organization?
This choice decides your timeline.
- A personal account created after 13 November 2023 must run a closed test with at least 12 testers, opted in for 14 continuous days, before it can apply for production access. A tester who drops out can reset the clock. Google Play’s 12 testers for 14 days explains what counts and how to plan around it.
- An organization account skips the closed test, but it needs a registered legal entity and a D-U-N-S number, which Google says can take up to 30 days.
Either way, the direct APK above keeps you selling to Android customers while you wait.
The build and your upload key
For Google Play, the console makes a signed .aab app bundle. Phones cannot install an .aab; it is the file you upload to Play. The same build also makes a fresh APK for your install link.
Each app gets its own signing key on its first Android build. You can export it as an upload key file from the Publish page, on any plan. Keep it somewhere safe: anyone with the file and its password can publish updates to your app, and you need it if you ever move the app away from StoreToNative.
The Play Console checklist
Open Publish → Google Play. The page is a checklist against your app’s real setup, with nine Play Console steps that you tick as you go: create the app, the store listing, the first upload to internal testing, the data safety form, the content rating, the app content declarations, countries and the closed test, send for review, and the steps after it is live.
- Data safety: the console works out the answers from the add-ons you use and gives you a Copy answers button. Play also wants an account-deletion address when your app has shopper accounts. Filling in app privacy and data-safety forms explains the form.
- Automatic uploads (optional): invite a service account in Play Console, and later store builds go to the internal testing track by themselves. Google’s own API does not allow two things, so they stay manual: creating the app record and the very first upload.
The full list is on the Publish to Google Play help page.
The review
Google reviews your app before it goes live. We can’t promise any reviewer’s decision. What the checklist does is remove the rejections that come from a form filled in wrong. Two states trip people up: a release saved as a draft on production, which nobody can install until you roll it out, and a change saved but not sent for review. The Publish page names both and says what to press.
After you are live: App Links
With App Links, a product link someone shares opens in your app instead of the browser. Android needs a small file, assetlinks.json, on your store’s own domain. It is completed with the Play App Signing SHA-256 fingerprint, which you copy from Play Console after Google approves the app, and the Product deep links add-on must be on. The optional WordPress companion plugin serves the file for you, or you download it from the console’s Growth page.
Then put the install path where your customers already are: a smart app banner on your mobile site and a QR code on packing slips.
Design changes reach installed apps over the air, within a launch or two, with no rebuild and no store re-review. A new build is needed only for the app name on the home screen, the launcher icon, the app id, the launch-screen color or a new store domain.
Related reading
- Publishing your store app to the App Store and Play
- Direct APK: your app without the Play Store
- Google Play’s 12 testers for 14 days, survived
- Filling in app privacy and data-safety forms
- WooCommerce iOS app: what it takes to reach the App Store
Guided Google Play publishing, under your own developer account, is part of every paid StoreToNative plan. The direct APK works on the trial. See what each plan includes.