Introduction

We can definitely make app monetization easier.

In today’s fast-moving app world, building a great product is just half the work — the real challenge is turning it into steady income. For Flutter developers, setting up in-app purchases (IAP) across iOS and Android is tricky, time-consuming, and filled with edge cases. That’s where RevenueCat steps in.

This guide is for developers, indie makers, and product folks who want to simplify IAP setup and grow revenue smarter. Whether you're building your first subscription app or improving an existing flow, you’ll find practical tips, tech know-how, and growth ideas based on real-world experience — all built on Flutter and powered by RevenueCat.

We can definitely make app monetization easier.

In today’s fast-moving app world, building a great product is just half the work — the real challenge is turning it into steady income. For Flutter developers, setting up in-app purchases (IAP) across iOS and Android is tricky, time-consuming, and filled with edge cases. That’s where RevenueCat steps in.

This guide is for developers, indie makers, and product folks who want to simplify IAP setup and grow revenue smarter. Whether you're building your first subscription app or improving an existing flow, you’ll find practical tips, tech know-how, and growth ideas based on real-world experience — all built on Flutter and powered by RevenueCat.

We can definitely make app monetization easier.

In today’s fast-moving app world, building a great product is just half the work — the real challenge is turning it into steady income. For Flutter developers, setting up in-app purchases (IAP) across iOS and Android is tricky, time-consuming, and filled with edge cases. That’s where RevenueCat steps in.

This guide is for developers, indie makers, and product folks who want to simplify IAP setup and grow revenue smarter. Whether you're building your first subscription app or improving an existing flow, you’ll find practical tips, tech know-how, and growth ideas based on real-world experience — all built on Flutter and powered by RevenueCat.

We can definitely make app monetization easier.

In today’s fast-moving app world, building a great product is just half the work — the real challenge is turning it into steady income. For Flutter developers, setting up in-app purchases (IAP) across iOS and Android is tricky, time-consuming, and filled with edge cases. That’s where RevenueCat steps in.

This guide is for developers, indie makers, and product folks who want to simplify IAP setup and grow revenue smarter. Whether you're building your first subscription app or improving an existing flow, you’ll find practical tips, tech know-how, and growth ideas based on real-world experience — all built on Flutter and powered by RevenueCat.

The Challenge: IAP Complexity

I want to start by sharing this image — and honestly, it might hit a little too close to home. Feels like everyday life as a developer, right?

You’ve likely been using LLM tools like ChatGPT to help write code, generate UI, or even draft documentation. These tools have changed the game.

Today, all it takes is one late-night idea. A few focused evenings later, you've got a working product. By morning, you’re posting about it on X or Threads, inviting friends to test it out.

Welcome to what I like to call the vibe-to-shipping era — if you've got the vibe, you can ship. And once you can ship, there’s a real shot at making money from it.

So here’s the question:
👉 When you already have the vibe, the product, and your first users... what’s next?

If you're building a mobile product and want users to pay for the value you're creating, In-App Purchases (IAP) are often your first real monetization challenge.

In this article, I’ll show how we use RevenueCat to simplify that journey — and turn a great product into a sustainable business.

What is In-App Purchase(IAP)？

In-App Purchases (IAP) let users buy digital items directly within your app. They’re one of the most common ways to monetize mobile products, and come in three main types, each serving different user needs:

1. Consumables

These are items that can be used up and bought again. Think of game currency, energy boosts, or one-time hints. Once used, they’re gone, so users can purchase them repeatedly.

2. Non-Consumables

A one-time purchase that users own forever. These could be premium features, removing ads, or unlocking a special tool.

3. Subscriptions

Access to premium features over time — monthly, quarterly, or yearly. Subscriptions usually auto-renew and are ideal for ongoing value like Pro features or exclusive content.

Each type has its role. Choosing the right one depends on your app’s value, audience, and how you want users to experience your product.

I want to start by sharing this image — and honestly, it might hit a little too close to home. Feels like everyday life as a developer, right?

You’ve likely been using LLM tools like ChatGPT to help write code, generate UI, or even draft documentation. These tools have changed the game.

Today, all it takes is one late-night idea. A few focused evenings later, you've got a working product. By morning, you’re posting about it on X or Threads, inviting friends to test it out.

Welcome to what I like to call the vibe-to-shipping era — if you've got the vibe, you can ship. And once you can ship, there’s a real shot at making money from it.

So here’s the question:
👉 When you already have the vibe, the product, and your first users... what’s next?

If you're building a mobile product and want users to pay for the value you're creating, In-App Purchases (IAP) are often your first real monetization challenge.

In this article, I’ll show how we use RevenueCat to simplify that journey — and turn a great product into a sustainable business.

What is In-App Purchase(IAP)？

In-App Purchases (IAP) let users buy digital items directly within your app. They’re one of the most common ways to monetize mobile products, and come in three main types, each serving different user needs:

1. Consumables

These are items that can be used up and bought again. Think of game currency, energy boosts, or one-time hints. Once used, they’re gone, so users can purchase them repeatedly.

2. Non-Consumables

A one-time purchase that users own forever. These could be premium features, removing ads, or unlocking a special tool.

3. Subscriptions

Access to premium features over time — monthly, quarterly, or yearly. Subscriptions usually auto-renew and are ideal for ongoing value like Pro features or exclusive content.

Each type has its role. Choosing the right one depends on your app’s value, audience, and how you want users to experience your product.

I want to start by sharing this image — and honestly, it might hit a little too close to home. Feels like everyday life as a developer, right?

You’ve likely been using LLM tools like ChatGPT to help write code, generate UI, or even draft documentation. These tools have changed the game.

Today, all it takes is one late-night idea. A few focused evenings later, you've got a working product. By morning, you’re posting about it on X or Threads, inviting friends to test it out.

Welcome to what I like to call the vibe-to-shipping era — if you've got the vibe, you can ship. And once you can ship, there’s a real shot at making money from it.

So here’s the question:
👉 When you already have the vibe, the product, and your first users... what’s next?

If you're building a mobile product and want users to pay for the value you're creating, In-App Purchases (IAP) are often your first real monetization challenge.

In this article, I’ll show how we use RevenueCat to simplify that journey — and turn a great product into a sustainable business.

What is In-App Purchase(IAP)？

In-App Purchases (IAP) let users buy digital items directly within your app. They’re one of the most common ways to monetize mobile products, and come in three main types, each serving different user needs:

1. Consumables

These are items that can be used up and bought again. Think of game currency, energy boosts, or one-time hints. Once used, they’re gone, so users can purchase them repeatedly.

2. Non-Consumables

A one-time purchase that users own forever. These could be premium features, removing ads, or unlocking a special tool.

3. Subscriptions

Access to premium features over time — monthly, quarterly, or yearly. Subscriptions usually auto-renew and are ideal for ongoing value like Pro features or exclusive content.

Each type has its role. Choosing the right one depends on your app’s value, audience, and how you want users to experience your product.

I want to start by sharing this image — and honestly, it might hit a little too close to home. Feels like everyday life as a developer, right?

You’ve likely been using LLM tools like ChatGPT to help write code, generate UI, or even draft documentation. These tools have changed the game.

Today, all it takes is one late-night idea. A few focused evenings later, you've got a working product. By morning, you’re posting about it on X or Threads, inviting friends to test it out.

Welcome to what I like to call the vibe-to-shipping era — if you've got the vibe, you can ship. And once you can ship, there’s a real shot at making money from it.

So here’s the question:
👉 When you already have the vibe, the product, and your first users... what’s next?

If you're building a mobile product and want users to pay for the value you're creating, In-App Purchases (IAP) are often your first real monetization challenge.

In this article, I’ll show how we use RevenueCat to simplify that journey — and turn a great product into a sustainable business.

What is In-App Purchase(IAP)？

In-App Purchases (IAP) let users buy digital items directly within your app. They’re one of the most common ways to monetize mobile products, and come in three main types, each serving different user needs:

1. Consumables

These are items that can be used up and bought again. Think of game currency, energy boosts, or one-time hints. Once used, they’re gone, so users can purchase them repeatedly.

2. Non-Consumables

A one-time purchase that users own forever. These could be premium features, removing ads, or unlocking a special tool.

3. Subscriptions

Access to premium features over time — monthly, quarterly, or yearly. Subscriptions usually auto-renew and are ideal for ongoing value like Pro features or exclusive content.

Each type has its role. Choosing the right one depends on your app’s value, audience, and how you want users to experience your product.

Why Most Apps Use IAP Subscriptions?

Take a look around - many top-performing apps today rely on IAP subscriptions. But what makes this model so effective?

The biggest perk is predictable recurring revenue. Once users subscribe and add a payment method, the billing renews automatically. This helps boost retention and gives your team better control over planning and growth.

It’s not limited to indie makers - even big players like Notion and CapCut have adopted this model. So it’s not just a passing trend - it’s a reliable and scalable strategy for modern app monetization.

What’s the efficient way to turn it into a monetizable product?

RevenueCat!

The truth is, setting up IAP isn’t as easy as just adding a “Buy” button.
A lot is going on behind the scenes — validating receipts, handling errors, cancellations, and syncing subscriptions. Doing it all yourself can quickly become overwhelming.

That’s exactly why we use RevenueCat. It handles all the tough backend work, so we don’t have to build and maintain a full IAP system from scratch.

Design For Mobile Apps

RevenueCat is an all-in-one platform made just for mobile apps with subscriptions. It connects easily with Apple and Google, and handles the hard stuff — like receipt checks, server-side webhooks, and all those tricky background tasks. Ask ChatGPT to select 62 more words to run Humanizer.

Analytics

Even better — it gives you built-in analytics, like churn rate, monthly recurring revenue (MRR), active subscriptions, and more.

You get a clear view of your app’s performance over time.

Real-time Subscriber Insights

With RevenueCat, your team can stay on top of every subscriber’s status in real time — when they start, cancel, renew, upgrade, or change plans. You can fully understand every user.

Take a look around - many top-performing apps today rely on IAP subscriptions. But what makes this model so effective?

The biggest perk is predictable recurring revenue. Once users subscribe and add a payment method, the billing renews automatically. This helps boost retention and gives your team better control over planning and growth.

It’s not limited to indie makers - even big players like Notion and CapCut have adopted this model. So it’s not just a passing trend - it’s a reliable and scalable strategy for modern app monetization.

What’s the efficient way to turn it into a monetizable product?

RevenueCat!

The truth is, setting up IAP isn’t as easy as just adding a “Buy” button.
A lot is going on behind the scenes — validating receipts, handling errors, cancellations, and syncing subscriptions. Doing it all yourself can quickly become overwhelming.

That’s exactly why we use RevenueCat. It handles all the tough backend work, so we don’t have to build and maintain a full IAP system from scratch.

Design For Mobile Apps

RevenueCat is an all-in-one platform made just for mobile apps with subscriptions. It connects easily with Apple and Google, and handles the hard stuff — like receipt checks, server-side webhooks, and all those tricky background tasks. Ask ChatGPT to select 62 more words to run Humanizer.

Analytics

Even better — it gives you built-in analytics, like churn rate, monthly recurring revenue (MRR), active subscriptions, and more.

You get a clear view of your app’s performance over time.

Real-time Subscriber Insights

With RevenueCat, your team can stay on top of every subscriber’s status in real time — when they start, cancel, renew, upgrade, or change plans. You can fully understand every user.

Take a look around - many top-performing apps today rely on IAP subscriptions. But what makes this model so effective?

The biggest perk is predictable recurring revenue. Once users subscribe and add a payment method, the billing renews automatically. This helps boost retention and gives your team better control over planning and growth.

It’s not limited to indie makers - even big players like Notion and CapCut have adopted this model. So it’s not just a passing trend - it’s a reliable and scalable strategy for modern app monetization.

What’s the efficient way to turn it into a monetizable product?

RevenueCat!

The truth is, setting up IAP isn’t as easy as just adding a “Buy” button.
A lot is going on behind the scenes — validating receipts, handling errors, cancellations, and syncing subscriptions. Doing it all yourself can quickly become overwhelming.

That’s exactly why we use RevenueCat. It handles all the tough backend work, so we don’t have to build and maintain a full IAP system from scratch.

Design For Mobile Apps

RevenueCat is an all-in-one platform made just for mobile apps with subscriptions. It connects easily with Apple and Google, and handles the hard stuff — like receipt checks, server-side webhooks, and all those tricky background tasks. Ask ChatGPT to select 62 more words to run Humanizer.

Analytics

Even better — it gives you built-in analytics, like churn rate, monthly recurring revenue (MRR), active subscriptions, and more.

You get a clear view of your app’s performance over time.

Real-time Subscriber Insights

With RevenueCat, your team can stay on top of every subscriber’s status in real time — when they start, cancel, renew, upgrade, or change plans. You can fully understand every user.

Take a look around - many top-performing apps today rely on IAP subscriptions. But what makes this model so effective?

The biggest perk is predictable recurring revenue. Once users subscribe and add a payment method, the billing renews automatically. This helps boost retention and gives your team better control over planning and growth.

It’s not limited to indie makers - even big players like Notion and CapCut have adopted this model. So it’s not just a passing trend - it’s a reliable and scalable strategy for modern app monetization.

What’s the efficient way to turn it into a monetizable product?

RevenueCat!

The truth is, setting up IAP isn’t as easy as just adding a “Buy” button.
A lot is going on behind the scenes — validating receipts, handling errors, cancellations, and syncing subscriptions. Doing it all yourself can quickly become overwhelming.

That’s exactly why we use RevenueCat. It handles all the tough backend work, so we don’t have to build and maintain a full IAP system from scratch.

Design For Mobile Apps

RevenueCat is an all-in-one platform made just for mobile apps with subscriptions. It connects easily with Apple and Google, and handles the hard stuff — like receipt checks, server-side webhooks, and all those tricky background tasks. Ask ChatGPT to select 62 more words to run Humanizer.

Analytics

Even better — it gives you built-in analytics, like churn rate, monthly recurring revenue (MRR), active subscriptions, and more.

You get a clear view of your app’s performance over time.

Real-time Subscriber Insights

With RevenueCat, your team can stay on top of every subscriber’s status in real time — when they start, cancel, renew, upgrade, or change plans. You can fully understand every user.

If We Do IAP — Flow

Let’s understand how the in-app purchase flow works. When building it yourself, you handle multiple parts: your app talks to Apple or Google Store SDKs, you validate receipts, and you need a backend to track user status. It’s not simple — it takes time and effort.

At every step, something can go wrong. Your app might face SDK errors. Payments may fail or get stuck. Your backend must stay updated and in sync with store data.

Each of these steps is sensitive and needs careful planning if you're managing IAPs manually.

📦 APP ↔ Store SDK

SDK integration error (initialization incomplete)
Wrong product ID
Error code not handled

🔄 Store SDK ↔ Apple/Google Store

Platform service delay
User cancellation, payment failure
Store response format changes have not kept up

🧾 Receipt validation (usually handled by the App Server)

The receipt was forged
The authentication API is invalid or formatted incorrectly
Different receipt formats on different platforms lead to processing errors

💾 App Server ↔ User Status Management

Permission update failed
Server crash causes data to become out of sync
No instant notification of app status changes

RevenueCat IAP Flow

After switching to RevenueCat, our development and maintenance load dropped significantly.

Once a purchase is triggered, RevenueCat handles everything, from validating receipts to updating subscription status and syncing across platforms.

All we do is listen for success or failure, then unlock the right feature or access.

No more building complex IAP systems from scratch. You can now focus on what truly matters, your product and your users.

Let’s understand how the in-app purchase flow works. When building it yourself, you handle multiple parts: your app talks to Apple or Google Store SDKs, you validate receipts, and you need a backend to track user status. It’s not simple — it takes time and effort.

At every step, something can go wrong. Your app might face SDK errors. Payments may fail or get stuck. Your backend must stay updated and in sync with store data.

Each of these steps is sensitive and needs careful planning if you're managing IAPs manually.

📦 APP ↔ Store SDK

SDK integration error (initialization incomplete)
Wrong product ID
Error code not handled

🔄 Store SDK ↔ Apple/Google Store

Platform service delay
User cancellation, payment failure
Store response format changes have not kept up

🧾 Receipt validation (usually handled by the App Server)

The receipt was forged
The authentication API is invalid or formatted incorrectly
Different receipt formats on different platforms lead to processing errors

💾 App Server ↔ User Status Management

Permission update failed
Server crash causes data to become out of sync
No instant notification of app status changes

RevenueCat IAP Flow

After switching to RevenueCat, our development and maintenance load dropped significantly.

Once a purchase is triggered, RevenueCat handles everything, from validating receipts to updating subscription status and syncing across platforms.

All we do is listen for success or failure, then unlock the right feature or access.

No more building complex IAP systems from scratch. You can now focus on what truly matters, your product and your users.

Let’s understand how the in-app purchase flow works. When building it yourself, you handle multiple parts: your app talks to Apple or Google Store SDKs, you validate receipts, and you need a backend to track user status. It’s not simple — it takes time and effort.

At every step, something can go wrong. Your app might face SDK errors. Payments may fail or get stuck. Your backend must stay updated and in sync with store data.

Each of these steps is sensitive and needs careful planning if you're managing IAPs manually.

📦 APP ↔ Store SDK

SDK integration error (initialization incomplete)
Wrong product ID
Error code not handled

🔄 Store SDK ↔ Apple/Google Store

Platform service delay
User cancellation, payment failure
Store response format changes have not kept up

🧾 Receipt validation (usually handled by the App Server)

The receipt was forged
The authentication API is invalid or formatted incorrectly
Different receipt formats on different platforms lead to processing errors

💾 App Server ↔ User Status Management

Permission update failed
Server crash causes data to become out of sync
No instant notification of app status changes

RevenueCat IAP Flow

After switching to RevenueCat, our development and maintenance load dropped significantly.

Once a purchase is triggered, RevenueCat handles everything, from validating receipts to updating subscription status and syncing across platforms.

All we do is listen for success or failure, then unlock the right feature or access.

No more building complex IAP systems from scratch. You can now focus on what truly matters, your product and your users.

Let’s understand how the in-app purchase flow works. When building it yourself, you handle multiple parts: your app talks to Apple or Google Store SDKs, you validate receipts, and you need a backend to track user status. It’s not simple — it takes time and effort.

At every step, something can go wrong. Your app might face SDK errors. Payments may fail or get stuck. Your backend must stay updated and in sync with store data.

Each of these steps is sensitive and needs careful planning if you're managing IAPs manually.

📦 APP ↔ Store SDK

SDK integration error (initialization incomplete)
Wrong product ID
Error code not handled

🔄 Store SDK ↔ Apple/Google Store

Platform service delay
User cancellation, payment failure
Store response format changes have not kept up

🧾 Receipt validation (usually handled by the App Server)

The receipt was forged
The authentication API is invalid or formatted incorrectly
Different receipt formats on different platforms lead to processing errors

💾 App Server ↔ User Status Management

Permission update failed
Server crash causes data to become out of sync
No instant notification of app status changes

RevenueCat IAP Flow

After switching to RevenueCat, our development and maintenance load dropped significantly.

Once a purchase is triggered, RevenueCat handles everything, from validating receipts to updating subscription status and syncing across platforms.

All we do is listen for success or failure, then unlock the right feature or access.

No more building complex IAP systems from scratch. You can now focus on what truly matters, your product and your users.

Basic Setup: Add Products in Stores & RevenueCat

Before integrating IAP, the first step is to define your products in both the app stores and RevenueCat. Each one represents something users can buy inside your app.

Make sure to give each product a unique Product ID - it can’t be changed later. Use clear, consistent names like “v1,” “promo,” or “spring2024” to make future tracking easier.

Next: Let’s talk about one of the core elements in RevenueCat — the Package.

1️⃣ Package

A Package is used to group the same product across different platforms.

This ensures that no matter where your user makes a purchase — Apple, Google, or even Stripe — it’s mapped back to the same logical item in your app. This cross-platform alignment makes handling purchases a lot smoother.

Example: Package A → Product A on all platforms

2️⃣ Entitlement

Entitlement defines what feature or access is granted after a purchase.

The second key concept in RevenueCat is the Entitlement. It defines what a user gets after a purchase, like premium access or ad removal. This makes it easy to manage what features each purchase unlocks.

Example: Buying product A might grant the “Gold” entitlement, and buying product C could grant “Diamond”

Remind: If it is a consumable product (such as game currency, points), it should generally not be bound to an Entitlement. This is different from the design concept of consumables (it can be purchased multiple times, and it is gone once it is used up).

3️⃣ Offering

Offering is the set of products shown to users on the paywall.

The last key concept is the Offering. It defines what users see when they’re deciding to subscribe. An Offering can include multiple packages, like “Pro Monthly” and “Pro Yearly — 30% Off.” This structure is perfect for testing price points and promotional campaigns.

Example: Astandard Pro plan and a special New Year deal.

You can use an API or feature flag to decide which offering group to display and dynamically switch product combinations. Allows you to flexibly switch which group of products to display to users, such as limited-time annual plans, student plans, etc.

Once Offerings are in place, we can move into building the actual paywall and subscription flow.

Before integrating IAP, the first step is to define your products in both the app stores and RevenueCat. Each one represents something users can buy inside your app.

Make sure to give each product a unique Product ID - it can’t be changed later. Use clear, consistent names like “v1,” “promo,” or “spring2024” to make future tracking easier.

Next: Let’s talk about one of the core elements in RevenueCat — the Package.

1️⃣ Package

A Package is used to group the same product across different platforms.

This ensures that no matter where your user makes a purchase — Apple, Google, or even Stripe — it’s mapped back to the same logical item in your app. This cross-platform alignment makes handling purchases a lot smoother.

Example: Package A → Product A on all platforms

2️⃣ Entitlement

Entitlement defines what feature or access is granted after a purchase.

The second key concept in RevenueCat is the Entitlement. It defines what a user gets after a purchase, like premium access or ad removal. This makes it easy to manage what features each purchase unlocks.

Example: Buying product A might grant the “Gold” entitlement, and buying product C could grant “Diamond”

Remind: If it is a consumable product (such as game currency, points), it should generally not be bound to an Entitlement. This is different from the design concept of consumables (it can be purchased multiple times, and it is gone once it is used up).

3️⃣ Offering

Offering is the set of products shown to users on the paywall.

The last key concept is the Offering. It defines what users see when they’re deciding to subscribe. An Offering can include multiple packages, like “Pro Monthly” and “Pro Yearly — 30% Off.” This structure is perfect for testing price points and promotional campaigns.

Example: Astandard Pro plan and a special New Year deal.

You can use an API or feature flag to decide which offering group to display and dynamically switch product combinations. Allows you to flexibly switch which group of products to display to users, such as limited-time annual plans, student plans, etc.

Once Offerings are in place, we can move into building the actual paywall and subscription flow.

Before integrating IAP, the first step is to define your products in both the app stores and RevenueCat. Each one represents something users can buy inside your app.

Make sure to give each product a unique Product ID - it can’t be changed later. Use clear, consistent names like “v1,” “promo,” or “spring2024” to make future tracking easier.

Next: Let’s talk about one of the core elements in RevenueCat — the Package.

1️⃣ Package

A Package is used to group the same product across different platforms.

This ensures that no matter where your user makes a purchase — Apple, Google, or even Stripe — it’s mapped back to the same logical item in your app. This cross-platform alignment makes handling purchases a lot smoother.

Example: Package A → Product A on all platforms

2️⃣ Entitlement

Entitlement defines what feature or access is granted after a purchase.

The second key concept in RevenueCat is the Entitlement. It defines what a user gets after a purchase, like premium access or ad removal. This makes it easy to manage what features each purchase unlocks.

Example: Buying product A might grant the “Gold” entitlement, and buying product C could grant “Diamond”

Remind: If it is a consumable product (such as game currency, points), it should generally not be bound to an Entitlement. This is different from the design concept of consumables (it can be purchased multiple times, and it is gone once it is used up).

3️⃣ Offering

Offering is the set of products shown to users on the paywall.

The last key concept is the Offering. It defines what users see when they’re deciding to subscribe. An Offering can include multiple packages, like “Pro Monthly” and “Pro Yearly — 30% Off.” This structure is perfect for testing price points and promotional campaigns.

Example: Astandard Pro plan and a special New Year deal.

You can use an API or feature flag to decide which offering group to display and dynamically switch product combinations. Allows you to flexibly switch which group of products to display to users, such as limited-time annual plans, student plans, etc.

Once Offerings are in place, we can move into building the actual paywall and subscription flow.

Before integrating IAP, the first step is to define your products in both the app stores and RevenueCat. Each one represents something users can buy inside your app.

Make sure to give each product a unique Product ID - it can’t be changed later. Use clear, consistent names like “v1,” “promo,” or “spring2024” to make future tracking easier.

Next: Let’s talk about one of the core elements in RevenueCat — the Package.

1️⃣ Package

A Package is used to group the same product across different platforms.

This ensures that no matter where your user makes a purchase — Apple, Google, or even Stripe — it’s mapped back to the same logical item in your app. This cross-platform alignment makes handling purchases a lot smoother.

Example: Package A → Product A on all platforms

2️⃣ Entitlement

Entitlement defines what feature or access is granted after a purchase.

The second key concept in RevenueCat is the Entitlement. It defines what a user gets after a purchase, like premium access or ad removal. This makes it easy to manage what features each purchase unlocks.

Example: Buying product A might grant the “Gold” entitlement, and buying product C could grant “Diamond”

Remind: If it is a consumable product (such as game currency, points), it should generally not be bound to an Entitlement. This is different from the design concept of consumables (it can be purchased multiple times, and it is gone once it is used up).

3️⃣ Offering

Offering is the set of products shown to users on the paywall.

The last key concept is the Offering. It defines what users see when they’re deciding to subscribe. An Offering can include multiple packages, like “Pro Monthly” and “Pro Yearly — 30% Off.” This structure is perfect for testing price points and promotional campaigns.

Example: Astandard Pro plan and a special New Year deal.

You can use an API or feature flag to decide which offering group to display and dynamically switch product combinations. Allows you to flexibly switch which group of products to display to users, such as limited-time annual plans, student plans, etc.

Once Offerings are in place, we can move into building the actual paywall and subscription flow.

Integrating RevenueCat SDK in Flutter

Now we move into the implementation phase, and good news, it’s lightweight. The first step is to add the official RevenueCat Flutter SDK, called purchases_flutter, to your pubspec.yaml file.

💡 Initialize RevenueCat SDK

After adding the SDK, the next step is initialization. You just need to provide your API key. It’s a straightforward setup, no complicated configuration required.

Purchases.configure(
  PurchasesConfiguration('your_revenuecat_api_key'),
);

💡Fetch Offerings

Then, call getOfferings() to fetch the available Offerings. Typically, you’ll present these in your subscription UI. If you only have one Offering, you can simply call the current one to retrieve the default set.

final offerings = await Purchases.getOfferings();
// Default offering
final currentOffering = offerings.current;

💡 Fetch Packages from Offering

The next step is to access its available Packages. Each Package maps to a product ID on Apple, Google, like “monthly_pro”, “annual_promo”, etc. These are the actual items your users will subscribe to.

You can now display them in your UI however you like — cards, price tiles, or your own custom layout.

final availablePackages = offering.availablePackages;

// package for platform product
final monthlyPackage = offering.monthly;
final quarterlyPackage = offering.threeMonth;
final annualPackage = offering.annual;
final lifetimePackage = offering.lifetime;

💡 Purchase Package

We can let users start the purchase by tapping a button. Just call purchasePackage() and pass in the selected Package.

This handles everything: opening the store dialog, confirming payment, and verifying the purchase behind the scenes.

await Purchases.purchasePackage(package);

💡 Verify User Entitlements

Once a purchase is complete, it returns a CustomerInfo object. This contains the list of active entitlements for the current user. Based on this, you can unlock premium features.

Remember: always check entitlements rather than trying to track purchases manually.

final customerInfo = await Purchases.getCustomerInfo();

final activeEntitlements = customerInfo.entitlements.active;
final hasActiveEntitlements = activeEntitlements.isNotEmpty;

final isPlus = customerInfo.entitlements.all['plus']?.isActive ?? false;
final isPro = customerInfo.entitlements.all['pro']?.isActive ?? false;
final isVip = customerInfo.entitlements.all['vip']?.isActive ?? false;

🙋🏻 Sync Existing Subscribers

If you say: you’re migrating from your own IAP system or switching to RevenueCat mid-project, I also want to synchronize existing subscribers to RevenueCat.

That’s of course no problem. Use syncPurchases() to upload the user’s local purchase history from the device. After syncing, the user’s entitlements will also be updated accordingly.

Now we move into the implementation phase, and good news, it’s lightweight. The first step is to add the official RevenueCat Flutter SDK, called purchases_flutter, to your pubspec.yaml file.

💡 Initialize RevenueCat SDK

After adding the SDK, the next step is initialization. You just need to provide your API key. It’s a straightforward setup, no complicated configuration required.

Purchases.configure(
  PurchasesConfiguration('your_revenuecat_api_key'),
);

💡Fetch Offerings

Then, call getOfferings() to fetch the available Offerings. Typically, you’ll present these in your subscription UI. If you only have one Offering, you can simply call the current one to retrieve the default set.

final offerings = await Purchases.getOfferings();
// Default offering
final currentOffering = offerings.current;

💡 Fetch Packages from Offering

The next step is to access its available Packages. Each Package maps to a product ID on Apple, Google, like “monthly_pro”, “annual_promo”, etc. These are the actual items your users will subscribe to.

You can now display them in your UI however you like — cards, price tiles, or your own custom layout.

final availablePackages = offering.availablePackages;

// package for platform product
final monthlyPackage = offering.monthly;
final quarterlyPackage = offering.threeMonth;
final annualPackage = offering.annual;
final lifetimePackage = offering.lifetime;

💡 Purchase Package

We can let users start the purchase by tapping a button. Just call purchasePackage() and pass in the selected Package.

This handles everything: opening the store dialog, confirming payment, and verifying the purchase behind the scenes.

await Purchases.purchasePackage(package);

💡 Verify User Entitlements

Once a purchase is complete, it returns a CustomerInfo object. This contains the list of active entitlements for the current user. Based on this, you can unlock premium features.

Remember: always check entitlements rather than trying to track purchases manually.

final customerInfo = await Purchases.getCustomerInfo();

final activeEntitlements = customerInfo.entitlements.active;
final hasActiveEntitlements = activeEntitlements.isNotEmpty;

final isPlus = customerInfo.entitlements.all['plus']?.isActive ?? false;
final isPro = customerInfo.entitlements.all['pro']?.isActive ?? false;
final isVip = customerInfo.entitlements.all['vip']?.isActive ?? false;

🙋🏻 Sync Existing Subscribers

If you say: you’re migrating from your own IAP system or switching to RevenueCat mid-project, I also want to synchronize existing subscribers to RevenueCat.

That’s of course no problem. Use syncPurchases() to upload the user’s local purchase history from the device. After syncing, the user’s entitlements will also be updated accordingly.

Now we move into the implementation phase, and good news, it’s lightweight. The first step is to add the official RevenueCat Flutter SDK, called purchases_flutter, to your pubspec.yaml file.

💡 Initialize RevenueCat SDK

After adding the SDK, the next step is initialization. You just need to provide your API key. It’s a straightforward setup, no complicated configuration required.

Purchases.configure(
  PurchasesConfiguration('your_revenuecat_api_key'),
);

💡Fetch Offerings

Then, call getOfferings() to fetch the available Offerings. Typically, you’ll present these in your subscription UI. If you only have one Offering, you can simply call the current one to retrieve the default set.

final offerings = await Purchases.getOfferings();
// Default offering
final currentOffering = offerings.current;

💡 Fetch Packages from Offering

The next step is to access its available Packages. Each Package maps to a product ID on Apple, Google, like “monthly_pro”, “annual_promo”, etc. These are the actual items your users will subscribe to.

You can now display them in your UI however you like — cards, price tiles, or your own custom layout.

final availablePackages = offering.availablePackages;

// package for platform product
final monthlyPackage = offering.monthly;
final quarterlyPackage = offering.threeMonth;
final annualPackage = offering.annual;
final lifetimePackage = offering.lifetime;

💡 Purchase Package

We can let users start the purchase by tapping a button. Just call purchasePackage() and pass in the selected Package.

This handles everything: opening the store dialog, confirming payment, and verifying the purchase behind the scenes.

await Purchases.purchasePackage(package);

💡 Verify User Entitlements

Once a purchase is complete, it returns a CustomerInfo object. This contains the list of active entitlements for the current user. Based on this, you can unlock premium features.

Remember: always check entitlements rather than trying to track purchases manually.

final customerInfo = await Purchases.getCustomerInfo();

final activeEntitlements = customerInfo.entitlements.active;
final hasActiveEntitlements = activeEntitlements.isNotEmpty;

final isPlus = customerInfo.entitlements.all['plus']?.isActive ?? false;
final isPro = customerInfo.entitlements.all['pro']?.isActive ?? false;
final isVip = customerInfo.entitlements.all['vip']?.isActive ?? false;

🙋🏻 Sync Existing Subscribers

If you say: you’re migrating from your own IAP system or switching to RevenueCat mid-project, I also want to synchronize existing subscribers to RevenueCat.

That’s of course no problem. Use syncPurchases() to upload the user’s local purchase history from the device. After syncing, the user’s entitlements will also be updated accordingly.

Now we move into the implementation phase, and good news, it’s lightweight. The first step is to add the official RevenueCat Flutter SDK, called purchases_flutter, to your pubspec.yaml file.

💡 Initialize RevenueCat SDK

After adding the SDK, the next step is initialization. You just need to provide your API key. It’s a straightforward setup, no complicated configuration required.

Purchases.configure(
  PurchasesConfiguration('your_revenuecat_api_key'),
);

💡Fetch Offerings

Then, call getOfferings() to fetch the available Offerings. Typically, you’ll present these in your subscription UI. If you only have one Offering, you can simply call the current one to retrieve the default set.

final offerings = await Purchases.getOfferings();
// Default offering
final currentOffering = offerings.current;

💡 Fetch Packages from Offering

The next step is to access its available Packages. Each Package maps to a product ID on Apple, Google, like “monthly_pro”, “annual_promo”, etc. These are the actual items your users will subscribe to.

You can now display them in your UI however you like — cards, price tiles, or your own custom layout.

final availablePackages = offering.availablePackages;

// package for platform product
final monthlyPackage = offering.monthly;
final quarterlyPackage = offering.threeMonth;
final annualPackage = offering.annual;
final lifetimePackage = offering.lifetime;

💡 Purchase Package

We can let users start the purchase by tapping a button. Just call purchasePackage() and pass in the selected Package.

This handles everything: opening the store dialog, confirming payment, and verifying the purchase behind the scenes.

await Purchases.purchasePackage(package);

💡 Verify User Entitlements

Once a purchase is complete, it returns a CustomerInfo object. This contains the list of active entitlements for the current user. Based on this, you can unlock premium features.

Remember: always check entitlements rather than trying to track purchases manually.

final customerInfo = await Purchases.getCustomerInfo();

final activeEntitlements = customerInfo.entitlements.active;
final hasActiveEntitlements = activeEntitlements.isNotEmpty;

final isPlus = customerInfo.entitlements.all['plus']?.isActive ?? false;
final isPro = customerInfo.entitlements.all['pro']?.isActive ?? false;
final isVip = customerInfo.entitlements.all['vip']?.isActive ?? false;

🙋🏻 Sync Existing Subscribers

If you say: you’re migrating from your own IAP system or switching to RevenueCat mid-project, I also want to synchronize existing subscribers to RevenueCat.

That’s of course no problem. Use syncPurchases() to upload the user’s local purchase history from the device. After syncing, the user’s entitlements will also be updated accordingly.

Congrats!

From here, with RevenueCat integrated, your Flutter app is ready to start monetizing and welcome its first paying user.

Can it get any easier?

At this point, some developers might ask — Can it get even easier? What if I don’t want to spend time designing my paywall UI? Maybe I just want something that works out of the box and lets me validate ideas quickly.

Well, RevenueCat has something for that, too.

It’s Paywall🧱

Visual Paywall: Build Less, Sell More
Paywall is RevenueCat’s visual editor for subscription UI — think of it like Figma, but for monetization. Just drag components, link packages, adjust styles, and you’re live.

It’s ideal for quick testing, lazy devs, or vibe coders who want to ship fast without crafting a custom UI.

Use RevenueCatUI.presentPaywall() to show the paywall.
Use RevenueCatUI.presentPaywallIfNeeded("pro") to show it only when needed.
Or embed PaywallView into your own UI and connect callbacks for full control.

void presentPaywall() async {
  final paywallResult = await RevenueCatUI.presentPaywall();
  log('Paywall result: $paywallResult');
}

void presentPaywallIfNeeded() async {
  final paywallResult = await RevenueCatUI.presentPaywallIfNeeded("pro");
  log('Paywall result: $paywallResult');
}

Embed PaywallView in your custom widget.

@override
Widget build(BuildContext context) {
  return Scaffold(
    body: SafeArea(
      child: Center(
        child: PaywallView(
          offering: offering, // Optional Offering object obtained through getOfferings
          onRestoreCompleted: (CustomerInfo customerInfo) {
            // Optional listener. Called when a restore has been completed.
            // This may be called even if no entitlements have been granted.
          } 
          onDismiss: () {
            // Dismiss the paywall, i.e. remove the view, navigate to another screen, etc.
            // Will be called when the close button is pressed (if enabled) or when a purchase succeeds.
          },
        ),
      ),
    ),
  );
}

At the same time, you can use the provided callbacks to react to user operations. Available ones are:

onPurchaseStarted
onPurchaseCompleted
onPurchaseError
onRestoreCompleted
onRestoreError
onDismiss

From here, with RevenueCat integrated, your Flutter app is ready to start monetizing and welcome its first paying user.

Can it get any easier?

At this point, some developers might ask — Can it get even easier? What if I don’t want to spend time designing my paywall UI? Maybe I just want something that works out of the box and lets me validate ideas quickly.

Well, RevenueCat has something for that, too.

It’s Paywall🧱

Visual Paywall: Build Less, Sell More
Paywall is RevenueCat’s visual editor for subscription UI — think of it like Figma, but for monetization. Just drag components, link packages, adjust styles, and you’re live.

It’s ideal for quick testing, lazy devs, or vibe coders who want to ship fast without crafting a custom UI.

Use RevenueCatUI.presentPaywall() to show the paywall.
Use RevenueCatUI.presentPaywallIfNeeded("pro") to show it only when needed.
Or embed PaywallView into your own UI and connect callbacks for full control.

void presentPaywall() async {
  final paywallResult = await RevenueCatUI.presentPaywall();
  log('Paywall result: $paywallResult');
}

void presentPaywallIfNeeded() async {
  final paywallResult = await RevenueCatUI.presentPaywallIfNeeded("pro");
  log('Paywall result: $paywallResult');
}

Embed PaywallView in your custom widget.

@override
Widget build(BuildContext context) {
  return Scaffold(
    body: SafeArea(
      child: Center(
        child: PaywallView(
          offering: offering, // Optional Offering object obtained through getOfferings
          onRestoreCompleted: (CustomerInfo customerInfo) {
            // Optional listener. Called when a restore has been completed.
            // This may be called even if no entitlements have been granted.
          } 
          onDismiss: () {
            // Dismiss the paywall, i.e. remove the view, navigate to another screen, etc.
            // Will be called when the close button is pressed (if enabled) or when a purchase succeeds.
          },
        ),
      ),
    ),
  );
}

At the same time, you can use the provided callbacks to react to user operations. Available ones are:

onPurchaseStarted
onPurchaseCompleted
onPurchaseError
onRestoreCompleted
onRestoreError
onDismiss

From here, with RevenueCat integrated, your Flutter app is ready to start monetizing and welcome its first paying user.

Can it get any easier?

At this point, some developers might ask — Can it get even easier? What if I don’t want to spend time designing my paywall UI? Maybe I just want something that works out of the box and lets me validate ideas quickly.

Well, RevenueCat has something for that, too.

It’s Paywall🧱

Visual Paywall: Build Less, Sell More
Paywall is RevenueCat’s visual editor for subscription UI — think of it like Figma, but for monetization. Just drag components, link packages, adjust styles, and you’re live.

It’s ideal for quick testing, lazy devs, or vibe coders who want to ship fast without crafting a custom UI.

Use RevenueCatUI.presentPaywall() to show the paywall.
Use RevenueCatUI.presentPaywallIfNeeded("pro") to show it only when needed.
Or embed PaywallView into your own UI and connect callbacks for full control.

void presentPaywall() async {
  final paywallResult = await RevenueCatUI.presentPaywall();
  log('Paywall result: $paywallResult');
}

void presentPaywallIfNeeded() async {
  final paywallResult = await RevenueCatUI.presentPaywallIfNeeded("pro");
  log('Paywall result: $paywallResult');
}

Embed PaywallView in your custom widget.

@override
Widget build(BuildContext context) {
  return Scaffold(
    body: SafeArea(
      child: Center(
        child: PaywallView(
          offering: offering, // Optional Offering object obtained through getOfferings
          onRestoreCompleted: (CustomerInfo customerInfo) {
            // Optional listener. Called when a restore has been completed.
            // This may be called even if no entitlements have been granted.
          } 
          onDismiss: () {
            // Dismiss the paywall, i.e. remove the view, navigate to another screen, etc.
            // Will be called when the close button is pressed (if enabled) or when a purchase succeeds.
          },
        ),
      ),
    ),
  );
}

At the same time, you can use the provided callbacks to react to user operations. Available ones are:

onPurchaseStarted
onPurchaseCompleted
onPurchaseError
onRestoreCompleted
onRestoreError
onDismiss

From here, with RevenueCat integrated, your Flutter app is ready to start monetizing and welcome its first paying user.

Can it get any easier?

At this point, some developers might ask — Can it get even easier? What if I don’t want to spend time designing my paywall UI? Maybe I just want something that works out of the box and lets me validate ideas quickly.

Well, RevenueCat has something for that, too.

It’s Paywall🧱

Visual Paywall: Build Less, Sell More
Paywall is RevenueCat’s visual editor for subscription UI — think of it like Figma, but for monetization. Just drag components, link packages, adjust styles, and you’re live.

It’s ideal for quick testing, lazy devs, or vibe coders who want to ship fast without crafting a custom UI.

Use RevenueCatUI.presentPaywall() to show the paywall.
Use RevenueCatUI.presentPaywallIfNeeded("pro") to show it only when needed.
Or embed PaywallView into your own UI and connect callbacks for full control.

void presentPaywall() async {
  final paywallResult = await RevenueCatUI.presentPaywall();
  log('Paywall result: $paywallResult');
}

void presentPaywallIfNeeded() async {
  final paywallResult = await RevenueCatUI.presentPaywallIfNeeded("pro");
  log('Paywall result: $paywallResult');
}

Embed PaywallView in your custom widget.

@override
Widget build(BuildContext context) {
  return Scaffold(
    body: SafeArea(
      child: Center(
        child: PaywallView(
          offering: offering, // Optional Offering object obtained through getOfferings
          onRestoreCompleted: (CustomerInfo customerInfo) {
            // Optional listener. Called when a restore has been completed.
            // This may be called even if no entitlements have been granted.
          } 
          onDismiss: () {
            // Dismiss the paywall, i.e. remove the view, navigate to another screen, etc.
            // Will be called when the close button is pressed (if enabled) or when a purchase succeeds.
          },
        ),
      ),
    ),
  );
}

At the same time, you can use the provided callbacks to react to user operations. Available ones are:

onPurchaseStarted
onPurchaseCompleted
onPurchaseError
onRestoreCompleted
onRestoreError
onDismiss

Key Considerations & Policy Compliance

🙋 Subscription Switching: Upgrade & Downgrade in Apple

When users today switch plans during some discount periods, they will ask what will happen after subscribing.

Upgrade(Monthly to Yearly): When a user upgrades from a monthly to a yearly plan, Apple charges immediately and refunds or credits the unused portion of the current subscription.

Downgrade: the change takes effect only after the current subscription period ends, and the user will be charged the new price in the next billing cycle.

🙋 Subscription Switching: Upgrade & Downgrade in Google

🙋 Google Upgrade Flow Tip

Google supports multiple upgrade paths during free trials. We suggest using CHARGE_PRORATED_PRICE — it mimics Apple’s style by charging right away, giving instant access and fair refunds. Feels smoother for users.

🙋 Apple Sandbox Slowness

During development, you may notice Apple Sandbox taking 10+ seconds to finish purchases. It’s slower by design. Nothing’s wrong with your code — live production is much faster and smoother.

🙋 Track Subscription Cancellations

To detect cancellations or expired plans, use RevenueCat webhooks or call their API regularly. Mobile SDKs don’t show this directly. This ensures you sync entitlements, prevent misuse, and handle user access rights.

🙋 Platform Account Binding

Purchases are tied to Apple/Google accounts, not your app login. Users often get confused. Just let them tap “Restore Purchase” — it’ll recover past entitlements if the store account matches, regardless of app login.

🙋 Price Variations by Region

Product prices vary by region due to currency rates and taxes. So don’t panic if numbers look different — users in different countries may see a slightly higher or lower final price.

🙋 Restoring on New Devices

When users switch phones, use restorePurchases() to bring back their subscription. Always add a “Restore Purchases” button on the settings screen — it’s also recommended by Apple for good UX.

// RevenueCat
await Purchases.restorePurchases();

🙋 Different testing settings for IAP

iOS

Developer settings, set up SANDBOX account
Using TestFlight builds

Android

Create a license tester
Use internal or alpha testing versions

🙋 Subscription Switching: Upgrade & Downgrade in Apple

When users today switch plans during some discount periods, they will ask what will happen after subscribing.

Upgrade(Monthly to Yearly): When a user upgrades from a monthly to a yearly plan, Apple charges immediately and refunds or credits the unused portion of the current subscription.

Downgrade: the change takes effect only after the current subscription period ends, and the user will be charged the new price in the next billing cycle.

🙋 Subscription Switching: Upgrade & Downgrade in Google

🙋 Google Upgrade Flow Tip

Google supports multiple upgrade paths during free trials. We suggest using CHARGE_PRORATED_PRICE — it mimics Apple’s style by charging right away, giving instant access and fair refunds. Feels smoother for users.

🙋 Apple Sandbox Slowness

During development, you may notice Apple Sandbox taking 10+ seconds to finish purchases. It’s slower by design. Nothing’s wrong with your code — live production is much faster and smoother.

🙋 Track Subscription Cancellations

To detect cancellations or expired plans, use RevenueCat webhooks or call their API regularly. Mobile SDKs don’t show this directly. This ensures you sync entitlements, prevent misuse, and handle user access rights.

🙋 Platform Account Binding

Purchases are tied to Apple/Google accounts, not your app login. Users often get confused. Just let them tap “Restore Purchase” — it’ll recover past entitlements if the store account matches, regardless of app login.

🙋 Price Variations by Region

Product prices vary by region due to currency rates and taxes. So don’t panic if numbers look different — users in different countries may see a slightly higher or lower final price.

🙋 Restoring on New Devices

When users switch phones, use restorePurchases() to bring back their subscription. Always add a “Restore Purchases” button on the settings screen — it’s also recommended by Apple for good UX.

// RevenueCat
await Purchases.restorePurchases();

🙋 Different testing settings for IAP

iOS

Developer settings, set up SANDBOX account
Using TestFlight builds

Android

Create a license tester
Use internal or alpha testing versions

🙋 Subscription Switching: Upgrade & Downgrade in Apple

When users today switch plans during some discount periods, they will ask what will happen after subscribing.

Upgrade(Monthly to Yearly): When a user upgrades from a monthly to a yearly plan, Apple charges immediately and refunds or credits the unused portion of the current subscription.

Downgrade: the change takes effect only after the current subscription period ends, and the user will be charged the new price in the next billing cycle.

🙋 Subscription Switching: Upgrade & Downgrade in Google

🙋 Google Upgrade Flow Tip

Google supports multiple upgrade paths during free trials. We suggest using CHARGE_PRORATED_PRICE — it mimics Apple’s style by charging right away, giving instant access and fair refunds. Feels smoother for users.

🙋 Apple Sandbox Slowness

During development, you may notice Apple Sandbox taking 10+ seconds to finish purchases. It’s slower by design. Nothing’s wrong with your code — live production is much faster and smoother.

🙋 Track Subscription Cancellations

To detect cancellations or expired plans, use RevenueCat webhooks or call their API regularly. Mobile SDKs don’t show this directly. This ensures you sync entitlements, prevent misuse, and handle user access rights.

🙋 Platform Account Binding

Purchases are tied to Apple/Google accounts, not your app login. Users often get confused. Just let them tap “Restore Purchase” — it’ll recover past entitlements if the store account matches, regardless of app login.

🙋 Price Variations by Region

Product prices vary by region due to currency rates and taxes. So don’t panic if numbers look different — users in different countries may see a slightly higher or lower final price.

🙋 Restoring on New Devices

When users switch phones, use restorePurchases() to bring back their subscription. Always add a “Restore Purchases” button on the settings screen — it’s also recommended by Apple for good UX.

// RevenueCat
await Purchases.restorePurchases();

🙋 Different testing settings for IAP

iOS

Developer settings, set up SANDBOX account
Using TestFlight builds

Android

Create a license tester
Use internal or alpha testing versions

🙋 Subscription Switching: Upgrade & Downgrade in Apple

When users today switch plans during some discount periods, they will ask what will happen after subscribing.

Upgrade(Monthly to Yearly): When a user upgrades from a monthly to a yearly plan, Apple charges immediately and refunds or credits the unused portion of the current subscription.

Downgrade: the change takes effect only after the current subscription period ends, and the user will be charged the new price in the next billing cycle.

🙋 Subscription Switching: Upgrade & Downgrade in Google

🙋 Google Upgrade Flow Tip

Google supports multiple upgrade paths during free trials. We suggest using CHARGE_PRORATED_PRICE — it mimics Apple’s style by charging right away, giving instant access and fair refunds. Feels smoother for users.

🙋 Apple Sandbox Slowness

During development, you may notice Apple Sandbox taking 10+ seconds to finish purchases. It’s slower by design. Nothing’s wrong with your code — live production is much faster and smoother.

🙋 Track Subscription Cancellations

To detect cancellations or expired plans, use RevenueCat webhooks or call their API regularly. Mobile SDKs don’t show this directly. This ensures you sync entitlements, prevent misuse, and handle user access rights.

🙋 Platform Account Binding

Purchases are tied to Apple/Google accounts, not your app login. Users often get confused. Just let them tap “Restore Purchase” — it’ll recover past entitlements if the store account matches, regardless of app login.

🙋 Price Variations by Region

Product prices vary by region due to currency rates and taxes. So don’t panic if numbers look different — users in different countries may see a slightly higher or lower final price.

🙋 Restoring on New Devices

When users switch phones, use restorePurchases() to bring back their subscription. Always add a “Restore Purchases” button on the settings screen — it’s also recommended by Apple for good UX.

// RevenueCat
await Purchases.restorePurchases();

🙋 Different testing settings for IAP

iOS

Developer settings, set up SANDBOX account
Using TestFlight builds

Android

Create a license tester
Use internal or alpha testing versions

IAP Tips & Sales Strategies

💡 IAP Tips & Sales Strategies

Boosting in-app revenue isn’t about pressure — it’s about smart moves. Here are a few practical strategies that can drive real results.

🪝 Use Webhooks to Stay in Sync

Webhooks are your backstage crew. When a user cancels, upgrades, or gets refunded, you can instantly react — update databases, trigger emails, or send push notifications. It keeps your user data fresh and your actions timely.

🤩 Create a Value-First Experience

Let users feel the Pro experience. Don’t just show a list of features — show the result.
Let them try it. In our product HerFIT, we offer a trial with real results in 3 months. That connection makes users say, “I can’t go back.”
Let them see the value before they pay.

🧠 Sales Hooks That Work

Add FOMO: Limited-time discounts with countdowns drive urgency.
Catch churn: Offer exit discounts or quick surveys when users cancel.
Target behavior: Track users who check the paywall often — send them tailored offers to help them convert.

Every touchpoint is an opportunity to earn trust and revenue.

A great purchasing experience makes users feel excited to buy now like they’d miss out if they don’t rather than feeling pressured or forced.

🏛️ Stay Updated on Policy

One thing many devs miss: IAP isn’t just code — it’s also about rules, laws, and compliance.

App Store & Play Store Guidelines
Apple and Google often update their rules. A small change like “must show post-trial pricing” can mean reworking your whole flow. Stay alert.

Local Regulations Matter
Rules vary across countries. India, South Korea, EU — all have different tax laws, commission rates, and billing policies. Don’t assume it’s the same everywhere.

Service Provider Changes
Platforms like RevenueCat update webhooks and APIs often. Missing these updates can break flows or cost you revenue. Keep an eye on changelogs.

Whether you’re a dev or product lead, staying informed helps protect your revenue and keep the user journey smooth. Policy isn’t boring admin stuff — it shapes real experiences.

💡 IAP Tips & Sales Strategies

Boosting in-app revenue isn’t about pressure — it’s about smart moves. Here are a few practical strategies that can drive real results.

🪝 Use Webhooks to Stay in Sync

Webhooks are your backstage crew. When a user cancels, upgrades, or gets refunded, you can instantly react — update databases, trigger emails, or send push notifications. It keeps your user data fresh and your actions timely.

🤩 Create a Value-First Experience

Let users feel the Pro experience. Don’t just show a list of features — show the result.
Let them try it. In our product HerFIT, we offer a trial with real results in 3 months. That connection makes users say, “I can’t go back.”
Let them see the value before they pay.

🧠 Sales Hooks That Work

Add FOMO: Limited-time discounts with countdowns drive urgency.
Catch churn: Offer exit discounts or quick surveys when users cancel.
Target behavior: Track users who check the paywall often — send them tailored offers to help them convert.

Every touchpoint is an opportunity to earn trust and revenue.

A great purchasing experience makes users feel excited to buy now like they’d miss out if they don’t rather than feeling pressured or forced.

🏛️ Stay Updated on Policy

One thing many devs miss: IAP isn’t just code — it’s also about rules, laws, and compliance.

App Store & Play Store Guidelines
Apple and Google often update their rules. A small change like “must show post-trial pricing” can mean reworking your whole flow. Stay alert.

Local Regulations Matter
Rules vary across countries. India, South Korea, EU — all have different tax laws, commission rates, and billing policies. Don’t assume it’s the same everywhere.

Service Provider Changes
Platforms like RevenueCat update webhooks and APIs often. Missing these updates can break flows or cost you revenue. Keep an eye on changelogs.

Whether you’re a dev or product lead, staying informed helps protect your revenue and keep the user journey smooth. Policy isn’t boring admin stuff — it shapes real experiences.

💡 IAP Tips & Sales Strategies

Boosting in-app revenue isn’t about pressure — it’s about smart moves. Here are a few practical strategies that can drive real results.

🪝 Use Webhooks to Stay in Sync

Webhooks are your backstage crew. When a user cancels, upgrades, or gets refunded, you can instantly react — update databases, trigger emails, or send push notifications. It keeps your user data fresh and your actions timely.

🤩 Create a Value-First Experience

Let users feel the Pro experience. Don’t just show a list of features — show the result.
Let them try it. In our product HerFIT, we offer a trial with real results in 3 months. That connection makes users say, “I can’t go back.”
Let them see the value before they pay.

🧠 Sales Hooks That Work

Add FOMO: Limited-time discounts with countdowns drive urgency.
Catch churn: Offer exit discounts or quick surveys when users cancel.
Target behavior: Track users who check the paywall often — send them tailored offers to help them convert.

Every touchpoint is an opportunity to earn trust and revenue.

A great purchasing experience makes users feel excited to buy now like they’d miss out if they don’t rather than feeling pressured or forced.

🏛️ Stay Updated on Policy

One thing many devs miss: IAP isn’t just code — it’s also about rules, laws, and compliance.

App Store & Play Store Guidelines
Apple and Google often update their rules. A small change like “must show post-trial pricing” can mean reworking your whole flow. Stay alert.

Local Regulations Matter
Rules vary across countries. India, South Korea, EU — all have different tax laws, commission rates, and billing policies. Don’t assume it’s the same everywhere.

Service Provider Changes
Platforms like RevenueCat update webhooks and APIs often. Missing these updates can break flows or cost you revenue. Keep an eye on changelogs.

Whether you’re a dev or product lead, staying informed helps protect your revenue and keep the user journey smooth. Policy isn’t boring admin stuff — it shapes real experiences.

💡 IAP Tips & Sales Strategies

Boosting in-app revenue isn’t about pressure — it’s about smart moves. Here are a few practical strategies that can drive real results.

🪝 Use Webhooks to Stay in Sync

Webhooks are your backstage crew. When a user cancels, upgrades, or gets refunded, you can instantly react — update databases, trigger emails, or send push notifications. It keeps your user data fresh and your actions timely.

🤩 Create a Value-First Experience

Let users feel the Pro experience. Don’t just show a list of features — show the result.
Let them try it. In our product HerFIT, we offer a trial with real results in 3 months. That connection makes users say, “I can’t go back.”
Let them see the value before they pay.

🧠 Sales Hooks That Work

Add FOMO: Limited-time discounts with countdowns drive urgency.
Catch churn: Offer exit discounts or quick surveys when users cancel.
Target behavior: Track users who check the paywall often — send them tailored offers to help them convert.

Every touchpoint is an opportunity to earn trust and revenue.

A great purchasing experience makes users feel excited to buy now like they’d miss out if they don’t rather than feeling pressured or forced.

🏛️ Stay Updated on Policy

One thing many devs miss: IAP isn’t just code — it’s also about rules, laws, and compliance.

App Store & Play Store Guidelines
Apple and Google often update their rules. A small change like “must show post-trial pricing” can mean reworking your whole flow. Stay alert.

Local Regulations Matter
Rules vary across countries. India, South Korea, EU — all have different tax laws, commission rates, and billing policies. Don’t assume it’s the same everywhere.

Service Provider Changes
Platforms like RevenueCat update webhooks and APIs often. Missing these updates can break flows or cost you revenue. Keep an eye on changelogs.

Whether you’re a dev or product lead, staying informed helps protect your revenue and keep the user journey smooth. Policy isn’t boring admin stuff — it shapes real experiences.

Stay Updated on Policy

Starting May 1st, Apple must allow iOS apps to support external payment systems, and they can’t charge that infamous 15–30% commission anymore.

This is great news for developers! For years we’ve been stuck paying platform fees we couldn’t avoid — and this shift is largely thanks to Epic Games and their ongoing legal battle.

But keep in mind — it only applies to U.S. apps for now, and reader apps (like Spotify).

This policy change brings several real benefits to developers and businesses.

First, more revenue stays in your hands. Without the 15–30% platform cut, you can reinvest that money into growth, marketing, or product improvements.
Second, you get to use custom payment solutions like Stripe or local providers. That means a smoother, more branded checkout experience tailored to your users.
Third, faster iteration. Since pricing and product changes happen on your own web pages, you skip App Store reviews and can push updates instantly. That gives your marketing team so much more flexibility.
And finally, faster payouts. No more waiting 1–2 months for Apple or Google to settle. For startups and lean teams, quicker cash flow can make a huge difference.

Of course, external payment comes with its own set of challenges. First, there’s a shift in user behavior. When users are taken out of the app to complete a purchase on the web. They may wonder, “Is this secure?” That drop in confidence can hurt your conversion rate. Second, there’s added friction and operational cost. Apple and Google usually handle things like refunds, fraud prevention, and tax compliance. But when you go external, those responsibilities fall on your team. Finally, let’s talk numbers. RevenueCat ran an A/B test and found that using external payments led to a 25% to 45% drop in conversion rate. And that’s not even counting the cost of setting up and maintaining your own payment system. So while external payment gives you more freedom, it also comes with trade-offs you’ll need to carefully weigh.

So, this article is about how to approach In-App Purchases with more professionalism and strategy. Once you’ve mastered these concepts, you’ll understand IAP better than many developers. And with that understanding, I believe you’re ready to take on the challenge of monetizing your product with confidence 💪Now’s the time — turn those ideas in your head into real products and start sharing them with the world!

Conclusion

Monetizing your app is easier with tools like RevenueCat — no need to build complex IAP systems from scratch. Focus on your product, let RevenueCat handle the backend.

And if you want to build apps even faster, check out Blup — the low-code Flutter builder made for shipping with speed and vibe.

Starting May 1st, Apple must allow iOS apps to support external payment systems, and they can’t charge that infamous 15–30% commission anymore.

This is great news for developers! For years we’ve been stuck paying platform fees we couldn’t avoid — and this shift is largely thanks to Epic Games and their ongoing legal battle.

But keep in mind — it only applies to U.S. apps for now, and reader apps (like Spotify).

This policy change brings several real benefits to developers and businesses.

First, more revenue stays in your hands. Without the 15–30% platform cut, you can reinvest that money into growth, marketing, or product improvements.
Second, you get to use custom payment solutions like Stripe or local providers. That means a smoother, more branded checkout experience tailored to your users.
Third, faster iteration. Since pricing and product changes happen on your own web pages, you skip App Store reviews and can push updates instantly. That gives your marketing team so much more flexibility.
And finally, faster payouts. No more waiting 1–2 months for Apple or Google to settle. For startups and lean teams, quicker cash flow can make a huge difference.

Of course, external payment comes with its own set of challenges. First, there’s a shift in user behavior. When users are taken out of the app to complete a purchase on the web. They may wonder, “Is this secure?” That drop in confidence can hurt your conversion rate. Second, there’s added friction and operational cost. Apple and Google usually handle things like refunds, fraud prevention, and tax compliance. But when you go external, those responsibilities fall on your team. Finally, let’s talk numbers. RevenueCat ran an A/B test and found that using external payments led to a 25% to 45% drop in conversion rate. And that’s not even counting the cost of setting up and maintaining your own payment system. So while external payment gives you more freedom, it also comes with trade-offs you’ll need to carefully weigh.

So, this article is about how to approach In-App Purchases with more professionalism and strategy. Once you’ve mastered these concepts, you’ll understand IAP better than many developers. And with that understanding, I believe you’re ready to take on the challenge of monetizing your product with confidence 💪Now’s the time — turn those ideas in your head into real products and start sharing them with the world!

Conclusion

Monetizing your app is easier with tools like RevenueCat — no need to build complex IAP systems from scratch. Focus on your product, let RevenueCat handle the backend.

And if you want to build apps even faster, check out Blup — the low-code Flutter builder made for shipping with speed and vibe.

Starting May 1st, Apple must allow iOS apps to support external payment systems, and they can’t charge that infamous 15–30% commission anymore.

This is great news for developers! For years we’ve been stuck paying platform fees we couldn’t avoid — and this shift is largely thanks to Epic Games and their ongoing legal battle.

But keep in mind — it only applies to U.S. apps for now, and reader apps (like Spotify).

This policy change brings several real benefits to developers and businesses.

First, more revenue stays in your hands. Without the 15–30% platform cut, you can reinvest that money into growth, marketing, or product improvements.
Second, you get to use custom payment solutions like Stripe or local providers. That means a smoother, more branded checkout experience tailored to your users.
Third, faster iteration. Since pricing and product changes happen on your own web pages, you skip App Store reviews and can push updates instantly. That gives your marketing team so much more flexibility.
And finally, faster payouts. No more waiting 1–2 months for Apple or Google to settle. For startups and lean teams, quicker cash flow can make a huge difference.

Of course, external payment comes with its own set of challenges. First, there’s a shift in user behavior. When users are taken out of the app to complete a purchase on the web. They may wonder, “Is this secure?” That drop in confidence can hurt your conversion rate. Second, there’s added friction and operational cost. Apple and Google usually handle things like refunds, fraud prevention, and tax compliance. But when you go external, those responsibilities fall on your team. Finally, let’s talk numbers. RevenueCat ran an A/B test and found that using external payments led to a 25% to 45% drop in conversion rate. And that’s not even counting the cost of setting up and maintaining your own payment system. So while external payment gives you more freedom, it also comes with trade-offs you’ll need to carefully weigh.

So, this article is about how to approach In-App Purchases with more professionalism and strategy. Once you’ve mastered these concepts, you’ll understand IAP better than many developers. And with that understanding, I believe you’re ready to take on the challenge of monetizing your product with confidence 💪Now’s the time — turn those ideas in your head into real products and start sharing them with the world!

Conclusion

Monetizing your app is easier with tools like RevenueCat — no need to build complex IAP systems from scratch. Focus on your product, let RevenueCat handle the backend.

And if you want to build apps even faster, check out Blup — the low-code Flutter builder made for shipping with speed and vibe.

Starting May 1st, Apple must allow iOS apps to support external payment systems, and they can’t charge that infamous 15–30% commission anymore.

This is great news for developers! For years we’ve been stuck paying platform fees we couldn’t avoid — and this shift is largely thanks to Epic Games and their ongoing legal battle.

But keep in mind — it only applies to U.S. apps for now, and reader apps (like Spotify).

This policy change brings several real benefits to developers and businesses.

First, more revenue stays in your hands. Without the 15–30% platform cut, you can reinvest that money into growth, marketing, or product improvements.
Second, you get to use custom payment solutions like Stripe or local providers. That means a smoother, more branded checkout experience tailored to your users.
Third, faster iteration. Since pricing and product changes happen on your own web pages, you skip App Store reviews and can push updates instantly. That gives your marketing team so much more flexibility.
And finally, faster payouts. No more waiting 1–2 months for Apple or Google to settle. For startups and lean teams, quicker cash flow can make a huge difference.

Of course, external payment comes with its own set of challenges. First, there’s a shift in user behavior. When users are taken out of the app to complete a purchase on the web. They may wonder, “Is this secure?” That drop in confidence can hurt your conversion rate. Second, there’s added friction and operational cost. Apple and Google usually handle things like refunds, fraud prevention, and tax compliance. But when you go external, those responsibilities fall on your team. Finally, let’s talk numbers. RevenueCat ran an A/B test and found that using external payments led to a 25% to 45% drop in conversion rate. And that’s not even counting the cost of setting up and maintaining your own payment system. So while external payment gives you more freedom, it also comes with trade-offs you’ll need to carefully weigh.

So, this article is about how to approach In-App Purchases with more professionalism and strategy. Once you’ve mastered these concepts, you’ll understand IAP better than many developers. And with that understanding, I believe you’re ready to take on the challenge of monetizing your product with confidence 💪Now’s the time — turn those ideas in your head into real products and start sharing them with the world!

Conclusion

Monetizing your app is easier with tools like RevenueCat — no need to build complex IAP systems from scratch. Focus on your product, let RevenueCat handle the backend.

And if you want to build apps even faster, check out Blup — the low-code Flutter builder made for shipping with speed and vibe.

How to Monetize Your Flutter App Without the Headache: Meet RevenueCat

Introduction

Introduction

Introduction

Introduction

The Challenge: IAP Complexity

The Challenge: IAP Complexity

The Challenge: IAP Complexity

The Challenge: IAP Complexity

What is In-App Purchase(IAP)？

1. Consumables

2. Non-Consumables

3. Subscriptions

What is In-App Purchase(IAP)？

1. Consumables

2. Non-Consumables

3. Subscriptions

What is In-App Purchase(IAP)？

1. Consumables

2. Non-Consumables

3. Subscriptions

What is In-App Purchase(IAP)？

1. Consumables

2. Non-Consumables

3. Subscriptions

Why Most Apps Use IAP Subscriptions?

Why Most Apps Use IAP Subscriptions?

Why Most Apps Use IAP Subscriptions?

Why Most Apps Use IAP Subscriptions?

RevenueCat!

Design For Mobile Apps

Analytics

Real-time Subscriber Insights

RevenueCat!

Design For Mobile Apps

Analytics

Real-time Subscriber Insights

RevenueCat!

Design For Mobile Apps

Analytics

Real-time Subscriber Insights

RevenueCat!

Design For Mobile Apps

Analytics

Real-time Subscriber Insights

If We Do IAP — Flow

If We Do IAP — Flow

If We Do IAP — Flow

If We Do IAP — Flow

RevenueCat IAP Flow

RevenueCat IAP Flow

RevenueCat IAP Flow

RevenueCat IAP Flow

Basic Setup: Add Products in Stores & RevenueCat

Basic Setup: Add Products in Stores & RevenueCat

Basic Setup: Add Products in Stores & RevenueCat

Basic Setup: Add Products in Stores & RevenueCat

1️⃣ Package

2️⃣ Entitlement

3️⃣ Offering

1️⃣ Package

2️⃣ Entitlement

3️⃣ Offering

1️⃣ Package

2️⃣ Entitlement

3️⃣ Offering

1️⃣ Package

2️⃣ Entitlement

3️⃣ Offering

Integrating RevenueCat SDK in Flutter

Integrating RevenueCat SDK in Flutter

Integrating RevenueCat SDK in Flutter

Integrating RevenueCat SDK in Flutter

💡 Initialize RevenueCat SDK

💡Fetch Offerings

💡 Fetch Packages from Offering

💡 Purchase Package

💡 Verify User Entitlements

🙋🏻 Sync Existing Subscribers

💡 Initialize RevenueCat SDK