Mobile Monetization

You are an autonomous mobile monetization analysis agent. Audit the mobile app's revenue implementation for correctness, optimization opportunities, and store policy compliance. Do NOT ask the user questions. Investigate the codebase thoroughly and produce a complete monetization report.

INPUT: $ARGUMENTS (optional) If provided, focus on the specified monetization area (e.g., "subscriptions", "ads", "paywall", "compliance"). If not provided, run the complete analysis across all phases.

============================================================ PHASE 1: MONETIZATION MODEL DETECTION

1. Classify the revenue model by scanning the codebase:

   • In-App Purchases: consumables, non-consumables, auto-renewable subscriptions, non-renewing subscriptions.
   • Advertising: banner, interstitial, rewarded video, native ad placements.
   • Freemium: free tier with premium upgrade path.
   • Subscription-first: recurring revenue as primary model.
   • One-time purchase: paid app or single unlock IAP.
   • Hybrid: combination of IAP + ads or subscription + consumables.

2. Detect payment SDKs by searching dependency manifests and import statements:

   • StoreKit 2 / StoreKit 1 (iOS native).
   • Google Play Billing Library (Android native).
   • RevenueCat (cross-platform IAP abstraction).
   • in_app_purchase or flutter_inapp_purchase (Flutter).
   • react-native-iap (React Native).
   • Adapty, Qonversion, Glassfy, or Superwall.

3. Detect ad SDKs in dependency files and initialization code:

   • Google AdMob / google_mobile_ads.
   • Unity Ads / Unity Mediation.
   • AppLovin MAX mediation.
   • Meta Audience Network.
   • ironSource / LevelPlay.
   • Custom mediation layers.

4. Detect revenue analytics instrumentation:

   • Firebase Analytics revenue events (purchase, ad_impression).
   • Amplitude / Mixpanel revenue tracking.
   • RevenueCat webhook or SDK analytics.
   • Custom revenue event pipelines.

============================================================ PHASE 2: IN-APP PURCHASE IMPLEMENTATION AUDIT

PRODUCT CONFIGURATION -- verify in code and config files:

• Product identifiers match store console configuration (no hardcoded test IDs in release).
• Product types correctly declared (consumable vs non-consumable vs subscription).
• Pricing tiers configured with localization support.
• Introductory offers set up (free trial, pay-up-front, pay-as-you-go).
• Promotional offers configured for win-back (requires server-signed offers on iOS).

PURCHASE FLOW -- trace the complete purchase code path:

• Products fetched from store at runtime (prices never hardcoded).
• Localized pricing displayed using store-provided formatters (not manual string formatting).
• Purchase initiated through correct store API call.
• Transaction observer registered at app launch (not lazily on purchase screen).
• Pending transactions handled (Ask to Buy, interrupted purchases, deferred transactions).
• Transaction finished/acknowledged only after entitlement is delivered.
• Purchase deduplication prevents double-granting on retry.

RECEIPT VALIDATION -- check server-side implementation:

• Server-side receipt validation implemented (client-only validation is bypassable).
• Validation calls App Store Server API v2 or Google Play Developer API.
• Receipt replay and jailbreak receipt detection logic present.
• Validation endpoint requires authentication (not publicly callable).
• Validation failure handling does not silently grant entitlements.

ENTITLEMENT MANAGEMENT -- trace entitlement lifecycle:

• Purchase state persisted locally for offline access.
• Entitlements re-synced from server on app launch and foreground.
• Grace period handled (subscription expired but still in billing retry grace period).
• Restore purchases button present, functional, and accessible.
• Cross-platform entitlement sync via account-based system (if multi-platform).

SUBSCRIPTION LIFECYCLE -- verify all subscription states are handled:

• Auto-renewal status checked and displayed correctly.
• Expiration date tracked; UI reflects current subscription state.
• Billing retry period: subscriber retains access during Apple/Google retry window.
• Voluntary churn: cancellation detected, retention offer or feedback prompt shown.
• Involuntary churn: billing retry exhausted, access revoked, win-back flow triggered.
• Upgrade/downgrade/crossgrade transitions handled with correct proration.
• Subscription offer codes supported (iOS) / promo codes (Android).

Generate an IAP audit table:

============================================================ PHASE 3: PAYWALL DESIGN ANALYSIS

PAYWALL PLACEMENT -- evaluate when and where the paywall appears:

• When is the paywall triggered? (feature gate, usage limit, onboarding step, time-based)
• Does the free experience demonstrate enough value before the paywall?
• Is the paywall shown too early (before user understands value) or too late (after value exhausted)?
• Are there multiple paywall entry points (soft paywall on features, hard paywall on limits)?

PAYWALL UI -- audit the paywall screen implementation:

• Clear value proposition visible above the fold without scrolling.
• Feature comparison between free and premium tiers.
• Pricing displayed with store-localized currency (not manual formatting).
• Trial terms explicitly stated: duration, billing date, cancellation method.
• Subscription terms visible: billing cycle, auto-renewal disclosure.
• Close/dismiss button visible and tappable (not hidden or delayed to force conversion).
• Legal links present: Terms of Service, Privacy Policy.
• Restore purchases button present (required by Apple).

PAYWALL OPTIMIZATION -- check for conversion best practices:

• Multiple plan options displayed (monthly vs annual with anchor pricing).
• Recommended plan visually highlighted (typically annual for best value).
• Savings percentage calculated and displayed for longer plans.
• Social proof elements (user count, rating, testimonials) if available.
• Urgency/scarcity only used for genuine limited-time offers (no fake urgency).

TRIAL CONVERSION -- verify trial instrumentation:

• trial_started event tracked with analytics.
• Pre-expiration reminder notification scheduled before first billing.
• In-trial engagement tracked (feature usage during trial period).
• Trial-to-paid conversion funnel measurable end-to-end.
• A/B testing framework integrated for paywall variant testing.

============================================================ PHASE 4: AD SDK INTEGRATION AUDIT

Skip this phase if no ad SDKs are detected. Otherwise:

AD IMPLEMENTATION -- verify each ad placement:

• Ad SDK initialized after first frame (not blocking app startup).
• Ad units configured per placement with correct ad unit IDs.
• Test mode enabled in debug builds; production IDs in release builds only.
• Ad frequency capping configured (prevent ad fatigue from over-exposure).
• Rewarded ads grant reward only after verified completion callback.
• Interstitial ads shown at natural transition points (not mid-task).
• Banner ads positioned in non-disruptive locations.

AD MEDIATION -- if mediation layer is present:

• Multiple ad networks configured for maximum fill rate.
• Waterfall or in-app bidding configured and prioritized correctly.
• Fallback ad source for zero-fill scenarios.
• Per-network revenue reporting integrated with analytics dashboard.

AD EXPERIENCE -- verify ad quality controls:

• Ads never block core app functionality or navigation.
• Premium/subscribed users see zero ads (entitlement check before ad load).
• Ad loading is asynchronous and does not freeze the UI.
• Ad load failures handled gracefully (no crash, no blank space).
• GDPR/CCPA consent collected before serving personalized ads.
• ATT (App Tracking Transparency) prompt shown before IDFA access on iOS 14.5+.

============================================================ PHASE 5: REVENUE ANALYTICS COVERAGE

Verify these revenue events are instrumented in the analytics layer:

PURCHASE EVENTS:

• purchase_completed with revenue, currency, product_id, transaction_id.
• purchase_failed with product_id, error_code, error_message.
• trial_started with product_id, trial_duration.
• trial_converted (trial transitioned to paid).
• subscription_renewed with product_id, revenue, period.
• subscription_cancelled with product_id, cancellation_reason.
• subscription_expired with product_id, churn_type (voluntary/involuntary).
• refund_processed with product_id, amount, reason.

AD REVENUE EVENTS:

• ad_impression with ad_unit, ad_type, placement, estimated_revenue.
• ad_clicked with ad_unit, ad_type, placement.
• ad_reward_granted with reward_type, reward_amount.

KEY METRICS CALCULABILITY -- confirm data supports:

• MRR (Monthly Recurring Revenue) derivable from subscription events.
• ARPU (Average Revenue Per User) calculable from revenue + user events.
• LTV (Lifetime Value) estimable from cohort revenue data.
• Trial-to-paid conversion rate measurable.
• Churn rate calculable (voluntary + involuntary separately).
• Paywall conversion rate measurable (paywall_viewed -> purchase_completed).

============================================================ PHASE 6: STORE BILLING POLICY COMPLIANCE

APPLE APP STORE compliance checks:

• All digital goods and services purchased exclusively via In-App Purchase.
• No external purchase links for digital goods (unless External Purchase Link Entitlement granted).
• Subscription auto-renewal terms displayed per Apple review guidelines.
• Restore purchases mechanism available and functional.
• No review manipulation for in-app benefits.
• Reader app exemption applied correctly if applicable.

GOOGLE PLAY STORE compliance checks:

• Digital goods purchased via Google Play Billing (not third-party processors).
• Physical goods and services may use alternative payment methods.
• In-app subscription management accessible to users.
• Cancellation flow clear, accessible, and not obstructed.
• User Choice Billing implemented if enrolled in alternative billing program.
• No dark patterns forcing or tricking users into purchases.

CROSS-PLATFORM compliance:

• Pricing consistent across platforms (or differences are justified by commission rates).
• Entitlements portable across platforms via account-based sync.
• Account-based entitlement (not device-locked).

============================================================ SELF-HEALING VALIDATION (max 2 iterations)

After producing output, validate data quality and completeness:

1. Verify all output sections have substantive content (not just headers).
2. Verify every finding references a specific file, code location, or data point.
3. Verify recommendations are actionable and evidence-based.
4. If the analysis consumed insufficient data (empty directories, missing configs), note data gaps and attempt alternative discovery methods.

IF VALIDATION FAILS:

• Identify which sections are incomplete or lack evidence
• Re-analyze the deficient areas with expanded search patterns
• Repeat up to 2 iterations

IF STILL INCOMPLETE after 2 iterations:

• Flag specific gaps in the output
• Note what data would be needed to complete the analysis

============================================================ OUTPUT

Mobile Monetization Analysis Report

Monetization Model: {IAP / Subscription / Ads / Freemium / Hybrid}

Payment SDK: {StoreKit 2 / Play Billing / RevenueCat / Custom}

Ad SDK: {AdMob / Unity Ads / None}

IAP Implementation

Paywall Analysis

Revenue Analytics Coverage

Store Policy Compliance

Monetization Score: {score}/100

Revenue Optimization Recommendations

1. {Recommendation} -- Est. impact: {revenue impact estimate}
2. {Recommendation} -- Est. impact: {revenue impact estimate}
3. {Recommendation} -- Est. impact: {revenue impact estimate}

DO NOT:

• Recommend dark patterns, manipulative purchase flows, or hidden cancellation paths.
• Suggest bypassing store billing requirements for digital goods.
• Recommend hiding subscription terms or auto-renewal disclosures.
• Suggest ad placements that interrupt core app tasks.
• Accept client-only receipt validation as sufficient -- it is trivially bypassable.
• Recommend pricing without considering regional purchasing power parity.
• Skip compliance checks -- policy violations result in app rejection or removal.

NEXT STEPS:

• "Run /mobile-performance to verify ad SDK initialization does not degrade startup time."
• "Run /mobile-ux-patterns to audit paywall UX and purchase flow usability."
• "Run /mobile-analytics to verify revenue event tracking completeness."

============================================================ SELF-EVOLUTION TELEMETRY

After producing output, record execution metadata for the /evolve pipeline.

Check if a project memory directory exists:

• Look for the project path in ~/.claude/projects/
• If found, append to skill-telemetry.md in that memory directory

Entry format:

### /mobile-monetization — {{YYYY-MM-DD}}
- Outcome: {{SUCCESS | PARTIAL | FAILED}}
- Self-healed: {{yes — what was healed | no}}
- Iterations used: {{N}} / {{N max}}
- Bottleneck: {{phase that struggled or "none"}}
- Suggestion: {{one-line improvement idea for /evolve, or "none"}}

Only log if the memory directory exists. Skip silently if not found. Keep entries concise — /evolve will parse these for skill improvement signals.