New guides: Step-by-step setup for mobile in-app purchases (Apple & Google)

Hey everyone — I’m Jeremy, product enablement manager at Bubble.

Last month, we launched subscription-based in-app purchases in beta for native mobile apps. The response has been great, and a lot of you have jumped in to start building.

But we’ve also heard loud and clear that getting everything configured — especially across Apple and Google’s respective systems — can be a frustrating, confusing process. There are a lot of moving parts: keys, permissions, billing notifications, and test validation. It’s easy to get stuck.

So we built something to help.

We’ve just published two new step-by-step guides for in-app purchases — one for Apple, one for Google — that walk you through the entire setup process from start to finish.

Here’s what each guide covers:

  • App store setup — getting your app configured in App Store Connect or Google Play Console

  • Keys and credentials — generating and connecting the API keys that Bubble needs to communicate with each store

  • Billing notifications — configuring server-to-server notifications so Bubble can track renewals, cancellations, and subscription status changes in real time

  • Permissions — making sure your app has the right entitlements and access levels in place

  • Test validation — confirming everything works before you go live, using sandbox environments in both stores

Whether you’re setting up IAP for the first time or got partway through and hit a wall, these guides are designed to get you unstuck and all the way to a working setup.

You can find the interactive guides here:

These guides focus specifically on the setup process. If you’re looking for help with the rest of the implementation, you can find more details in our documentation:

A reminder that in-app purchases for subscriptions is still in beta, so we’re continuing to refine the experience. If you run into anything unexpected or have feedback on the guides themselves, drop it in the thread.

— Jeremy and the Mobile team

5 Likes

Thanks @Jeremy for this helpful guide!

When using the Initalize In-App Purchase workflow action, what’s your recommended next step? In the web app editor using the Stripe plugin you could basically ensure that the workflow would only proceed past the in-app purchase action if the checkout was completed. What’s the equivalent for native mobile?

What I’m finding is that Go to View proceeds in the background while the user looks at the Simulate Purchase modal.

Did you ever find a solution for this @mattblake ?