Get your free design
For Flutter developers

One project, both stores.

TL;DR. Flutter apps ship to App Store and Play Store simultaneously. Mokbi exports both stores' required sizes from one design: iPhone 6.9", iPad 13", Galaxy S25 Ultra and Galaxy Tab S9 Ultra, in one ZIP per locale, then publishes it straight to both stores. No two separate workflows.

Flutter's strength is "one codebase, two stores". Most screenshot generators don't share that philosophy, they make you build the design twice, once at iPhone aspect ratios and once at Android. Mokbi is designed around the multi-platform reality: pick the devices you target, design once with the multi-panel composer, export a ZIP organized by platform → device → locale.

Flutter screenshot workflow

  1. Run your app on a real device or simulator. Capture the panels you want: a hero shot, the main feature, the killer use case. flutter screenshot works from the command line.
  2. Open Mokbi. Drop the PNG screenshots in. The auto-fit feature matches your image's aspect ratio to the chosen device frame so there's no letterbox.
  3. Build the carousel. 3–5 panels with captions; spanning layers (gradient bars, etc.) work across panels.
  4. Pick devices for both stores. iPhone 16 Pro Max (App Store 6.9") and Galaxy S25 Ultra (Play Store). Add iPad 13" and Galaxy Tab S9 Ultra for tablets.
  5. Translate to all relevant locales: Flutter apps usually target all 50 App Store + global Play markets.
  6. Export or publish. Download one ZIP (6.9"/, iPad 13"/, Galaxy/, each with per-locale subfolders), or push the whole listing straight to both stores.

Alternatives in the Flutter ecosystem

The screenshot pub package captures raw widget screenshots from your running app. Useful for capturing the source frames, but doesn't add marketing overlays. Same trade-off as Fastlane snapshot on the iOS side: real app capture vs designed marketing carousel.

The combination most Flutter teams settle on: flutter screenshot or the screenshot pub package for capturing panels from the real app, then Mokbi for the marketing composition and localized exports.

Handling iOS vs Android design conventions

Same app screenshot looks different in an iPhone frame vs a Pixel frame because of bezel thickness, notch geometry, and Android nav-bar conventions. Mokbi renders both correctly; you can toggle status bars on iOS (9:41 convention) and configure tilt angles per device class to keep the carousel coherent across both stores.

Learn: Features · Guides · Pricing

Open editor →