App Annie claims that 94% of all top-250 apps in the App Store are monetized using an in-app subscription. The same is true for the vast majority of apps that are not as popular. Usually, only 3–5% of all users convert into buying a subscription and 80% of them cancel it after a couple of months. How do you handle such a churn?
Subscriptions became a predominant way to monetize mobile applications in the last 5 years:
Activating a subscription is easy: with a bank card already attached, all you need to do is to verify your purchase with Face or Touch IDs.
As a consequence, subscriptions became a target for scammers. The scheme was simple: a paywall was set up during the onboarding in the scammer’s app and traffic was bought. A user would then be tricked into buying a subscription for a completely useless functionality. (Users then would most likely delete an app but the subscription will be automatically renewed nevertheless). The scheme worked well even with low traffic budgets.
In 2018 the App Store scamming scheme became widely discussed. Apple didn’t hesitate to fix the issue: the subscription process was changed to be more transparent while the reviewing process became more vigorous. For instance, now, when you are deleting an app with an active subscription, a pop-up appears to remind you about the subscription. As a result of Apple’s measures, users started to churn. Many companies made it only because of the “heavy tail” — users who forgot about a subscription and removed an app before updating to iOS 13. With Apple being stricter, analysts anticipate a tougher life for apps with subscriptions in the future.
In Adapty, we can see that the situation develops in a forecasted way:
Problems stated above are easily converted into more manageable tasks. Before Adapty, we’ve developed a mobile app with subscriptions and had several associated issues:
We developed most tools in-house and they required constant support. Because of system complexity, there were two times when subscriptions didn’t work at all for a couple of days (clap if you have the same issues)
After inventing the wheel, we have talked with fellow developers and realized that majority had the same problems. As a result, we decided to build Adapty as a standalone product.
It is hard to develop an app, but it is even harder to monetize it. We are developing Adapty to help developers monetize applications so they can concentrate on the product. We have decided to start with in-app A/B testing for paywalls, and here is what we have now:
Connect Apple Sales Reports and instantly get analytics and reports. You will see a dashboard with your app’s metrics: MRR, churn rate, cancelation reasons, and much more. Also, you will receive reports with daily, weekly, or monthly performance info via email or Slack.
With installing SDK great features unlock such as purchases framework, A/B testing for paywalls, promo campaigns in push notifications. SDK is literally a proxy for API and it weights 164kb (source code). It’s a 100% open source.
SDK works in two modes:
A paywall in Adapty behaves like a container — a placeholder on the device with all the content stored and managed from the server.
After the experiment, Adapty performs stats tests and metrics calculations:
Tests also have versioning, so different configurations do not conflict with each other.
Adapty incapsulates products from various platforms into one inner product. This means that purchases on different platforms are represented as makePurchase(<productid>), where productID is the same for all platforms.</productid>
Adapty generates 13 event types and can redirect them to other services. For instance, you can integrate it with AppsFlyer and pay media agency for traffic using a CPA model.
You can also change user ID for each analytics system separately.
Sometimes users message the support about broken or bugged subscriptions, the purchases not going through, or other payment difficulties. In this case, to help a user, it is important to understand who he is and what is his purchase history. Such support is done even by the Calm app. Adapty helps to make this process easier.
You can look up full information about each user.
Moreover, you can manage user access level in the app and choose what functionality is available for him. Imagine you had a technical issue in the app and someone posted a bad review in the App Store as a result. To make the user happy again, you can unlock free premium access for a limited time.
The majority of users do not pay, but you can convert them into paying ones. Retargeting traffic is a very expensive tool for such a task and usually puts a strain on the economy. But sending a promo in the push notification is free.
In Adapty you can send push notifications to user cohorts that have completed a certain action.
Integrating Adapty takes about 10 minutes without an SDK and an hour with it. As a result, you get analytics and a full infrastructure for your subscriptions, including A/B tests and promotional push notifications.
As an alternative, to get similar functionality, you can create a stack including a server, Firebase, Amplitude, Excel, and so on. Such a stack is time-consuming to create and it needs constant support.
Our data shows that after A/B testing your purchases, depending on the volume, the revenue can grow up to 40%.
Adapty proved to be stable for more than half a year. Companies buy traffic and pay agencies using our events, handle in-app purchases, and create A/B tests. Recently we have released all features and were featured on Product Hunt.
If you think Adapty can help you with development, marketing or monetization, reach out to me at firstname.lastname@example.org or on Facebook. We are happy to provide you with a demo, help with creating an account and integrating the SDK.