Shopify Store to Android App: Checkout, Google Pay and Play Rules (2026)

To turn a Shopify store into an Android app, you either wrap your live storefront in an Android app shell (a WebView app) or rebuild it as native screens that talk to Shopify's APIs. Wrapping is faster and keeps your theme, installed Shopify apps and checkout exactly as they are, but three details decide whether it works in practice: how checkout payments behave inside the app (especially Google Pay), whether Google Play's billing rules apply to what you sell, and whether the app passes Play's WebView spam review.

Can you turn a Shopify store into an Android app?

Yes, a Shopify store can become an installable Android app, but Shopify does not publish a Play Store app for your storefront on your behalf. You use a third-party app builder, a converter that wraps your store URL, or a custom build by a developer. The route you pick sets your cost, how closely the app matches your website, and how much of it you must maintain.

If your store already works well on a phone, wrapping is the shortest path. The longer guide on how to turn Shopify, Wix, Squarespace or Webflow into an Android app covers the general process; this post covers what is specific to a store that takes payments.

Does Google Pay work in a Shopify Android app?

Google Pay can work inside an Android app that embeds your Shopify checkout, but it is not automatic. Google announced Google Pay support inside Android WebView on May 28, 2025, available from WebView version 137 and Google Play Services 25.18.30, and the app itself must switch on the Payment Request API for its WebView. Until that is done, the Google Pay button can be missing in the app even though it shows in Chrome on the same phone.

Developers hit exactly this gap with Shopify's own Android checkout SDK: a public GitHub issue describes the Google Pay button missing from the in-app checkout while it appeared in the browser, and a later comment on the thread reports that Google Pay works from SDK version 3.4.0. According to Google's announcement of Google Pay in Android WebView, the app also needs a manifest declaration and production access requested through the Google Pay & Wallet console.

The practical lesson is to test payment wallets on your own store with a real device rather than assume they appear. Cards and other methods your checkout offers are separate from Google Pay, so test each one you rely on.

1. 1

   Install the build on a real phone

   Use an Android phone with Google Pay set up and a current Android System WebView. Emulators often lack a configured wallet.

2. 2

   Open your store in Chrome first

   Add a product to the cart, start checkout and note every payment option shown. This is your baseline.

3. 3

   Repeat the same order in the app

   Compare the payment options in the app with the Chrome baseline. A missing wallet button is the most common difference.

4. 4

   Complete a test order

   Finish an order in your payment provider's test mode, or a low-value real order, and confirm the order and confirmation email arrive.

5. 5

   Check the exit paths

   On the thank-you page, tap links such as order status or account. Make sure the shopper is not stranded outside the app or on a dead end.

6. 6

   Retest after changes

   Run the same checklist after a theme change, a new payment method or a major Android WebView update.

Does Google Play billing apply to products sold in a Shopify app?

For physical goods, no: Google's Payments policy says Google Play's billing system must not be used when payment is primarily for physical goods such as groceries, clothing, housewares or electronics, so your Shopify checkout is the correct payment path. For digital goods and paid in-app features, the same policy requires Google Play's billing system unless a stated exception applies. Read the current text on Google Play's Payments policy page, because policy wording and regional programs change.

Will Google Play reject a Shopify store app that is just a WebView?

It can. Google's Android Developers blog says it sees many submissions that are only webviews of existing websites, submitted mainly to drive traffic, and that such apps are treated as webview spam and removed from Play. Google's advice there is to think through what users can do better in the app than on the web. A store app with a real reason to exist is far easier to defend than a bare window onto your homepage.

For a store, that reason is usually re-engagement. Push notifications for order updates, restocks and offers give shoppers something the mobile site cannot, and Capsule includes push notifications. The full list of rejection causes and fixes is in the guide to Google Play rejecting WebView apps, and the setup side is in push notifications for an app built from your website. Google's own wording is in its common policy violations post.

What should you fix in your Shopify theme before wrapping it?

Fix anything that behaves differently inside an embedded browser than in Chrome, because shoppers will meet it in the app on day one.

• Sign-in with Google: Google blocks its sign-in page inside embedded WebViews, so a Google login button on your account pages can fail with Error 403: disallowed_useragent. Offer email or another method in the app.
• File uploads: if a product page lets buyers upload a photo or file, test it. On Android, an embedded WebView does nothing for a file input unless the app implements a file chooser.
• Banners that say "Download our app": remove or hide them for app visitors, since they would show inside the app itself.
• Pop-ups and cookie banners: make sure they can be dismissed with a tap and do not cover the add-to-cart button.
• Tap targets and sticky bars: check the cart button, variant selectors and quantity steppers with a thumb on a small screen.
• External links: decide whether links to social profiles or policies should open in the app or the browser, and test them.

Wrapped store app or native Shopify app builder: which should you choose?

Choose a wrapped app when your Shopify theme already works well on phones and you want it on Google Play quickly; choose a native builder when you want app-specific screens, product sync into native layouts, or an iOS app at the same time. Native builders have real strengths here. Several list catalog sync, push and both Android and iOS output, and some, like Choicely, rebuild pages as native screens instead of embedding the website.

• Pick a wrapped app if you want your store exactly as it is, one design to maintain, and a one-time cost rather than a monthly plan.
• Pick a native builder if you need iOS today, want screens that differ from your website, or want deeper catalog features.
• Pick a custom build if the app is a core product with its own roadmap and you have developer budget.

For pricing models across both approaches, see the cost breakdown for turning a website into an app.

Where does Capsule fit for a Shopify store?

Capsule turns a website URL into an Android app and delivers a signed APK and AAB, with push notifications included, for a $120 one-time fee per app after a 7-day free trial. For a Shopify store, the sensible way to use the trial is to run the checkout checklist above on your own store before you pay. iOS is on Capsule's roadmap, so a store that needs an iPhone app today should look at a native builder.

How do you publish a Shopify store app on Google Play?

You upload the signed AAB to Google Play Console, complete the store listing and app content forms, and submit for review. The full walkthrough, with costs and timelines, is in the guide to how to publish an app on Google Play.

1. 1Create a Play Console developer account.
2. 2Build and sign the app (an AAB for Play, plus an APK for sideload testing).
3. 3Prepare listing assets: icon, screenshots and a clear description of what shoppers can do in the app.
4. 4Complete the app content forms, including privacy policy and data safety.
5. 5Upload the AAB, run the required testing for your account type, and submit for review.