Adapty VS purchases-ios

Please check it out https://github.com/adaptyteam/AdaptySDK-iOS/tree/master/Example/SwiftUI it would be helpful for me to know the opinion of experts like you. Thanks!

Hi folks, I added a SwiftUI-based demo application to our main SDK. This is my first experience with iOS development, and I want to know what experienced guys like you think. https://github.com/adaptyteam/AdaptySDK-iOS/tree/master/Example/SwiftUI

A possible solution is to use any services for subscription analytics which offer a smooth integration with Amplitude. Try checking out Adapty.io or Revenue Cat.

Another way is to temporarily change a price on a paywall and its design. For this purpose, you can design and code a new paywall and release a new version of the app. I do it the easier way, I use Adapty for it, so I don’t have to submit an app for the App Review every time I want to change something on my paywall.

The only ‘but’ here is that the server-side validation is hard to develop, because you need to think about numerous scenarios like refunds,, billing issues, intro/promo offers, family sharing, cross-grading, downgrading, a product unavailable for renewal, you name it. So at last I settled on using an off-the-shelf solution. I chose Adapty for that, because I like the simplicity of integration and the interface.

In my experience, you should almost never try implementing subscriptions by yourself, because it’s time-consuming and tedious. It's much faster and safer to just use a off-the-shelf solutions, like Adapty.io or RevenueCat.

Hey! I happy to help with Adapty (https://adapty.io) — we have simpler and more flexible SDK design which I bet you like.

BTW we're developing Adapty (https://adapty.io/) — an all-in-one service for mobile subscriptions with support of any web payments!

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.