A few years back Apple. introduced an in-app purchases concept in app stores which helps app #developers. to receive #payments. from customers without using anything 3rd party (Apple will manage everything ) for non-consumable products that can be consumed on a mobile device. It was optional and now it’s mandatory to use. You cant use another payment provider on App Store for products like digital goods, subscriptions, and premium content.
I am pretty sure developers who had implemented Apple in-app purchases faced a lot of difficulties especially if u had used hybrid development either react native or Flutter because of a lack of standardised documentation.
Apple In-app purchases will take you a minimum of 1 week for implementation and deployment which is quite a time if u compare another offering like Stripe which requires a maximum of 1 day for implementation and deployment. In-app purchases testing Is altogether an independent pain.
We are in an era where everything is just plugged and play, especially in payment industries where u can just get the payment with one line of code. But in the case of Apple, it is a whole lot of stories. Why can’t Apple offer just a simple web-based Integration or one function call and manage everything internally? I think it will save a lot of developers’ time.
If you are thinking you can use any 3rd parties like Chargebee. or RevenueCat. and reduce your implementation time, I will not be positive about this. They will help you to manage your revenue in one place if u have multiple revenue channels like web, android, ios etc but not reduce your implementation pain.
