iOS SDK overview

Welcome! We’re here to make in-app purchases a breeze 🚀

We’ve built the Adapty iOS SDK to take the headache out of in-app purchases so you can focus on what you do best – building amazing apps. Here’s what we handle for you:

• Handle purchases, receipt validation, and subscription management out of the box
• Create and test flows and paywalls without app updates
• Get detailed purchase analytics with zero setup - cohorts, LTV, churn, and funnel analysis included
• Keep the user subscription status always up to date across app sessions and devices
• Integrate your app with marketing attribution and analytics services using just one line of code

Get started

Here’s what we’ll cover in the integration guide:

1. Install & configure SDK: Add the SDK as a dependency to your project and activate it in the code.
2. Enable purchases through flows: Set up the purchase flow so users can buy products. To build your own UI, see Implement paywalls manually instead.
3. Check the subscription status: Automatically check the user’s subscription state and control their access to paid content.
4. Identify users (optional): Associate users with their Adapty profiles to ensure their data is stored consistently across devices.

See it in action

Want to see how it all comes together? We’ve got you covered:

• Sample apps: Check out our complete examples that demonstrate the full setup

Main concepts

Before diving into the code, let’s get familiar with the key concepts that make Adapty work.

The beauty of Adapty’s approach is that only placements are hardcoded in your app. Everything else – products, paywall designs, pricing, and offers – can be managed flexibly from the Adapty dashboard without app updates:

1. Product - Anything available for purchase in your app – subscription, consumable product, or lifetime access.

2. Flow or paywall - Products bundled with configuration, attached to a placement. Two flavors:

   • Flow - Visual, no-code interface built in Flow Builder. Adapty renders the UI and handles the purchase for you.
   • Paywall - No visual config; you build the UI in your own code and call makePurchase yourself. See Implement paywalls manually.

   In SDK code, both are retrieved via the same getFlow method.

3. Placement - A strategic point in your user journey where you want to show a flow or paywall. Think of placements as the “where” and “when” of your monetization strategy. Common placements include:

   • main - Your primary paywall location
   • onboarding - Shown during the user onboarding flow
   • settings - Accessible from your app’s settings

   Start with the basics like main or onboarding for your first integration, then think about where else in your app users might be ready to purchase.

4. Profile - When users purchase a product, their profile is assigned an access level which you use to define access to paid features.