4 ms·
I recently implemented Google Play billing in my app (after doing Stripe and Apple App Store) and Stripe was by far the easiest to implement/test/maintain. Goo
by candiddevmike 6y ago
I recently implemented Google Play billing in my app (after doing Stripe and Apple App Store) and Stripe was by far the easiest to implement/test/maintain. Google and Apple not only take their 15/30% cut, their payment systems add a very non trivial amount of work (cost) to implement and maintain while offering none of the (automated) testing capabilities of Stripe. Work that I'm forced to do, even though I had already implemented Stripe. All because they have a monopoly on their platform.
For something as critical as payment processing, both Apple and Google make it an arcane journey into API documentation and stack overflow questions.
Hoping to write a blog post detailing all of this in the near future.
- cyral 6y agoI really hope Stripe builds out a better payment solution around the App Store and Google Play APIs. I would love to see their take on it. There are services like RevenueCat that do this but they are small companies and still don’t have the best API. (And have a lot of bugs) Still better than dealing with the terrible APIs from Apple and Google directly though
- CodesInChaos 6y agoThe google play subscription API is unbelievably buggy and generally terrible. Apple's and Amazon's APIs have major flaws as well, but Google is on a whole different level.
- shimfish 6y agoI used RevenueCat's API for Apple and Google just to avoid having to do all this crap myself and it's free up to $10,000 of monthly revenue. I was less happy with their Google implementation, mostly because of their bizarre insistence of treating every IAP as consumable but overall still less painful than having to roll my own code.