You have a working app. Now you need it to generate revenue. In-app purchases (IAPs) are one of the primary monetization methods for mobile apps, but the setup process, fee structures, and platform rules differ between Apple and Google. Getting any of these wrong can lead to rejected submissions, broken purchase flows, or unexpected deductions from earnings.
This guide covers how to select the right in-app purchase (IAP) type, configure both stores, understand commission rates, and improve conversions using platform tools. If you are launching your first paid feature or restructuring an existing model, the fastest path to revenue is simple: pick the correct product type, follow the store rules precisely, and iterate on pricing and paywall messaging based on real user behavior.
Why in-app purchases matter for indie builders right now
IAPs matter because Apple and Google designed their platforms around them. The stores handle tax collection, regional pricing, refunds, and subscription management in a way that is hard to replicate safely on your own.
Here is what that means for indie builders: if you sell digital goods or premium access inside a mobile app, you usually get higher trust and fewer payment failures by using the native purchase system. You also reduce compliance surface area because the platforms already define the required UX, disclosures, and receipt mechanics.
Choosing the right IAP type for your app
The IAP type you pick determines how you charge, how you deliver value, and how much ongoing maintenance your monetization needs. Decide this before you open App Store Connect or Google Play Console, because it affects everything downstream.
Apple and Google support the main product types described in the IAP documentation.
Pick consumables for repeat purchases, non-consumables for one-time access
Consumables are used once and can be repurchased, such as AI credits or extra exports. They work well when your app has a natural spending mechanic. Users make frequent small transactions, and you do not have renewals or churn management to handle.
Non-consumables are purchased once and last indefinitely, such as ad removal or premium feature access. They are operationally the simplest IAP type. Set them up once and keep them stable. For solopreneurs with limited bandwidth, that simplicity is a significant advantage. Apple also expects you to provide a restore purchases path for eligible items under Guideline 3.1.1.
Use subscriptions for predictable recurring revenue
Auto-renewable subscriptions renew automatically and suit apps that deliver ongoing value, such as content updates, cloud sync, or features with recurring API costs. They provide predictable recurring revenue, which allows for more stable financial planning and investment. The tradeoff is that subscriptions add operational overhead: churn management, renewal communication, and compliance with both platforms’ subscription UX requirements.
Non-renewing subscriptions cover fixed-duration access, such as a time-limited course or a seasonal pass. They can fit products where access is naturally time-bound.
Both Apple and Google let you offer multiple product types at once, so hybrid approaches work without extra architectural overhead.
Setting up IAPs on Apple and Google
Once you know what you are selling, configure the stores carefully. Store configuration mistakes create the most frustrating failure mode: purchases that work on your device, then fail in review or after release.
Apple App Store setup basics
Apple requires account-level setup before any purchase can succeed in production. Start by accepting the Paid Apps Agreement in App Store Connect. Without that agreement, you can build code and UI, but you can not sell.
Review the Human Interface Guidelines and the App Review Guidelines before finalizing your paywall UX. Apple rejects apps where the purchase experience feels misleading, incomplete, or inconsistent with platform patterns.
In App Store Connect, configure each product with a unique product identifier, localized metadata, pricing, regional availability, and the correct tax category. Keep identifiers consistent across App Store Connect and code, because mismatches cause the most common “product not found” and failed fetch issues.
On the implementation side, Apple’s current guidance is to use StoreKit 2 where possible and to validate transactions properly before granting entitlements. Make sure you test purchases in a controlled environment before you submit.
Google Play setup basics
Google requires Google Play Billing for digital goods sold in-app. Use the official billing documentation and keep your integration current, because older APIs get deprecated and removed over time.
Plan your product IDs carefully. They are permanent once created and can not be changed or reused. For subscriptions, you must create at least one base plan before any purchase is possible. You can not delete a subscription once a base plan exists. You can only archive it.
Treat purchase verification as a core part of your architecture. At minimum, verify purchase state before granting access, and handle refunds and chargebacks. For subscriptions, you will also want to use server-side status checks and event notifications so your entitlement state stays correct when renewals fail or users cancel.
Commission rates and how to keep more revenue
Platform fees directly change how much cash you can reinvest into the app. You do not need to optimize fees on day one, but you should understand the thresholds early so you do not price yourself into a corner.
Google Play’s service fee for eligible developers is 15% on $1M of earnings each year, then 30% above that. Google applies the reduced rate automatically when you qualify.
On Apple, you must enroll in the Small Business Program to get the reduced rate. The program terms include a reduced commission of 15% (with 30% otherwise) based on eligibility.
Do not build your model around bypassing IAP for digital goods. Apple’s review rules generally require IAP for digital content and features, and violations often lead to rejection under Guideline 3.1.1.
Pricing strategies that convert
Once you understand your fee structure, pricing becomes a product decision, not a guess. The goal is to reduce cognitive load at the paywall and make the value tradeoff feel obvious. Charm pricing often helps. Prices ending in .99 can convert better than round numbers.
Decoy pricing uses multiple tiers so one option looks like the clear choice. Price anchoring places annual and monthly plans side-by-side so annual feels like a better deal. The same principle applies when you add a premium tier. A high-priced option can make the mid-tier feel more reasonable, even if few people buy the top tier.
Keep your pricing structure simple. Your pricing structure is too complex if you need to explain which tier includes which features. Confusing tiers increase drop-off and also increase support load after users subscribe.
Optimizing for retention and growth
After you ship your paywall, your job shifts to measurement and iteration. Focus on reducing purchase friction and keeping entitlements accurate, because billing bugs look like churn.
Let users experience value before paying
In most categories, users convert more reliably after they reach a meaningful result. Design your onboarding so users hit a small win, then show the upgrade as the obvious next step.
For subscriptions, consider free trials or introductory offers where they make sense. Use the official subscription tooling and UX patterns described in the subscription guidance so users understand what they are buying.
Use free platform analytics
Use App Store Connect’s App Analytics and subscription reporting to track conversion funnels and retention. Pair that with Play Console’s monetization and subscription reporting so you can compare behavior across platforms.
The practical goal is the same on both stores: understand where users drop off (paywall view, plan selection, authentication, purchase confirmation), then fix the highest-impact step first.
Test weekly, not quarterly
Small, frequent tests tend to beat large redesigns because you learn faster and you reduce the risk of breaking a working flow. Run a focused test each week, such as paywall copy, plan ordering, or which feature you highlight first.
Keep the scope tight. Change one variable, wait until results stabilize, ship the winner, and move to the next test.
Apps that teach users how to get value tend to retain better than apps that only show features. Add lightweight guidance, checklists, or examples so users reach success quickly, then connect the upgrade to what they already tried.
Turning setup into revenue
Geography now requires an explicit strategy. The rules and fee programs for the United States and the EU diverge, and the safest approach is to pick a default model, then adjust by region only when you have a clear reason.
Start with the simplest IAP type that fits your app. Configure it correctly on both platforms. Price it using a structure users can understand in seconds. Then iterate based on funnel data and support tickets. Your first paying user will give you more usable signal than another month of theorizing. Get started and ship the version that can earn revenue.
