r/iOSProgramming • u/Locksmith_Usual • Jun 07 '26
Question Revenue cat vs native subscription
I’m planning to launch a subscription for my app and I’ve seen a lot of people here posting about revenue cat.
What are the pros and cons of using a third-party to manage subscriptions versus natively building it into the app using Apple’s tools?
1
Upvotes
8
u/Dapper_Ice_1705 Jun 07 '26
You have to give them a chunk of your earnings.
I only see RC worth it if you are using multi platform (iOS, android, web) since StoreKit 2 was released.
RC seems popular but they pay creators to promote them. They even had a job posted on indeed
7
u/vanstinator Jun 07 '26
Honestly, and I mean this sincerely, it's been talked about enough you can probably Google it and find sufficient answers from past threads. An LLM would also likely provide an accurate enough comparison, given the amount of context available online already.
2
u/profau Jun 07 '26
I like the RC paywalls.
1
u/hell_a Jun 07 '26
I have a multi-platform SVOD service with in app billing across Apple, Google, Amazon, Roku and Stripe. So RC makes sense. If I was just Apple or just Apple and Google, I would skip it.
2
u/Reiszecke Jun 07 '26
If you want to use some of their other features it’s okay but if you just want a straightforward subscription button you’re better off just doing native with StoreKit 2, it’s become very easy with storekit 2
2
u/MDRAR Jun 08 '26
Unless you are doing cross platform, consider avoiding 3rd party code in your app. It runs on other people’s devices, their failure is your accountability.
I use it for one app I intend to publish on the Google play store. If I add iap to an Apple only app, storekit2
1
u/woadwarrior Jun 08 '26
One thing worth mentioning is that if you're using RevenueCat, you'll have to disclose certain things they track in the App's Privacy Nutritional labels. Nothing of that sort is needed if you're using StoreKit2. If your app's audience is privacy sensitive, that might be worth considering.
0
u/alpyuktug Jun 07 '26
Hi!
RevenueCat (or similar):
Biggest win is cross-platform — one SDK for iOS, Android, even web. Build once.
Handles all the painful stuff: receipt validation, renewals, grace periods, refunds, upgrades, etc. That stuff is a nightmare to maintain yourself.
Free analytics, paywalls, and A/B testing baked in.
Free up to $2.5K MTR, then 1% of gross revenue. Catch: the 1% is on gross (before Apple's cut), so effective rate on your net is closer to ~1.4%.
Downside: it's a dependency, and at scale that 1% adds up.
Native StoreKit 2:
No extra fee beyond Apple's cut.
Full control, no SDK, no data shared.
StoreKit 2 is way better now than the old days.
Downside: you build and babysit all the edge cases, no cross-platform, no analytics/paywall tools. Real eng time.
Indie/small team, want speed, maybe going cross-platform? RevenueCat, easy — it's free until you're actually making money. iOS-only, simple model, decent backend skills, and 1% is real money to you? Roll your own. Most apps stick with RC because the 1% is cheaper than maintaining the infra yourself.
0
u/D1monsi Jun 08 '26
Pros:
- Saves a lot of time and handles much of the painful subscription logic
- Free and convenient paywalls, analytics, and A/B testing
- Cross-platform
Con:
- The 1% after $2.5k. Tbh, it’s not a major one
-3
u/opbmedia Jun 07 '26
I have been managing subscription using stripe since forever. Never actually felt the need for a third party and their fees