# App launch Human Guide

## What This Is For
Provides expert guidance for guidance for mobile app launches with experience across indie apps and top-charting products. It gives the agent a clearer input/output frame for growth marketing: what context to ask for, what decisions to make, and what usable artifact to return.

Use this as a human-readable version of the App launch agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions.

## When To Use This
- Use this when you need a repeatable process for app launch.
- Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt.
- Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact.

## When Not To Use This
- Do not use this when you only need a quick factual answer.
- Do not use this when the work depends on private data you cannot share with the assistant.
- Do not use this as a replacement for legal, compliance, financial, or medical review.

## What You Need Before Starting
- The goal or business outcome you want.
- The audience, customer segment, or market context.
- Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance.
- Constraints such as tone, length, channel, deadline, region, or approval requirements.
- A clear definition of what a good final answer should look like.

## Step-By-Step Workflow
1. State the job clearly: "Use the App launch guide to help me with..."
2. Add context: audience, goal, offer, channel, source material, and constraints.
3. Ask the assistant to identify missing inputs before producing the final output.
4. Have the assistant follow the skill-specific guidance below.
5. Review the result against the final checklist and ask for revisions where needed.

## Skill-Specific Guidance
- Check for `app-marketing-context.md` — read it for app context
- Ask: **New app or major update?**
- Ask: **Launch date** (or flexible?)
- Ask: **Budget** (organic only, or paid acquisition available?)
- Ask: **Pre-existing audience?** (email list, social following, existing app users)
- Ask: **Target countries** (simultaneous or phased rollout?)
- [ ] Run `keyword-research` to identify target keywords
- [ ] Run `metadata-optimization` to craft title, subtitle, keyword field
- [ ] Run `competitor-analysis` to understand the landscape
- [ ] Design screenshots (run `screenshot-optimization`)
- [ ] Create app preview video (15-30 seconds)
- [ ] Write compelling description with strong first 3 lines

## Decision Points And Nuance
The original skill emphasizes: Initial Assessment, Launch Timeline, 8 Weeks Before Launch, 4 Weeks Before Launch, 1 Week Before Launch, Launch Day, Week 1 After Launch, Month 1 After Launch, Launch Amplification Tactics, Free Channels.

Use these questions to steer the work:
- What is the intended audience or buyer?
- What source material must be preserved?
- What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion?
- What examples represent the desired quality bar?
- What should the assistant avoid?

## Common Mistakes
- Starting without a clear audience or goal.
- Asking for a final artifact before sharing examples or constraints.
- Accepting a generic first draft without checking it against the intended use.

## Copy-And-Paste Prompt
```text
Use the App launch human guide.

My goal:
[Describe the business outcome]

Audience:
[Describe who this is for]

Context and source material:
[Paste notes, examples, links, or existing copy]

Constraints:
[Tone, length, channel, timeline, must-include items, must-avoid items]

Before producing the final output, ask me for any missing information that would materially improve the result.
```

## Final Checklist
- [ ] The output matches the original goal.
- [ ] The audience and context are reflected in the answer.
- [ ] Important constraints and source material were preserved.
- [ ] The assistant made the relevant decisions explicit.
- [ ] The final artifact is ready to use, review, or hand to the next person.

## Source
This guide was generated from the eronred/aso-skills skill entry for `app-launch`.

## Source Skill Notes
These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic.

# App Launch Strategy

You are an expert in mobile app launches with experience across indie apps and top-charting products. Your goal is to create a comprehensive launch plan that maximizes day-one visibility and sustains momentum.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for app context
2. Ask: **New app or major update?**
3. Ask: **Launch date** (or flexible?)
4. Ask: **Budget** (organic only, or paid acquisition available?)
5. Ask: **Pre-existing audience?** (email list, social following, existing app users)
6. Ask: **Target countries** (simultaneous or phased rollout?)

## Launch Timeline

### 8 Weeks Before Launch

**ASO Foundation:**
- [ ] Run `keyword-research` to identify target keywords
- [ ] Run `metadata-optimization` to craft title, subtitle, keyword field
- [ ] Run `competitor-analysis` to understand the landscape
- [ ] Design screenshots (run `screenshot-optimization`)
- [ ] Create app preview video (15-30 seconds)
- [ ] Write compelling description with strong first 3 lines
- [ ] Design a distinctive icon

**Pre-launch Page (if new app):**
- [ ] Set up App Store pre-order page
- [ ] Enable pre-order notifications
- [ ] Share pre-order link for early sign-ups

**Press & Community:**
- [ ] Build a press kit (screenshots, icon, description, founder story)
- [ ] Identify 20-30 relevant journalists, bloggers, YouTubers
- [ ] Draft personalized pitch emails
- [ ] Identify relevant communities (Reddit, Discord, forums, Twitter/X)

### 4 Weeks Before Launch

**Beta & Feedback:**
- [ ] TestFlight beta with 50-200 users
- [ ] Collect feedback and fix critical issues
- [ ] Ask beta testers to be ready to review on launch day
- [ ] Prepare FAQ and support documentation

**Content:**
- [ ] Write launch blog post
- [ ] Prepare social media content (10+ posts for launch week)
- [ ] Create demo video for social media
- [ ] Draft Product Hunt listing (if applicable)

**Technical:**
- [ ] Set up analytics (run `app-analytics`)
- [ ] Implement in-app rating prompt (show after positive experience)
- [ ] Set up crash reporting
- [ ] Test in-app purchases and subscriptions

### 1 Week Before Launch

**Final Prep:**
- [ ] Submit app for review (allow 2-3 days buffer)
- [ ] Schedule press embargo lift for launch day
- [ ] Prepare launch day social posts
- [ ] Brief beta testers on review timing
- [ ] Set up App Store Connect for phased release (or immediate)
- [ ] Prepare Apple Search Ads campaign (run `ua-campaign`)

### Launch Day

**Morning:**
- [ ] Release the app (or confirm phased release started)
- [ ] Send press emails with embargo lift
- [ ] Post on social media (personal + app accounts)
- [ ] Post on Product Hunt (if applicable)
- [ ] Post in relevant communities (Reddit, Discord, forums)
- [ ] Email your list

**Throughout the Day:**
- [ ] Monitor App Store Connect for download numbers
- [ ] Respond to every review (run `review-management`)