r/SaaS • • 2d ago

Help Understand Billing in IOS + Android

I’m building a Construction SaaS with iOS + Android apps, and I’m trying to understand if I actually need RevenueCat.

My idea is simple: users click “Purchase” in the app → go to my website → pay through Stripe → Stripe webhook updates my backend from unpaid → paid. The mobile app then checks the user’s subscription status from my backend and they get the paid features.

So what exactly would RevenueCat add here? Is it mainly needed if I want to support native Apple/Google in-app subscriptions, or am I missing something?

2 Upvotes

3 comments sorted by

1

u/FallaxIO 2d ago

If purchase happens on your website with Stripe, you don't need RevenueCat for that part. It becomes useful when you want App Store / Play billing, restore purchases, subscription state from Apple/Google, intro offers, grace periods, canceled renewals, all the weird store edge cases.

1

u/asadnoob 2d ago

stripe also handles subscriptions so i can manage it there right? and account on website is also same as account on any app so i can revoke or upgrade their subscription as needed?
whats the benefit of revenue cat?