Has someone tried to integrate revenue cat with ios or android?
cheers
I haven’t personally integrated RevenueCat with Bubble, but it’s possible through their REST API. You’d call RevenueCat’s API endpoints using Bubble’s API Connector to manage subscriptions, entitlements, and webhooks.
The trickier part is the native iOS/Android side — RevenueCat’s SDK is native, so if you’re using Bubble’s native wrapper (or something like BDK Native), you’d need to figure out how to bridge that. If you’re just building a PWA, the REST API route is more straightforward.
What’s your setup — native wrapper or PWA?
Legend Alex. Thanks. I’m thinking ahead, but I want to go with a native wrapper.
Hi @adig, we have in app purchases supported natively (direct connection with Apple and Google’s billing systems). Is there a reason why you want to connect to revenuecat instead?
Hey @nick.carroll Cheers for jumping. Well, doesn’t Apple take 30% from the in-app purchase?
I’m guessing with revenue cat you won’t have this issue?
Would appreciate clearing this out.
So yeah for In App Purchases, Apple and Google take a cut of the revenue. However, that problem doesn’t go away if you add an intermediary like RevenueCat. RevenueCat allows app developers to provide In App Purchases more easily by abstracting the connections required to Apple and Google’s billing system, however, you still would be subject to Apple and Google’s cut.
We are essentially doing the same thing that RevenueCat is doing, just already integrated and built into Bubble.
Yeah, makes complete sense. What if I have a pay per use model? I’m guessing that’s not considered an in-app puchase? Do I just use a stripe (flow) in the native mobile screen for a user to pay once for a service? Cheers
Hi Adig, just yesterday we released this RevenueCat plugin: RevenueCat Advanced for Bubble: 🚀 [NEW PLUGIN] RevenueCat Advanced: The ultimate subscription engine for Bubble!, and I’d love to go a bit deeper into why it can be really valuable to use RevenueCat on top of Bubble’s native in‑app purchases.
First, RevenueCat gives you a single, unified subscription backend across iOS, Android and Web, so you manage products, entitlements and users in one place instead of rebuilding logic per platform or wrapper (BDK Native, PWA, etc.). On top of that, it comes with a dedicated analytics layer (MRR, churn, cohorts, trial conversions, LTV) built specifically for subscription businesses, which you’d otherwise have to stitch together manually in Bubble workflows and your own database.
Second, RevenueCat provides rich webhooks and integrations so all key subscription events (renewals, cancellations, billing issues, grace periods) can be pushed reliably into Bubble or external tools like Segment, Amplitude, or your own backend. That makes it easier to automate lifecycle flows (win‑back emails, in‑app messages, feature gating) without reinventing the plumbing.
Finally, using RevenueCat as the subscription layer gives you portability and flexibility: if you ever move part of your product outside Bubble or add new frontends, you don’t need to redesign how subscriptions work because RevenueCat already abstracts the stores for you. Bubble’s native IAP is great for many use cases, but RevenueCat can be a strong complement when you’re aiming for a serious, multi‑platform subscription business with deeper analytics and growth tooling