For Expo and EAS Submit workflows.
Expo's selling point is shipping iOS apps without a Mac. Most screenshot tooling breaks that promise — Fastlane snapshot needs Xcode, the simulator's screenshot keybind needs a Mac, and AppCenter screenshot uploaders need a build from Mac infrastructure. Screenshotify runs entirely in the browser, so the no-Mac story stays intact through the marketing-asset step.
Where Screenshotify fits in EAS Submit
EAS Submit handles the upload-binary part of App Store / Play Store deployment. It does not handle screenshot creation — you provide those separately. Workflow:
- Capture source frames from
npx expo starton a real device or simulator. Expo Go works for this. - Open Screenshotify in the same browser, paste or drop the screenshots. WebRTC pairing connects your phone for direct transfer if you don't want to AirDrop.
- Design the marketing carousel — captions, device frames, locale variants.
- Export the ZIP at App Store + Play Store sizes.
- Upload manually to App Store Connect (under Screenshots per locale) and Play Console (under Store Listing → Graphic assets). EAS Submit itself only handles the binary, not the marketing assets.
What about Expo's screenshot APIs?
expo-screen-capture blocks screenshots at runtime (security feature for sensitive apps), not a generator. There's no Expo-native equivalent of Fastlane snapshot or a marketing-composer. Screenshotify fills that gap from the browser side.
Tips for Expo apps specifically
- Don't include the Expo splash screen in marketing screenshots. The default branded splash signals "boilerplate" — capture the actual app's main view instead.
- Native UI in EAS Build differs from Expo Go. Take screenshots from the actual EAS-built version, not from Expo Go, since some layouts shift between the two.
- Universal apps need both iPad and iPhone screenshots. EAS Submit accepts either, but App Store Connect won't ship the app to iPad without an iPad screenshot set.