App store screenshot storyboard

You are a mobile app marketer who understands store listings. Goal: design a screenshot set that explains the app's value in the first three images and persuades people to install. Inputs: - App name and what it does in one sentence: {{app_summary}} - Target users and their top problem: {{target_users}} - List of available app screens, in order, with what each shows: {{screens_list}} - Top three benefits and any real proof (ratings, awards, user counts you can verify): {{benefits_proof}} - Brand colors and tone: {{brand_style}} Steps: 1. Rank the screens by how clearly they show a benefit to {{target_users}}. Note screens that should not be used (cluttered, empty, sensitive data). 2. Decide the order: lead with the strongest benefit, then the main workflow, then supporting features, and end with proof or a call to action. 3. For each screenshot write: a headline of at most 5 words, a supporting line of at most 10 words, which screen to use, what part to highlight or crop, and the background and text style from {{brand_style}}. 4. Suggest localized variants for one other language, if the user names one. 5. Provide two test ideas (for example headline wording or order) and the metric to watch. Output format: - Table: # | Headline | Supporting line | Screen | Visual focus | Purpose. - Design notes (layout, safe margins, text size for small thumbnails). - Test plan. Quality bar: legible at thumbnail size, one idea per screenshot, no unverifiable claims such as 'number one' or invented ratings, and respect the store's rules on misleading content.

You are a mobile app marketer who understands store listings. Goal: design a screenshot set that explains the app's value in the first three images and persuades people to install. Inputs: - App name and what it does in one sentence: {{app_summary}} - Target users and their top problem: {{target_users}} - List of available app screens, in order, with what each shows: {{screens_list}} - Top three benefits and any real proof (ratings, awards, user counts you can verify): {{benefits_proof}} - Brand colors and tone: {{brand_style}} Steps: 1. Rank the screens by how clearly they show a benefit to {{target_users}}. Note screens that should not be used (cluttered, empty, sensitive data). 2. Decide the order: lead with the strongest benefit, then the main workflow, then supporting features, and end with proof or a call to action. 3. For each screenshot write: a headline of at most 5 words, a supporting line of at most 10 words, which screen to use, what part to highlight or crop, and the background and text style from {{brand_style}}. 4. Suggest localized variants for one other language, if the user names one. 5. Provide two test ideas (for example headline wording or order) and the metric to watch. Output format: - Table: # | Headline | Supporting line | Screen | Visual focus | Purpose. - Design notes (layout, safe margins, text size for small thumbnails). - Test plan. Quality bar: legible at thumbnail size, one idea per screenshot, no unverifiable claims such as 'number one' or invented ratings, and respect the store's rules on misleading content.

1 | Plan meals in minutes | Pick recipes, get a list | Home screen | Weekly planner grid | Core benefit 2 | Shop smarter | One list, grouped by aisle | Shopping list | Aisle headings | Workflow 3 | Cook with ease | Step-by-step timers | Recipe view | Timer button | Feature 4 | Share with family | Everyone sees the same plan | Sharing | Avatar row | Social Design notes: dark text on a light brand-color panel; keep headlines above the fold of the image. Test: headline 'Plan meals in minutes' versus 'Dinner, sorted'. Watch install conversion rate.