Monetization strategy for iOS/macOS apps. Covers readiness assessment, pricing model selection, tier structuring, free trial strategy, and implementation guidance. Use when deciding what to charge, how to price, or planning monetization end-to-end.
把这段话发给 Claude Code、Codex 或 Cursor。智能体会先检查安全性，你确认后才安装。
读取 https://funcoding.ai/skills/rshankras/claude-code-apple-skills/monetization/install.md ，按里面的步骤帮我安装这个 Skill。
End-to-end monetization guidance for Apple platform apps — from "should I charge?" to "here's your pricing page structure."
Sub-skills in this category: external-purchases/ (US web checkout via the External Purchase Link entitlement, commission-flip architecture) and bundles-and-licensing/ (own-app bundles, Family Sharing, cross-developer suites, institutional volume licensing). Route there when the question is beyond the single-app price tag.
Use this skill when the user:
Before recommending a pricing model, evaluate whether the app is ready to monetize. Ask these questions via AskUserQuestion:
1. App Stage
2. Value Proposition
3. Current State
Evaluate against these criteria:
| Signal | Ready | Not Ready |
|---|---|---|
| Core value | Clear, differentiated | Still finding product-market fit |
| User retention | D7 > 20% | D7 < 10% |
| User feedback | "I'd pay for this" | Silence or complaints |
| Feature depth | Enough for free + paid split | Everything feels essential |
| Competition | You offer something unique | Commodity feature set |
| Polish | Professional quality | Rough edges everywhere |
Recommendation thresholds:
Based on app type and user behavior, recommend the right model.
Is the app used daily/weekly?
├── YES → Does it provide ongoing value?
│ ├── YES → SUBSCRIPTION
│ └── NO → ONE-TIME PURCHASE (with optional tip jar)
└── NO → Is it a utility/tool?
├── YES → ONE-TIME PURCHASE or FREEMIUM
└── NO → Is it content-based?
├── YES → SUBSCRIPTION or CONSUMABLE IAP
└── NO → FREEMIUM with premium unlock
Read pricing-models.md for detailed comparison of each model:
Read app-type-guides.md for specific guidance by app category:
Once a model is selected, design the tier structure.
Two-tier structure (recommended for most indie apps):
FREE PRO ($X.99/mo or $XX.99/yr)
───────────────────── ─────────────────────────────
Core functionality Everything in Free
Limited usage/storage Unlimited usage
Basic features Advanced features
Priority support (optional)
Early access to new features
Three-tier structure (for apps with clear user segments):
FREE PLUS ($X.99/mo) PRO ($XX.99/mo)
──────────── ────────────────── ──────────────────
Basic use Power user Professional/team
Ads/limits No ads, more quota Unlimited + extras
The hardest decision. Follow these principles:
Free tier should:
Paid tier should:
❌ Bad splits:
✅ Good splits:
| Type | Best For | Apple Support |
|---|---|---|
| Introductory offer (free) | Subscriptions | Built-in via App Store |
| Introductory offer (discounted) | High-value subscriptions | Built-in via App Store |
| Feature-limited free tier | Freemium apps | N/A (your logic) |
| Time-limited full access | Productivity apps | Built-in via App Store |
| App Type | Trial Length | Reason |
|---|---|---|
| Daily-use productivity | 7 days | Quick to see value |
| Health/fitness tracking | 14 days | Need time to build habit |
| Creative tools | 7 days | One project cycle |
| Business/professional | 14-30 days | Need to integrate into workflow |
| Education/learning | 7 days | One learning cycle |
After strategy is set, guide implementation.
| Scenario | Apple's Cut | You Keep |
|---|---|---|
| Standard (Year 1) | 30% | 70% |
| After Year 1 of subscription | 15% | 85% |
| Small Business Program (< $1M/yr) | 15% | 85% |
| Small Business + Year 2 subscription | 15% | 85% |
Important: Revenue calculations should always account for Apple's cut. A $9.99/mo subscription with Small Business Program = ~$8.49/mo to you.
For code generation, refer users to the paywall-generator skill:
Use the paywall-generator skill to create:
- StoreKit 2 subscription management
- Paywall UI (SwiftUI)
- Receipt validation
- Subscription status tracking
Do:
Don't:
Key rules to follow:
Present monetization strategy as:
# Monetization Strategy: [App Name]
## Readiness Assessment
**Score**: X/6 — [Ready to monetize / Soft-launch / Focus on product]
| Signal | Status | Notes |
|--------|--------|-------|
| Core value | ✅/❌ | ... |
| Retention | ✅/❌ | ... |
| User demand | ✅/❌ | ... |
| Feature depth | ✅/❌ | ... |
| Differentiation | ✅/❌ | ... |
| Polish | ✅/❌ | ... |
## Recommended Model
**[Model Name]** — [One-line rationale]
## Tier Structure
| Feature | Free | Pro ($X.99/mo) |
|---------|------|-----------------|
| ... | ✅ | ✅ |
| ... | Limited | Unlimited |
| ... | ❌ | ✅ |
**Annual pricing**: $XX.99/yr (XX% savings)
## Free Trial
**Type**: [Introductory offer / Feature-limited / etc.]
**Duration**: [X days]
**Conversion tactics**: [Bullet list]
## Revenue Projections (Conservative)
| Metric | Estimate |
|--------|----------|
| Monthly price | $X.99 |
| Annual price | $XX.99 |
| Conversion rate (free→paid) | X-X% |
| Revenue per 1K MAU | $XXX-$XXX/mo |
## Implementation Checklist
- [ ] Configure products in App Store Connect
- [ ] Implement StoreKit 2 (use paywall-generator skill)
- [ ] Design paywall UI
- [ ] Set up introductory offers
- [ ] Add analytics for conversion tracking
- [ ] Test with StoreKit Configuration file
- [ ] Submit for review
## Next Steps
1. [First action item]
2. [Second action item]
3. [Third action item]
anthropics/skills180kApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
AI 与智能体
anthropics/skills180kA set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
AI 与智能体
anthropics/skills180kanthropics/skills180kGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).
AI 与智能体
anthropics/skills180kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
AI 与智能体
anthropics/skills180kStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.
AI 与智能体