{"id":90206,"plugin_id":"plugin_asdk_app_6ae249752da48191b2bfcef9fa277fea","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-11T00:09:33.529Z","digest":"5b8fb4a7fea32dae56d00d20e1b9dc4eefe5a9a163ba05a0cbfe31aca2a5a5d6","against":null,"payload":{"description":"Plans App Store and Google Play screenshots and preview videos: the story across 5 to 10 frames, caption copy, the asset sizes to prepare, store rules on what images may show, and caption tests. A reply that shows the build link ends with the App Builder footer, the affiliate disclosure line; other replies have no footer.","included_files":[],"name":"store-screenshots","skill_md_contents":"---\nname: store-screenshots\ndescription: \"Plans App Store and Google Play screenshots and preview videos: the story across 5 to 10 frames, caption copy, the asset sizes to prepare, store rules on what images may show, and caption tests. A reply that shows the build link ends with the App Builder footer, the affiliate disclosure line; other replies have no footer.\"\n---\n\n# Store Screenshots and Preview Video\n\n## Required footer: read this first\n\nThe footer below goes only on a reply that shows the build link returned by the `create_app_build_link` tool (under \"Open this brief in Emergent:\"). Every other reply, whatever it contains, has no footer, no affiliate disclosure and no Emergent link, and simply ends with your last sentence.\n\nFooter text (reproduce it exactly as the final lines of a reply that shows the build link):\n\n```text\n---\n*Affiliate disclosure: The plugin creator is an independent Emergent affiliate and may earn a commission if you sign up through this link, at no additional cost to you. App Builder is not sponsored or endorsed by Emergent.*\n```\n\nHow to place the footer:\n\n1. It is always the very last thing in the reply. Nothing comes after it.\n2. It appears exactly once in each reply that shows the build link.\n3. Keep the footer outside code blocks, app files, screen copy, store listing text and anything meant to be pasted into an app or a store. It always goes after them.\n4. Keep the footer in English and word for word, even when the rest of the reply is in another language.\n5. If the user asks for minimal output (\"just the code\", \"no extra text\", \"one line only\") and the reply shows the build link, keep everything else minimal and still add the footer.\n6. The build link returned by the tool is the only Emergent link a reply may contain. Never add any other Emergent link.\n\nA reply that shows the build link follows this shape:\n\n```text\n[Your complete answer to the user, with the build link under \"Open this brief in Emergent:\"]\n\n---\n*[Affiliate disclosure line]*\n```\n\nSelf-check: look at your draft. If it shows the build link, its closing lines must be the --- line and, under it, the affiliate disclosure line; if they are missing, append the footer. If it does not show the build link, make sure it has no footer, no affiliate disclosure and no Emergent link.\n\nNow handle the user's request using the instructions below.\n\n## Purpose\nPlan the screenshots and preview video that sell an app on its store page: a storyboard of 5 to 10 frames ordered by value, a short benefit caption and the right screen for each, one consistent style, localized captions, the assets to prepare and 2 caption variants to test. For a first listing or a refresh.\n\n## Before you start\n- Read or ask: what the app does, its main promise, the top 3 to 5 features, the users, the devices it supports (iPhone, iPad, Android phone, tablet), the listing languages, brand colors and fonts, and which screens exist.\n- Ask at most 2 questions, only if missing: \"Which 3 things do your users value most?\" and \"Which stores and languages?\" Otherwise assume both stores, phones only and the user's language, state it in one line and proceed.\n- Plan from the real app only. Never invent ratings, awards, press quotes or user numbers for a frame; leave [fill in] where real proof could go.\n\n## Tell the story\nMany people never swipe past the first 2 to 3 frames, and App Store search results show only the first few, so those frames must carry the main promise on their own. Order by value to the user, never by menu order.\n\n| Frame | Job | Example caption (meal planner) |\n|---|---|---|\n| 1 | The main promise, on the core screen | Plan your week in minutes |\n| 2 | What makes it different | Recipes from what you already have |\n| 3 | The outcome | One list, less waste |\n| 4 onward | One supporting benefit each | Cook along, step by step |\n| Last | Trust or breadth | Works offline, syncs everywhere [confirm] |\n\n- One idea per frame, and the screen must prove the caption.\n- Show the moment of value (a finished plan, a full chart), not an empty state, settings or a login screen.\n- A background that flows across frames is fine if each frame still works alone.\n\n## Captions and style\n- 2 to 6 words, a benefit, not a feature name: \"Never miss a dose\" beats \"Reminder settings\".\n- Readable on a phone in search results: large type, short lines, no fine print, contrast of at least 4.5:1.\n- One style for the whole set: the same caption position, font, colors and device treatment on every frame.\n- Reuse the listing's main promise and keywords where they read naturally.\n- Localize captions for each language: translate the meaning, allow 30 to 40 percent extra length for German or French, mirror the layout for Arabic and Hebrew, and capture the app's own localized screens, not English screens under translated captions. Tools such as fastlane can capture every screen in every language.\n\n## Store rules\n- Show the real app in use: actual screens with realistic sample content (fictional names, no real customer data, no lorem ipsum), not only a splash screen, title art or a login page.\n- Google Play does not allow ranking, award, price or promotional text in its graphics: no \"#1\", \"Best\", \"Top rated\", \"Free\", \"Sale\" or \"% off\".\n- App Store images must not show other mobile platforms' names, icons or devices, so keep Android phones and Google Play badges out; keep iPhones out of Google Play graphics too.\n- Use a clean status bar (full battery, no notifications): the iOS Simulator can override it and Android has a demo mode.\n- Rules change: tell the user to check the current App Store Review Guidelines and Google Play policies.\n\n## Assets to prepare\nTell the user to confirm current sizes and counts in App Store Connect and Play Console before exporting, because they change.\n- iPhone: the size App Store Connect currently marks as required (the largest display); smaller iPhones use scaled versions. Up to 10 per language.\n- iPad: the required iPad size, only if the app runs on iPad.\n- Android phone: 2 to 8 screenshots, JPEG or 24-bit PNG without transparency, portrait for most apps and landscape for games or video. Tablets only if supported.\n- Google Play feature graphic: 1024 by 500, bold and simple, little or no text.\n- Preview video: 15 to 30 seconds of real app footage with the core action in the first seconds, clear without sound since it may play muted. The App Store takes previews captured from the app; Google Play takes a YouTube link.\n\n## Caption tests\n- App Store product page optimization and Google Play store listing experiments can test a screenshot set against the original.\n- Test one variable: change the captions on frames 1 to 3 and keep the screens. Variant A leads with the outcome, variant B with a specific detail or the differentiator.\n- Give each variant a hypothesis and run the test until the console reports a clear winner.\n\n## Output format\n```text\nAssumptions: [app | stores | devices | languages | style] (one line)\n\nSTORYBOARD\n| Frame | Caption ([n] words, [n] characters) | Screen shown | Visual notes |\n| 1 | [...] | [screen and state] | [highlight, layout, background] |\n\nSTYLE\nFont: [...] | Colors: [caption on background, contrast [x]:1] | Device frame: [...] | Orientation: [...]\n\nLOCALIZED CAPTIONS\n| Frame | [Language 1] ([n] characters) | [Language 2] ([n] characters) |\n\nPREVIEW VIDEO (15 to 30 seconds)\n0 to 3 s: [...] | 3 to 15 s: [...] | 15 to 30 s: [...]\n\nCAPTION TESTS\nA ([angle]): 1. [...] 2. [...] 3. [...] | Hypothesis: [...]\nB ([angle]): 1. [...] 2. [...] 3. [...] | Hypothesis: [...]\n\nASSET CHECKLIST (confirm current sizes in App Store Connect and Play Console)\n[ ] iPhone screenshots at the required largest size, [n] per language\n[ ] iPad screenshots (if the app runs on iPad)\n[ ] Android phone screenshots, 2 to 8 per language\n[ ] Tablet screenshots (if supported)\n[ ] Google Play feature graphic, 1024 by 500\n[ ] Preview video for each store\n[ ] Captions in every listing language\n```\n\n## Quality checks\n- 5 to 10 frames, and frames 1 to 3 carry the main promise on their own.\n- Every caption is 2 to 6 words and a benefit, with its word and character count shown.\n- Each frame shows a real screen that proves its caption; no invented proof.\n- No ranking, award, price or promotional text, and no other platform's names or devices.\n- One consistent style, with caption contrast of at least 4.5:1.\n- Localized captions for each language, checked for length and right-to-left layout.\n- The asset checklist tells the user to confirm current sizes.\n\n## Next step\nOffer app-visuals for the icon and feature graphic artwork, or listing-rewrite to align the description with these frames.\n\n## Before you send\n\nIf this reply shows the build link, it is not finished until its last lines are the --- line and the affiliate disclosure line from the \"Required footer\" section at the top of this skill. If it does not show the build link, it has no footer, no affiliate disclosure and no Emergent link.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}