0Pricing
Indie Hacker Mobile Apps · Lezione

Acquisti in-app e abbonamenti

Integri acquisti in-app per contenuti acquistabili una sola volta e configuri abbonamenti ricorrenti tramite le API degli app store.

Acquisti in-app e abbonamenti è una lezione Indie Hacker Mobile Apps gratuita su CoddyKit. Questa è la lezione 1 di 4. Puoi leggere la lezione completa qui gratuitamente — poi esercitati direttamente nel browser con un editor di codice integrato e un tutor IA disponibile 24/7. Fa parte del percorso di apprendimento Indie Hacker Mobile Apps, e i tuoi progressi si sincronizzano tra il web e l'app CoddyKit. Il corso Indie Hacker Mobile Apps include 4 lezioni in totale.

Parti di questa lezione non sono ancora state tradotte e vengono mostrate in inglese.

Monetizing with IAPs & Subscriptions

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.

One-Time Purchases: Consumable

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.

One-Time Purchases: Non-Consumable

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.

Recurring Revenue: Subscriptions

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.

The IAP Integration Flow

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.

Setting Up Products (Conceptual)

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.

Initiating a Purchase Request

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:

/* Pseudo-code for a purchase request */

// Imagine the user tapped a 'Buy Premium' button

function startPurchase(productId) {
  console.log(`User wants to buy: ${productId}`);

  // 1. Request product details from the App Store API
  //    (This step often happens earlier to display prices)
  const product = AppStoreAPI.getProductDetails(productId);

  if (product) {
    // 2. Initiate the purchase flow for this product
    //    The OS will handle the payment UI (Face ID/fingerprint)
    AppStoreAPI.makePayment(product);
  } else {
    console.error("Product not found or invalid.");
  }
}

// Example call
// startPurchase("com.myindieapp.remove_ads");

Handling Transaction Outcomes

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.

Server-Side Receipt Validation

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.

Check Your Understanding

Let's quickly check your knowledge of In-App Purchases and Subscriptions.

Recap & Next Steps

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!

Domande Frequenti

La lezione «Acquisti in-app e abbonamenti» è gratuita?

Sì — il testo completo di «Acquisti in-app e abbonamenti» è gratuito qui sul web. Per esercitarvi in modo interattivo (un editor di codice integrato e un tutor IA 24/7) e sbloccare il resto del corso Indie Hacker Mobile Apps, passa a CoddyKit PRO. Il corso Indie Hacker Mobile Apps include 4 lezioni in totale.

Cosa imparerò in «Acquisti in-app e abbonamenti»?

Integri acquisti in-app per contenuti acquistabili una sola volta e configuri abbonamenti ricorrenti tramite le API degli app store. Eserciti Indie Hacker Mobile Apps con codice pratico che esegui direttamente nel browser, e un tutor IA 24/7 risponde alle tue domande mentre lavori sulla lezione.

Ho bisogno di esperienza per iniziare Indie Hacker Mobile Apps?

Non è richiesta alcuna esperienza precedente. Indie Hacker Mobile Apps su CoddyKit è strutturato per principianti e studenti avanzati, quindi puoi iniziare da qui o dall'inizio e procedere al tuo ritmo. Questa è la lezione 1 di 4.

Quanto tempo richiede la lezione «Acquisti in-app e abbonamenti»?

La maggior parte delle lezioni CoddyKit richiede circa 5–10 minuti. Ogni lezione è breve e interattiva, quindi fai progressi costanti e riprendi esattamente da dove hai lasciato su web e app.

Posso scrivere ed eseguire codice in questa lezione Indie Hacker Mobile Apps?

Sì. Ogni lezione Indie Hacker Mobile Apps include un editor di codice integrato, quindi scrivi ed esegui codice reale direttamente nel tuo browser e ricevi feedback istantaneo dall'IA — nessuna configurazione locale necessaria.

Tutte le lezioni di questo corso

  1. Acquisti in-app e abbonamenti
  2. Integrazione della pubblicità mobile
  3. Modelli di prezzo e sperimentazione
  4. Ridurre il churn e massimizzare il lifetime value
← Torna a Indie Hacker Mobile Apps