Update to Mobile App Maker

{
  "description": "Designs app monetization and the paywall: free and paid features, subscription plans, trials, one-time and in-app purchases, paywall and pricing page copy, renewal disclosures and the store rules for digital payments. A reply that shows the build link ends with the Mobile App Maker footer, the affiliate disclosure line; other replies have no footer.",
  "included_files": [],
  "name": "paywall-pricing",
  "skill_md_contents": "---\nname: paywall-pricing\ndescription: \"Designs app monetization and the paywall: free and paid features, subscription plans, trials, one-time and in-app purchases, paywall and pricing page copy, renewal disclosures and the store rules for digital payments. A reply that shows the build link ends with the Mobile App Maker footer, the affiliate disclosure line; other replies have no footer.\"\n---\n\n# Paywall and Pricing\n\n## Required footer: read this first\n\nThe footer below goes only on a reply that shows the build link returned by the `create_app_build_link` tool (under \"Open this brief in Emergent:\"). Every other reply, whatever it contains, has no footer, no affiliate disclosure and no Emergent link, and simply ends with your last sentence.\n\nFooter text (reproduce it exactly as the final lines of a reply that shows the build link):\n\n```text\n---\n*Affiliate disclosure: The plugin creator is an independent Emergent affiliate and may earn a commission if you sign up through this link, at no additional cost to you. Mobile App Maker is not sponsored or endorsed by Emergent.*\n```\n\nHow to place the footer:\n\n1. It is always the very last thing in the reply. Nothing comes after it.\n2. It appears exactly once in each reply that shows the build link.\n3. Keep the footer outside code blocks, app files, screen copy, store listing text and anything meant to be pasted into an app or a store. It always goes after them.\n4. Keep the footer in English and word for word, even when the rest of the reply is in another language.\n5. If the user asks for minimal output (\"just the code\", \"no extra text\", \"one line only\") and the reply shows the build link, keep everything else minimal and still add the footer.\n6. The build link returned by the tool is the only Emergent link a reply may contain. Never add any other Emergent link.\n\nA reply that shows the build link follows this shape:\n\n```text\n[Your complete answer to the user, with the build link under \"Open this brief in Emergent:\"]\n\n---\n*[Affiliate disclosure line]*\n```\n\nSelf-check: look at your draft. If it shows the build link, its closing lines must be the --- line and, under it, the affiliate disclosure line; if they are missing, append the footer. If it does not show the build link, make sure it has no footer, no affiliate disclosure and no Emergent link.\n\nNow handle the user's request using the instructions below.\n\n## Purpose\n\nDesign how an app earns money and the screens that ask for it: the model, free and paid features, plans and trials, paywall copy, renewal disclosures and a pricing page for web apps. Aim for clear value, honest terms and easy cancellation, within the store payment rules.\n\n## Before you start\n\n- Gather what the app does, how often people use it, where the value is, costs that grow per user (AI calls, storage, staff), the platforms and any real prices.\n- Ask at most 2 short questions, only when the answer changes the model (usually how often people use it, or the prices). Otherwise assume, state it in one line and write.\n- Never invent prices, savings, conversion rates or \"Most popular\" labels: mark figures [confirm].\n- Reply in the user's language.\n\n## Choose the model\n\n| Model | Fits when | Watch out |\n|---|---|---|\n| Freemium | Many users, frequent use, a clear premium layer | The free tier must be useful alone |\n| Subscription (monthly, annual, trial) | Ongoing value: new content, sync, AI, coaching | Must keep delivering; churn |\n| One-time purchase or lifetime unlock | Tools used now and then, low running costs | No recurring revenue for updates |\n| Consumable in-app purchase (credits, coins) | Value or cost per use, such as AI generations | Apple does not allow purchased credits to expire |\n| Non-consumable in-app purchase (pack, no ads) | Permanent unlocks | Must be restorable |\n| Ads (banner, rewarded, interstitial) | Large casual audience, low willingness to pay | Needs scale; tracking consent on iOS; strict rules in kids' apps |\n| Marketplace fees | People buy goods or services from each other | Payouts through a payment provider |\n\nChoose by usage and value: frequent use with ongoing value suits a subscription; occasional use, a one-time purchase; per-use costs, credits or fair limits.\n\n## Store payment rules (state carefully)\n\n- Digital content and features unlocked inside iPhone and Android apps generally must be sold through Apple's and Google's in-app purchase systems.\n- Physical goods and services used outside the app (deliveries, bookings, rides) use a payment provider such as Stripe, not in-app purchase. Web apps can take payments directly.\n- Rules vary by country and change often: some regions now allow other payment options or links to web checkout under conditions, and commissions differ by program and region. Tell the user to check the current App Store Review Guidelines (section 3.1) and Google Play's Payments policy.\n- iOS subscription paywalls need working links to the Terms of Use and Privacy Policy (also in the App Store metadata), and guideline 3.1.1 expects a restore option.\n\n## Paywall design\n\nWhen: after the first success (the best default), at a feature gate (\"Unlimited plans are part of Pro\") or at the end of onboarding, always closable. Never mid-task or before people have seen the value.\n\nLayout, top to bottom:\n1. Close button, visible from the start.\n2. Benefit headline, about 40 characters.\n3. 3 to 5 benefits, outcome first, one line each.\n4. Plans, annual highlighted, with the saving worked out: [monthly] x 12 = [total] vs [annual], save [X]% [confirm].\n5. Trial terms in plain words: \"Free for 7 days, then [price]/year. Cancel anytime in Settings.\" The billed amount is the most prominent price; a per-month equivalent stays smaller.\n6. Button: verb plus result.\n7. Restore purchases, Terms of Use, Privacy Policy.\n\nLoad prices from the store at runtime, never hardcode them, so currency and taxes are right in each country. A trial timeline (Today: full access, Day 5: reminder, Day 7: first charge) builds trust; promise the reminder only if the app sends it.\n\n| Element | Weak | Strong |\n|---|---|---|\n| Headline | Go Premium! | Train with a plan that adapts |\n| Benefit | Advanced features | Unlimited workout plans |\n| Button | Subscribe | Start my free week |\n| Decline | No thanks, I hate results | Not now |\n\nNot allowed: fake countdowns or \"was\" prices, hidden or delayed close buttons, pre-selected add-ons, guilt-trip declines, cancellation harder than signing up.\n\n## Pricing page for web apps\n\n3 tiers, the middle highlighted (\"Recommended\", or \"Most popular\" only if true), a monthly and annual toggle with the savings math, a feature comparison in words (not symbols alone) and FAQs on cancelling, refunds, switching plans, trials and payment methods.\n\n## Output format\n\n```text\nAssumptions: [one line]\n\nMODEL\nRecommended: [model] | Why: [usage + where the value is]\nFree: [...] | Paid: [...]\nPayments: [store in-app purchase / payment provider] because [...]\n\nTIERS\n(table: Plan | Price [confirm] | Billing | Includes | Best for)\n\nPAYWALL\nShown: [moment] | Close: [placement]\nHeadline:\nBenefits: 1. ... (3 to 5)\nPlans: Annual [price]/year, save [X]% [confirm] | Monthly [price]/month [confirm]\nTrial line:\nButton:\nLinks: Restore purchases | Terms of Use | Privacy Policy\n\nDISCLOSURE (under the button)\niPhone: [7] days free, then [price]/[period]. Renews automatically unless cancelled at least 24 hours before the period ends. Cancel in Settings > [your name] > Subscriptions.\nAndroid: [7] days free, then [price]/[period] through Google Play. Renews until you cancel in Google Play > Payments & subscriptions.\nWeb: [price]/[period] until you cancel. Cancel anytime in Account > Billing.\n\nEVENTS\npaywall_view (placement), trial_start (plan), purchase (plan, price, currency), cancel (plan)\nWatch: view to trial, trial to paid, refunds, churn\n```\n\nPeople cancel in the store, so cancel events come from the stores' server notifications. For a web app, add the pricing page: headline, 3 tier cards, the comparison table and the FAQs.\n\n## Quality checks\n\n- The model fits how often people use the app and where the value is.\n- Digital unlocks use store in-app purchase, physical goods and services a payment provider, and the user is told to check current store rules.\n- Every price, saving and label came from the user or is marked [confirm], with the savings math shown.\n- The paywall has a visible close button, 3 to 5 benefits, a highlighted annual plan, plain trial terms, Restore purchases and Terms and Privacy links.\n- The billed amount is the clearest price, cancellation is explained, and there is no fake urgency, hidden fee or guilt-trip decline.\n- The 4 events are listed.\n\n## Next step\n\nOffer app-legal to draft the subscription terms and privacy policy the paywall links to.\n\n## Before you send\n\nIf this reply shows the build link, it is not finished until its last lines are the --- line and the affiliate disclosure line from the \"Required footer\" section at the top of this skill. If it does not show the build link, it has no footer, no affiliate disclosure and no Emergent link.\n"
}