Prepare Flutter screenshots for the App Store and Google Play

1. Choose the build, device and demo content

Write down the app version, platform, device and language before capturing. Open a demo account with fictional content and navigate to a screen that demonstrates a real capability. Wait for images, fonts and network data to settle. Keep permission dialogs, debug banners and temporary notifications out of the capture by preparing the app state itself.

Flutter's CLI documents devices, run and screenshot commands. Use the help shipped with your installed SDK for target-specific options; device support and project build configuration matter. A successful command alone does not establish that the app state or image is suitable for a store listing.

flutter --version
flutter devices
flutter help screenshot
flutter screenshot

2. Review the capture before designing

1. Open the saved image at its original size. Check text rendering, icons, safe areas and any clipped scrollable content.
2. Compare the captured state with the release build you intend to ship. Remove demo-only features from the story if customers cannot access them.
3. Capture iOS and Android independently when their controls or layout differ. A device frame does not transform one platform's UI into the other.
4. Save an untouched source copy. Give files stable sequence names such as 01-overview and 02-create-task, then add platform and locale folders around them.

3. Build an editable screenshot set in Skir

Choose an existing library template and set Screenshot platform before opening it. Replace the illustrative app image with your Flutter capture. Keep that image intact: use Skir's editable text layers for the surrounding message rather than reconstructing the app's buttons or labels as marketing text.

For a hypothetical habit tracker, the first image might show the day's habits, the second show recording a completed habit, and the third show the history screen. Each caption should describe what the image proves. If your app has no history view, choose another real action instead of adapting the story to fit a template.

4. Handle text and layout changes deliberately

Flutter text scale, translated labels and different device proportions can change the screen you capture. Re-capture those states in the app, then review the surrounding headline separately. Shorten an overcrowded headline before shrinking it until it becomes unreadable. Keep important UI away from the crop edge and inspect any frame corners against the actual screenshot.

A screenshot checker can measure a file's dimensions and format, but it cannot decide whether the depicted Flutter UI is accurate. Treat visual approval and file validation as separate release checks.

5. Export and hand off the exact files

Wait for the project to save, export the available screenshots and unzip the download. Check dimensions, alpha, orientation and order on the exported PNGs or JPEGs. Keep the approved ZIP alongside the app version and locale notes so a later release can reproduce the same sequence.

This workflow uses external Flutter capture and manual image import into Skir. It does not require a Flutter plugin, and Skir does not run Flutter tests or publish your store listing. For repeat releases, automate stable app capture first and keep final artwork approval explicit.