App Store Optimizer

Keyword Research Workflow:
1. Brainstorm seed keywords
   ├── Core functionality terms
   ├── Problem/solution terms
   ├── Competitor brand terms (careful - avoid trademarked terms)
   └── User language terms (how users describe the problem)

2. Expand keyword list
   ├── App Store Suggest (type in search bar, note autocomplete)
   ├── Google Play autocomplete
   ├── ASO tools (App Radar, Sensor Tower, AppTweak)
   ├── Related searches shown after search results
   └── Competitor keyword spy tools

3. Evaluate keywords
   ├── Search volume (traffic score)
   ├── Difficulty (competition score)
   ├── Relevance (does it match your app?)
   └── Intent (will searchers want your app?)

4. Prioritize keywords
   ├── High volume + low difficulty + high relevance = PRIORITY
   ├── High volume + high difficulty = LONG TERM
   ├── Low volume + low difficulty = QUICK WIN
   └── Low volume + high difficulty = AVOID

5. Place keywords strategically
   ├── Most important → App name
   ├── Second tier → Subtitle (iOS) / Short description (Android)
   ├── Supporting → Keyword field (iOS) / Description (Android)
   └── Do NOT repeat keywords across fields (iOS deduplicates)

iOS Keyword Optimization Rules:
- Keywords are pulled from: Name + Subtitle + Keyword field
- Do NOT repeat words across these three fields
- Keyword field: Use commas as separators, no spaces after commas
- Apple indexes singular and plural forms separately
- Include common misspellings if space allows
- Localize keywords for each target market

Example:
  Name: "FitTrack - Workout Planner"
  Subtitle: "Exercise & Gym Log"
  Keywords: "fitness,training,health,routine,muscle,cardio,strength,weight,body,yoga"

  Effective indexed terms:
  fittrack, workout, planner, exercise, gym, log, fitness, training,
  health, routine, muscle, cardio, strength, weight, body, yoga
  + combinations like "fitness planner", "gym workout", etc.

Google Play Keyword Optimization Rules:
- Google indexes the full description (all 4000 chars)
- Repeat primary keywords 3-5 times naturally in description
- Short description is heavily weighted - use top keywords
- Title has highest weight per character
- Google understands synonyms and related terms
- Backlinks with anchor text influence ranking
- Do NOT keyword-stuff; Google penalizes this

Example Short Description (80 chars):
  "Track workouts, build muscle & reach fitness goals with personalized plans"

Recommended Screenshot Order:
1. Hero shot - Primary value proposition + most impressive UI
2. Key feature 1 - The feature that solves the main user problem
3. Key feature 2 - Differentiating feature vs. competitors
4. Social proof - "Trusted by 1M+ users" or press quotes
5. Key feature 3 - Another compelling feature
6. Integration/ecosystem - Works with other tools/platforms
7. Personalization - Show customization options
8. Call to action - "Get started free" or pricing info

Screenshot A/B Test Framework:
├── Test one variable at a time
│   ├── Background color
│   ├── Text copy
│   ├── Screenshot order
│   ├── With/without device frames
│   └── Dark vs. light UI shown
├── Run for 7+ days minimum
├── Need 1000+ impressions per variant for significance
├── Use Google Play Store Listing Experiments (built-in)
├── Use third-party tools for iOS (SplitMetrics, StoreMaven)
└── Track conversion rate (impressions → installs)

Review Response Decision Tree:
├── 5-star review
│   └── Thank the user briefly, mention a new feature they might like
├── 4-star review
│   ├── Thank them, ask what would make it 5 stars
│   └── If they mention a specific feature, note it for product roadmap
├── 3-star review
│   ├── Acknowledge their feedback
│   ├── Address specific concerns
│   └── Invite them to contact support for resolution
├── 2-star review
│   ├── Apologize for the experience
│   ├── Address the specific issue
│   ├── Provide a workaround if available
│   └── Ask them to update review after fix
├── 1-star review
│   ├── Respond within 24 hours
│   ├── Never be defensive
│   ├── Provide direct support contact
│   ├── If it is a bug, confirm you are fixing it
│   └── If it is a misunderstanding, clarify politely
└── Spam / inappropriate review
    └── Report to Apple/Google for removal

Bug Report (1-2 stars):
"Hi [Name], we're sorry you experienced this issue. We've identified the
bug you described and our team is working on a fix for the next update.
In the meantime, you can [workaround]. If you need immediate help,
please reach out to support@myapp.com. Thank you for your patience."

Feature Request (3 stars):
"Thank you for the feedback! We hear you on [feature request]. It's on
our roadmap and we're aiming to include it in an upcoming release.
We'd love to hear more about your use case at feedback@myapp.com."

Positive Review (5 stars):
"Thank you so much for the kind words! We're thrilled you're enjoying
[specific feature mentioned]. Have you tried [related feature]? We think
you'll love it too!"

Rating Prompt Triggers (Best Practices):
├── After a positive experience
│   ├── Completing a key task successfully
│   ├── Reaching a milestone or achievement
│   ├── After the Nth successful session (e.g., 5th)
│   └── After a positive outcome (workout completed, goal reached)
├── Timing constraints
│   ├── NOT on first launch
│   ├── NOT after a crash or error
│   ├── NOT during a flow (checkout, editing)
│   ├── Maximum 3 prompts per 365-day period (Apple limit)
│   └── Wait at least 14 days between prompts
├── Smart gating approach
│   ├── First: Ask "Are you enjoying [App]?" in custom dialog
│   ├── If YES → Show native rating prompt (SKStoreReviewController)
│   ├── If NO → Show feedback form (capture issues internally)
│   └── This prevents negative reviews from reaching the store
└── Never incentivize reviews (violates store guidelines)

// iOS rating prompt implementation
import StoreKit

class RatingManager {
    private let defaults = UserDefaults.standard
    private let sessionCountKey = "sessionCount"
    private let lastPromptDateKey = "lastPromptDate"

    func trackSession() {
        let count = defaults.integer(forKey: sessionCountKey) + 1
        defaults.set(count, forKey: sessionCountKey)
    }

    func requestReviewIfAppropriate() {
        let sessionCount = defaults.integer(forKey: sessionCountKey)
        let lastPrompt = defaults.object(forKey: lastPromptDateKey) as? Date

        guard sessionCount >= 5 else { return }
        guard lastPrompt == nil || Date().timeIntervalSince(lastPrompt!) > 90 * 86400 else { return }

        if let scene = UIApplication.shared.connectedScenes
            .first(where: { $0.activationState == .foregroundActive }) as? UIWindowScene {
            SKStoreReviewController.requestReview(in: scene)
            defaults.set(Date(), forKey: lastPromptDateKey)
        }
    }
}

Localization Priority Framework:
1. Analyze current organic traffic by country (App Store Connect / Play Console)
2. Estimate market size (smartphone users * app category penetration)
3. Assess competition level in each market
4. Consider monetization potential (ARPU by country)
5. Evaluate localization cost vs. expected return

Tier 1 (highest ROI): English, Spanish, Portuguese, French, German, Japanese
Tier 2: Korean, Italian, Dutch, Russian, Turkish, Arabic
Tier 3: Thai, Vietnamese, Indonesian, Hindi, Polish, Swedish

Minimum viable localization:
- Translate: Name, subtitle/short description, keywords, screenshot text
- Do NOT auto-translate descriptions (use native speakers)
- Localize screenshots (text overlays + possibly UI screenshots)
- Research local keywords (direct translation often misses search terms)

Category Selection Decision:
├── Primary category
│   ├── Choose the most accurate category for your app
│   ├── Consider competition density (fewer apps = easier ranking)
│   ├── Check top 10 in each candidate category
│   └── Verify your app legitimately fits the category
├── Secondary category (iOS only)
│   ├── Choose a complementary category for additional exposure
│   ├── Can rank in both categories simultaneously
│   └── Example: Meditation app → Primary: Health & Fitness, Secondary: Lifestyle
└── Category changes
    ├── Allowed (both platforms)
    ├── Takes effect with next update
    └── Rankings reset in old category

For each top 5 competitor, analyze:

1. Metadata
   ├── Title / subtitle keywords
   ├── Description structure and keywords
   ├── Number and quality of screenshots
   └── Whether they use app preview videos

2. Ratings & Reviews
   ├── Average rating and total count
   ├── Recent review sentiment trends
   ├── Common complaints (opportunities for you)
   └── Features users praise most

3. Update Frequency
   ├── How often they update
   ├── What they highlight in release notes
   └── Feature velocity

4. Keyword Rankings
   ├── Which keywords they rank for
   ├── Keywords where they are weak (your opportunity)
   └── Keyword overlap percentage with your app

5. Visual Assets
   ├── Screenshot style and messaging
   ├── Icon design approach
   └── What they emphasize first