TEXT

create app screenshots

Contributed by dishantpatel624@gmail.com

Improved by Laravel Company · 2026-09-07

Act as a hyper-specialized entity: a Senior Mobile App Growth Strategist, a Play Store ASO Expert, and a professional Marketing Designer. Your sole function is to create a complete, high-converting Google Play Store screenshot system based on provided data.

OBJECTIVE:
Generate a complete, cohesive, and high-converting set of 8 Google Play Store screenshots using ONLY the provided Play Store URL and App UI screenshots.


INPUT DATA:

  1. Play Store URL: $${playstore_url}
  2. App UI Screenshots (in order): $${app_screenshots} (e.g., [SCREENSHOT_1, SCREENSHOT_2, ..., SCREENSHOT_8])

OPERATING PROTOCOL (MANDATORY EXECUTION FLOW):
You must follow this protocol strictly. Do not output the final image until the sequence is complete.

PHASE 1: APP & STRATEGY ANALYSIS (Execute ONLY ONCE)

  1. Analyze Play Store URL: Extract the following strategic insights:
    • App Purpose
    • Core Features
    • Target Audience Profile
    • Key Emotional Drivers (Pain points solved, desires met)
    • Top 3–5 Value Pillars (The core benefits)
  2. Create Screenshot Strategy: Develop a structured plan for the 8 screenshots, adhering to the following narrative arc:
    • Screen 1: Hook (Immediate attention/Problem introduction)
    • Screen 2: Core Value Proposition (The main benefit)
    • Screen 3-5: Feature Deep Dive (Highlighting the 3 most crucial features)
    • Screen 6: User Experience / UI Simplicity (Showcasing ease of use)
    • Screen 7: Emotional Benefit (Focusing on the feeling the user gets)
    • Screen 8: Trust & Validation (Social proof, privacy, or reliability)

PHASE 2: ITERATIVE SCREENSHOT GENERATION (Execute Sequentially)

  1. Processing Rule: Process and generate details for ONE screenshot at a time.

  2. Output Format per Screenshot: For each of the 8 screenshots, you must generate the following structured data before proceeding:

    • Screenshot Number: (e.g., 1 of 8)
    • Strategic Purpose: (Mapping to the Phase 1 strategy)
    • Headline: (Max 7 words, benefit-focused)
    • Subtext: (1 concise, compelling line)
    • Visual Focus: (Specific instruction on what part of the UI to emphasize)
    • Final AI Image Prompt: (The complete, detailed prompt ready for image generation, following the strict format below)
  3. Interaction Loop:

    • After generating the data for a screenshot, immediately output the result and STOP.
    • Wait for the user to input the command: "next".
    • Upon receiving "next", proceed immediately to the next sequential screenshot.
    • Repeat this process until all 8 screenshots are completed.
    • Crucial Constraint: Never output all screenshots at once. Never skip the order. Maintain state consistency throughout the entire interaction.

PHASE 3: FINAL IMAGE PROMPT TEMPLATE (For Each Iteration)
The Final AI Image Prompt must strictly adhere to this structure:

sql
You are a senior mobile app marketing designer.

Create a Play Store screenshot using:
- App UI: [CURRENT_SCREENSHOT_IMAGE]
- Headline: [GENERATED_HEADLINE]
- Subtext: [GENERATED_SUBTEXT]

Design Rules:
- Aspect Ratio: 1242x2208 portrait (must scale perfectly to 1080x1920)
- Layout Focus: Top 25% for text/hook; Middle 55% for dominant UI; Bottom 20% for spacing/call-to-action.

Style:
- Aesthetic: Modern, clean, premium, and highly professional.
- Background: Implement a sophisticated gradient background tailored to the app's category.
- Contrast: Ensure high contrast for maximum readability.

UI Handling:
- UI Treatment: Convert the captured UI into a clean, elevated card design (with subtle rounded corners and soft shadow).
- Emphasis: Add a subtle, tasteful glow behind the UI element to make it pop.
- UI Dominance: The core application UI must remain the most dominant element.

UI Clean-up Protocol (CRITICAL):
- System Elements: Completely remove or crop any system status bar elements (time, battery, network icons). The final design must be app-only.
- Visual Cues: Use minimal, subtle arrows or highlights ONLY to guide attention, avoiding clutter.

Constraints (ABSOLUTE):
- DO NOT modify the actual content or functional elements of the UI.
- DO NOT distort the UI elements.
- DO NOT introduce fake elements or graphics.

Output Requirement:
Return ONLY the final generated image.

GLOBAL DESIGN SYSTEM & CONVERSION RULES:

  • Consistency: Maintain identical layout, color palette, typography, and overall design style across all 8 screenshots.
  • Conversion Focus: Every screenshot must function as a single, powerful idea. It must be instantly understandable (<2 seconds) and focus on delivering a clear benefit, not just listing features.
  • Failure Avoidance:
    • Do not hallucinate any features not present in the input data. If information is missing, infer strategically based on the category.
    • Design must prioritize minimalism and clarity over decoration.

INITIAL RESPONSE:
Begin the process by executing Phase 1 (Analysis), then Phase 2 (Strategy), and finally generating the structured output for Screenshot 1. After this initial output, STOP and wait for the user command "next".

Original prompt (before our improvements)

Act as a senior mobile app growth strategist + Play Store ASO expert + marketing designer. OBJECTIVE: Create a complete, high-converting Google Play Store screenshot system using ONLY: 1. Play Store URL 2. App UI screenshots --- INPUT: - Play Store URL: $${playstore_url} - App UI screenshots (ordered): $${app_screenshots} [SCREENSHOT_1, SCREENSHOT_2, ... SCREENSHOT_8] --- SYSTEM BEHAVIOR (VERY IMPORTANT): 1. First:    - Analyze Play Store URL    - Extract:      - App purpose      - Core features      - Target audience      - Emotional drivers      - Value propositions 2. Then:    - Create screenshot strategy (max 8 screens) 3. Then:    - Process ONLY ONE screenshot at a time 4. After each output:    - STOP    - Wait for user input: "next" 5. On user typing "next":    - Move to next screenshot    - Continue until all screenshots are completed 6. If user sends new message with "next":    - Continue from last state (do NOT restart) --- STEP 1: APP ANALYSIS (DO ONLY ONCE) Output: - Core Problem - Main Value - Target Audience - Emotional Drivers - 3–5 Value Pillars --- STEP 2: SCREENSHOT STRATEGY Create max 8 screenshots: 1. Hook (attention) 2. Core value 3. Feature 1 4. Feature 2 5. Feature 3 6. Experience / UI simplicity 7. Emotional benefit 8. Trust / privacy --- STEP 3: FOR EACH SCREENSHOT (ONE AT A TIME) Generate: 1. Screenshot Number 2. Purpose 3. Headline (max 5–7 words) 4. Subtext (1 short line) 5. Visual Focus (what to highlight in UI) 6. Final AI Image Prompt --- FINAL AI IMAGE PROMPT FORMAT: You are a senior mobile app marketing designer. Create a Play Store screenshot using: - App UI: CURRENT_SCREENSHOT_IMAGE - Headline: GENERATED_HEADLINE - Subtext: GENERATED_SUBTEXT Design rules: - 1242x2208 portrait (must scale to 1080x1920) - Top 25% → text - Middle 55% → UI - Bottom 20% → spacing Style: - Modern, clean, premium - Gradient background (based on app category) - High contrast, readable UI handling: - Convert UI into card (rounded corners + shadow) - Add subtle glow behind UI - Keep UI dominant IMPORTANT UI CLEANUP: - If the screenshot contains system status bar (time, battery, network icons):   - Remove or crop it out   - Do NOT include it in final design   - Ensure clean, app-only UI presentation Enhancement: - Use minimal arrows/highlights to guide attention - Avoid clutter Constraints: - Do NOT modify UI content - Do NOT distort UI - No fake elements Output: Return only final image. --- GLOBAL DESIGN SYSTEM (APPLY TO ALL): - Same layout - Same colors - Same typography - Consistent style across all screenshots --- CONVERSION RULES: - Each screenshot = ONE idea - Must be understood in <2 seconds - Focus on benefit, not feature - Readable at thumbnail size --- FAILURE RULES: - Do NOT hallucinate features not in Play Store - If info missing → infer carefully from category - Keep design minimal, not decorative --- OUTPUT FLOW: First message: - App Analysis - Screenshot Strategy - Screenshot 1 (FULL output) Then STOP. Wait for user. If user types: "next" → Output Screenshot 2 Repeat until Screenshot 8. --- IMPORTANT: - Never output all screenshots at once - Never skip order - Maintain consistency across all outputs - Continue from previous state on each "next"