Launch HN: RevenueCat (YC S18) – Simple API for Managing In-App Subscriptions

  • Congrats on the launch. I love 'boring infrastructure' companies, they are the ones that become huge :) The world is moving to subscription businesses and the tech needs to catch up

  • Man I wish this existed 8 months ago when I built our own version internally! We have a mix of Stripe and App Store customers so we'll definitely be switching (to remove our mental load) if you guys ever support that!

    Best of luck.

  • Pricing isn’t clear for larger scale apps. Is the extra charge per $1k on include the first 20k; after a tier is reached, how is the next $1k calculated.

    You should have an interactive price meter where we enter MTR and see the costs per month.

    You should also specify if MTR includes or excludes Apple’s cut.

    A great inclusion to the service is handling timed hooks to send notifications. Like if a user is about to have their trial expires and have their subscription cancelled, sending a notification to remind them of the trial can be helpful.

  • About time. It just saddens me that after so long dealing with the myriad problems of selling through the AppStore, the response has to come from a third party instead of Apple. Well, I guess it's developers solving developers' problems.

    Question: How does RevenueCat data integrate with my data pipeline? Seeing all the metrics and charts in your dashboard is great, but if I already have a data solution set up, is there a way to export all the revenue data from RevenueCat into our infrastructure?

  • This looks amazing and is definitely much-needed.

    Any plans to add an SDK for the Microsoft Store?

  • Any ETA/plans for a web version?

    I'd love to be able to use the same API for web and mobile, with revenue cat just wrapping a conventional payment processor to provide a compatible API surface.

  • Why has this not existed before?

  • Why would I use this over, say, Stripe, which is also very developer friendly, robust, and no fear of disappearing anytime soon.

  • Typo :^)

    Why should I trust RevenueCat? "Because... They brings that experience to RevenueCat."

  • Sounds cool. I would deploy it for our iOS app, but our subscriptions are finally working really well and there is too much risk that we’d break it. Maybe we’ll try it for our Android version when that gets built in a few months.

  • When will the Xamarin SDK be ready? Need to decide whether to implement on our own or wait for RevenueCat

  • There's a minor typo in the footer: "Revenue Model Cal>C<ulator"