Add screenstack_sdk to your Flutter project, declare your screens in screenstack.yml, and ScreenStack composites them at every App Store and Play Store size on every CI run — inside real device frames, with your brand backdrops and captions.
● captured by @voostack/screenstack-sdk against this very site
If your Flutter project already runs on FlightStack, wiring ScreenStack takes one block. If it doesn't, the SDK runs equally well on GitHub Actions, GitLab CI, or any container.
One dependency. Flutter 3.16+ on iOS, Android, and Web. Uses the standard integration_test harness — no native plumbing.
# pubspec.yaml
dev_dependencies:
screenstack_sdk: ^3.1.0
integration_test:
sdk: flutterOne block per screen. Device profiles + test users are resolved at run time from your CI environment — credentials never live in the file.
project: prj_abc123
deviceProfile: iphone-15-pro-max
testUser:
secretRef: ssr_xxx
screens:
- route: /home
targets: ["iOS/Home", "Play/Home"]
- route: /dashboard
targets: ["iOS/Dashboard"]Same five tasks, two workflows. One eats an afternoon of every release; the other runs while you push.
Composite once in the editor, export every Apple- and Google-required size at native pixel density.
iPhone 16 Pro Max, 15 Pro Max
iPhone 11 Pro Max, XS Max
iPhone 8 Plus
Required for iPad apps
Mid-tier iPad slot
Tablets at 1200 × 1920
Full reference of every supported dimension on /screenshot-sizes.
The SDK piggybacks on your existing integration tests. If you can tap a button in a widget test, you can declare a screen target.
If your project has a Flutter app and a marketing site, both SDKs feed the same editor project. Web Capture keeps the landing in sync with prod.
The flightstack/screen-stack job handles secret distribution + run scheduling. One config block, no boilerplate.
Free tier includes every store size and 5 exports a month. Wire the SDK in once and your store assets refresh on every CD run, forever.