Why would I use this over, say, Stripe, which is also very developer friendly, robust, and no fear of disappearing anytime soon.
You are forced to use Apple's in-app purchase APIs which are not very developer friendly (especially for subscriptions) and aren't very complete with regards to metrics.
Also, RevenueCat will be around for 1000 years so I reject the notion of us disappearing. :p Actually, I think about that every day. I had a lot of friends who got burned when Parse shutdown and I plan to avoid that. The way our pricing and costs work, we should never have to shut down the service.
It's my intention to build the company of my life and run the service forever. I hate the idea of a BigCo buying us, shutting down our service, and screwing over all the devs that trusted us. It would have to be a pretty ridiculous amount of money to make me sell out like that (in case you're listening Mark).
I think we just need build trust in the community. That takes time and I accept that.
Obviously I think the benefits of outsourcing your in-app subscriptions to us is well worth it, based on our experience and the engineering time you will be saving, but I might be biased :)
I've grown a lot since the AppLoop days. :)
As far as not losing motivation, I can't prove a negative, so I won't try.
We are not dead if Apple does something to make the system much better, the problem of multi-channel subscription management will still exist for our largest customers.
P.S. Hope L.A. treats you well. I have scooter envy.
I think they did as good a job as could be done shutting it down. But, I think they missed a huge opportunity though. They could have been Firebase. Maybe making money was an issue but I think they could have figured it out eventually.
Parse was very very good for making it easy to prototype apps. However, once apps began to scale, Parse fell apart and was not a suitable technology. They would not have been able to make money because all the big money comes when people have full scale deployments on a platform, and that simply would not have been possible with Parse's shitty-for-scale technology. Again, very awesome tech for rapid prototyping mobile app development ca. 2012 2013..
It wasn't my decision to bet on the technology; it was in place when I was called in to put out the fires. I have a hard-won personal rule not to bet my organization's technical architecture on any tech that hasn't been around for at least 5 years UNLESS it solves a mission-critical pain point / workflow / etc.
I was on the engineering team for another mobile app that did $20M a year in revenue, mostly from in-app subscriptions.. was extremely costly to manage, so seems like you may have a pain point here and a new tech that may be worth betting on. Good luck!