Google Play will sell your in-app products outside your app. Is your billing ready?

Google Play wants to sell your in-app products in places other than your app. On 16 November 2026, Phalene Gowling and Rejane França published a post on the Android Developers Blog explaining how developers can now sell digital products outside the app itself. Everything runs through the Merchandising and optimization page in Play Console. You choose the products, and Play decides where they show up, on surfaces like Apps Home, Games Home and the details pages for apps and games.
The page covers three things: featured products, reminders when someone abandons a cart, and recommendations inside the purchase flow. Google says the Play Store has more than 2.5 billion monthly active users and that over 7,700 developers already use the page. Its showcase partner, MYBO Games, saw user spend outside its game rise 60%, based on Google's internal 2026 data. There are new controls too. You can cap how often one account can claim a product or offer. Exclusion groups keep your entry-level discount away from current subscribers or people who just bought something. You can target audiences for one-time products and offers, and link accounts across platforms using Play Billing account identifiers that you verify on your server. Play Billing Lab now has previews for out-of-app purchases. The flashiest part, buying digital goods inside a Gemini conversation with one-tap Play checkout, is only running in early-access pilots. Google's example is someone asking Gemini about music streaming plans.
What this changes for mobile teams
For most apps the storefront has always been something you build yourself, inside your own UI, on your own terms. Now Play renders your products in places you don't control, and the purchase can start while your app isn't even running. The extra reach is real. The catch is that part of the purchase journey now happens outside your code.
In our native Android projects, the billing bugs that hurt most are almost never the purchase itself. They show up just after it: the app wasn't open, the purchase listener never fired, and the user opens the app three hours later to find nothing there. Then the support tickets arrive. Out-of-app sales turn that path from an edge case into a normal day. If your app only grants entitlements from an in-app callback, fix that before you feature a single product.
Honestly, the controls matter more than the reach
The reach numbers are Google's numbers. A 60% lift at one hand-picked partner is a showcase, not a forecast for your app. What I find more useful are the boring parts. Quantity limits and exclusion groups are what stop your own promotions from eating your revenue. In our work with gaming studios we've watched starter packs get farmed by players with several accounts, and new-user discounts quietly bought by people who had been paying full price for a year. Rules like these used to live in custom backend code. Having them at the store level is a good thing.
The problem is that several of these controls are available or rolling out through the Early Access Program, and you need to work with a Google Play partner manager to join. That covers multi-level exclusion groups, quantity limits, target audiences for one-time products, the Play Billing Lab preview and agentic catalog management. Plenty of the startups we work with don't have a partner manager. So you may get the new surfaces before the guardrails. Until you have the guardrails, price anything you feature as if anyone at all can buy it, as many times as they like.
Account linking is a security question
Verified cross-platform account linking sounds like a convenience feature. From the backend side it is mostly a security feature. During our pentesting engagements, entitlement endpoints that trust whatever the client sends are a finding we keep running into on mobile backends. If someone buys on Play and expects the item on iOS or on your web app, your server has to tie that purchase to the right account, and it has to check the purchase with Google instead of taking the app's word for it.
When we build PHP and Docker backends that serve both iOS and Android clients, we keep one entitlement service as the source of truth and make the apps ask it what the user owns. If your apps each decide for themselves today, out-of-app purchases will expose that quickly. Our development work on cross-platform apps nearly always starts with this piece, because it's the hardest one to change later.
Gemini checkout: interesting, but not this quarter
I have mixed feelings about selling inside a chat assistant. On one hand, a user asking about streaming plans is about as high-intent as it gets. On the other, you hand the pitch to a model you don't control, in a pilot you probably aren't in. I wouldn't plan a roadmap around it yet. What I would do is treat your product catalog as something machines will read. Product names like "pack_03_v2" or a plain "100 coins" mean nothing on Games Home, and they'll mean even less to an assistant.
What to do this week
- Find every place your app grants entitlements. Anything that depends only on an in-app purchase callback should move to server-side verification, with a check against owned purchases every time the app starts.
- Clean up your catalog. Give products names and descriptions that make sense to someone who has never opened your app.
- Decide which products should never be featured, for example one-time starter offers, until you can apply quantity limits and exclusions.
- If you have access, use the Play Billing Lab previews to walk through user journeys, check how featured products and cart reminders look on different screen sizes, test your exclusion rules and confirm entitlements actually arrive before launch.
- If you already have a partner manager, ask about the Early Access Program now rather than after a promotion has gone wrong.
We've spent years on billing flows in games, healthcare and e-commerce apps, and some of that shows up in our portfolio. The pattern holds every time: the more places a purchase can start, the more your backend has to be the one that decides what the user owns.
If a billing flow that only works when your app is open sounds familiar, let's talk.