implement-in-app-purchase

Generate complete In-App Purchase implementation for Flutter apps.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/andrelucassvt/CleanMacForDevsWeb --skill implement-in-app-purchase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-in-app-purchase
Source: https://github.com/andrelucassvt/CleanMacForDevsWeb/tree/main/.agents/skills/implement-in-app-purchase
Command: npx skills add https://github.com/andrelucassvt/CleanMacForDevsWeb --skill implement-in-app-purchase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implements In-App Purchase (consumable, non-consumable, or subscription) following the project architecture. Asks whether there is a backend server, then generates the complete implementation: InAppPurchaseService, Cubit, State, View, DI registration, and purchase verification flow (local storage via StorageService OR backend endpoint call). Use whenever adding purchases, subscriptions, paywall, or premium features to the app, integrating App Store or Google Play billing, verifying receipts, or restoring purchases. Activate even when the user says 'make the app paid', 'add a paywall', 'implement premium', 'add a subscription plan', 'unlock premium features', or 'monetize the app' without explicitly mentioning InAppPurchase, StoreKit, or Google Play Billing.

Core Features & Use Cases

  • Complete scaffolding including InAppPurchaseService, Cubit, State, View, DI registration, and pull/push verification flows
  • Supports back-end and local verification modes
  • Paywall guidelines including Terms of Use and Privacy Policy notes for subscriptions
  • Integration with App Store and Google Play billing, purchase restoration, and receipt validation

Quick Start

Provide all required configuration answers (backend presence, product types, product IDs, and feature name) in a single message to generate the complete IAP implementation.

Frequently Asked Questions about implement-in-app-purchase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement in-app purchases in Flutter for subscriptions and consumables?

To implement in-app purchases in Flutter, you need to generate an InAppPurchaseService, Cubit, State, View, and dependency injection setup. This scaffolds complete integration for consumables, non-consumables, and subscriptions across App Store and Google Play billing.

What is the best way to verify Google Play and App Store receipts in a Flutter app?

Receipt verification in a Flutter app can be handled via local storage using a StorageService or through a backend endpoint call. The method depends on whether your project architecture includes a backend server for validating purchases.

Does this in-app purchase integration support both local and backend server verification?

Yes, the in-app purchase integration supports both local and backend server verification flows. It asks whether a backend server exists and generates the appropriate purchase verification process, including complete service and state management configurations.

How to add a paywall and premium features to a Flutter app?

Adding a paywall and premium features requires integrating App Store or Google Play billing through a complete state management setup. This includes generating the necessary views, cubits, and paywall guidelines referencing Terms of Use and Privacy Policy.

Do I need a backend server to monetize my Flutter app with subscriptions?

A backend server is not strictly required to monetize a Flutter app with subscriptions, as local verification via StorageService is supported. However, having a backend enables secure server-side receipt validation and storage for restored purchases.

Why should I use cubit state management for Flutter in-app purchase flows?

Using cubit state management for Flutter in-app purchase flows provides a structured architecture that handles purchase statuses, verification triggers, and UI updates. It pairs with dependency injection to cleanly separate the InAppPurchaseService from view rendering.