Show HN: RevenueCat Paywalls
twitter.comHey HN! It's been a while but I wanted to pop back in to share that we just shipped paywalls: a remotely configurable, App Store compliant, and testable paywall out of the box.
We shied away from building this for longer than we should have but it's such a huge component of making more money on the app stores we just had to.
It relies on native components, but is configurable from the web, which we think achieves a good balance of flexibility and performance. We're just on iOS for now, Android soon, then hopefully more platforms in time. I might be migrating to using Revenuecat and I am curious about one thing. I have in app subscriptions in iOS and Android. I plan to add Stripe into this mix as well at some point and I wonder if you handle the case when users jump from subscriptions in one platform to another. I would like to move certain users (for instance by recommending that in a newsletter, or handing out coupons for the Stripe subscription) from their current iOS subscription to Stripe, and it is hard to make the overlap smooth. Does Revenuecat have some solution to this? Hi! We’d love to have you. For this particular case it’s tricky on iOS since you can’t programmatically cancel a subscription on iOS. It must be initiated by the customer on the device. However, if you navigate that UX challenge, you can use our events and webhooks to make a smooth experience guiding a user through the process. Hadn’t thought of this before, but you could probably pre-authorize a stripe token, then ask them to cancel on iOS, then wait for the webhook from us, then finish the transaction and track it to the same customer ID in RevenueCat. Alright, I might try it out. When the user cancel iOS the subscription is still payed and valid until the month ends probably. I guess one could delay the Stripe period the same amount of days or something. Love it: The bottom banner view is a killer feature Love this!