purchases-ios VS Swinject

RevenueCat — Hosted backend for in-app purchases and subscriptions (iOS and Android). Free up to $2.5k/mo in tracked revenue.

You got it! Yea, I can't promise everything will work perfectly with all those other platforms, but I will promise that I believe we have the best handling out there. We have 10+ engineers fielding issues from 1000s of developers every month and incrementally improving.

We try to collect as little data as possible, but we use RevenueCat for handling the IAP. We currently use it with anonymous (randomly generated) IDs and don't save additional attribution metadata, so we try to be as privacy-friendly as is possible with this setup.

For IAPs, RevenueCat is one of the simplest setup that exists for React Native. And they have an expo plugin. But having this expo management workflow is the first thing you want to do. https://www.revenuecat.com/

Alternatively you could use RevenueCat which would handle receipt validation for you. I haven’t used it personally but everyone seems to sing its praises.

There are services out there like revenuecat (disclaimer: I have no connection with them, other than being a satisfied customer) that help make these things easier. I recommend looking into them if you’re struggling to wrap your head around it on your own, apple’s documentation can be pretty hard to decipher at times.

I'm Josh Holtz, the author of this article. You might now me from my lead maintainer role of fastlane, creator of Indie Dev Monday, and founder of the new Deep Dish Swift conference ☺️ But I also work at RevenueCat to help developers make more money by making in-app purchases and subscriptions easier!

I have integrated RevenueCat in my previous Startup Fitenium to manage subscriptions, and it was one of the best decisions. Instead of having to integrate both Apple and Google play SDK for subscriptions, with RevenueCat I simply integrated their SDK, which is well documented and much easier to work with. Everything else is magically managed by RevenueCat behind the scenes, to properly handle the payments, users, and analytics.

RevenueCat — Hosted backend for in-app purchases and subscriptions (iOS and Android). Free up to $10k/mo in tracked revenue.

DI is a concept which makes a class independent of its dependency management. It achieves that by decoupling the usage of an object from its creation. This helps you to follow SOLID’s dependency inversion and single responsibility principles. To achieve this in Swift one of the most appreciated library is Swinject. This library not only provides DI but also have many other features like:-

Swinject - Dependency injection framework for Swift. Language: Swift.

We use Swinject which is probably quite similar https://github.com/Swinject/Swinject

So, how do we fix this? There is a cleaner solution. By using a dependency injection framework, such as Swinject we can create a base module that we might call the DI module.