인앱 구매 및 구독

Welcome to monetizing your mobile app! As an indie hacker, generating revenue is key to sustainability. This lesson introduces In-App Purchases (IAPs) and Subscriptions.

These are ways for users to buy digital goods, services, or access within your app, directly through the app stores.

IAPs come in a few forms. First, Consumable IAPs are items that can be used up and purchased again. Think of them like digital currency or power-ups.

• Examples: Game coins, extra lives, hints, temporary boosts.
• Once used, they are gone and the user can buy more.
• These are often critical for 'freemium' game monetization.

Next are Non-Consumable IAPs. These grant permanent access to content or features after a single purchase. They don't expire or get used up.

• Examples: Removing ads, unlocking premium features, full game versions, digital books.
• Users buy them once and own them forever.
• These purchases should be restorable if a user reinstalls your app or gets a new device.

Auto-Renewable Subscriptions are a powerful monetization model for ongoing access to content or services. Users are automatically charged on a recurring basis (e.g., monthly, yearly).

• Examples: Premium content in a news app, ad-free access to a streaming service, advanced features in a productivity app.
• They continue until the user cancels them.
• Many apps offer free trials to attract subscribers.

Regardless of the type, the basic flow for integrating IAPs and Subscriptions is similar:

1. Define Products: Set up your IAPs in App Store Connect / Google Play Console.
2. Display Products: Show product details (price, description) in your app.
3. Initiate Purchase: User taps 'Buy', your app requests the purchase.
4. Process Payment: App store handles payment and authentication.
5. Grant Access: Your app receives confirmation and unlocks content.

Before writing any code, you define your IAPs and subscriptions in the respective app store consoles. This involves:

• Creating unique Product IDs (e.g., com.myapp.premium_feature).
• Setting up names, descriptions, and pricing.
• For subscriptions, defining durations (monthly, yearly) and optional free trials.

These IDs are what your app will use to reference each specific product.

When a user decides to buy, your app communicates with the platform's billing API (e.g., StoreKit on iOS, Google Play Billing Library on Android).

Here's a simplified pseudo-code of how a purchase might be initiated:

After a purchase is initiated, your app will receive a transaction update. You must handle various outcomes:

• Purchased: The payment was successful. Grant the user access to the purchased content/feature.
• Failed: Payment error or user cancelled. Inform the user.
• Pending: Payment is awaiting external approval (e.g., family sharing). Wait for further updates.
• Restored: User is re-downloading previously purchased non-consumables or subscriptions.

For robust security and to prevent fraud, especially with subscriptions, server-side receipt validation is crucial. Your app sends the purchase receipt to your backend server.

Your server then sends this receipt to Apple/Google's verification servers. They confirm the purchase's authenticity, and your server can then securely grant access to the user.

This prevents users from tampering with local receipts to unlock features for free.

You've learned the fundamentals of monetizing with In-App Purchases and Subscriptions!

• We covered Consumable and Non-Consumable IAPs for one-time purchases.
• Explored Auto-Renewable Subscriptions for recurring revenue.
• Understood the basic integration flow and the importance of server-side receipt validation for security.

Next, dive into the specific platform APIs (Apple's StoreKit or Google Play Billing Library) to implement these powerful monetization strategies in your apps!