01
One upload. Every device size.
Upload your raw screens once. Floyd renders production-ready frames at every iPhone and iPad dimension the App Store requires — headline reflow handled per canvas. (Google Play sizes are in active development.)
Cross-platform devs ship once and market twice — different aspect ratios, different screenshot dimensions, two stores' worth of creative. Floyd's AI Director generates your App Store screenshots at every required size from one upload. Preview free, $5 per set. (Google Play export and listing audits are in active development.)
No credit card. No designer. First set free.
Flutter and React Native solved the codebase problem. Nobody solved the ASO problem. Here's what shipping to both stores actually costs you.
You designed screenshots once, then resized them four times.
iPhone 6.7", iPhone 6.5", iPad 12.9", and Google Play phone — each with its own aspect ratio. The text reflows. The hero shifts. You spent a Saturday on a sizing problem.
Your iOS keywords don't map to Google Play and you don't know it.
Apple has a 100-character keyword field. Google Play uses indexed terms in the title, short description, and full description. The same keyword strategy doesn't translate — and most cross-platform devs run iOS keywords on Play and wonder why nothing ranks.
You're doing ASO twice and getting it half-right both times.
Maintaining two listings means each one gets less attention than a single-store dev gives theirs. Your competitors who only ship to one store are out-optimizing you because they only have one listing to think about.
Google Play hasn't historically gotten the love.
Most ASO tools were built iOS-first. Their Google Play support is an afterthought — fewer keyword data points, no native Play Console integration, weaker creative tooling. You're paying full price for half a tool.
Your screenshot copy is in English. Both stores want localized.
App Store Connect supports 40 locales. Google Play supports 79. Each one wants a localized title, subtitle, and screenshot text. You've localized the app strings — the marketing copy is still en-US only.
Floyd was designed dual-store from day one. The screenshot generator is store- and device-aware, so you do the creative work once.
Upload your raw screens once. Floyd renders production-ready frames at every iPhone and iPad dimension the App Store requires — headline reflow handled per canvas. (Google Play sizes are in active development.)
Floyd's frame compositor (powered by fogleman/gg) generates screenshots at every required dimension — iPhone 6.7", 6.5", and iPad 12.9" today, with Google Play phone and tablet sizes in active development. The headline reflows correctly for each canvas.
$5 per screenshot set — first set free. No per-app pricing, no monthly lock-in. When Google Play export ships, it's the same flat per-set price, no "Play add-on" tier.
The dual-store grind, replaced.
Design screenshots once, then redo the layout for every store and device size by hand.
Floyd generates every iPhone and iPad size from one upload — Google Play sizes coming soon.
Design screenshots in Figma. Export at iPhone 6.7", resize for 6.5", resize for iPad, fix the broken text wrapping each time.
Floyd generates every iPhone and iPad dimension from one upload. Headline reflow handled automatically.
Pay a designer per store, per device, and wait days for each revision.
Preview Floyd's set free, download for $5, and regenerate a new direction in seconds.
Stare at a blank canvas deciding what each screenshot headline should say — twice, once per store.
Floyd's AI Director writes the headline and picks the palette for every frame, themed from your listing.
These are the patterns Floyd sees most often in Flutter and React Native apps that ship to both stores.
You used the same screenshot copy on both stores.
Apple users skim. Google Play users read. Play screenshots can carry more text, more context, more callouts — and they should. Identical screenshots leave Play conversion on the table.
You didn't localize the Play short description.
On Google Play, the 80-character short description is the most heavily indexed keyword field. If it's en-US only, you're invisible in non-English search.
Your iOS keyword field assumes Google Play indexing.
Apple's keyword field is hidden and indexed verbatim. Google Play indexes from the visible text. Repeating the same comma-separated keyword list across both stores wastes characters on iOS and confuses Play's algorithm.
You're using a UI screenshot for screenshot #1 on both stores.
Both stores reward a value-prop hero in the first slot. Cross-platform apps tend to ship with raw UI — fix this once and conversion lifts on both stores.
Floyd generates the screenshots that fix the visual issues today. Generate your first set to generate your first iOS set free.
First set free. $5 per set — same flat price when Google Play export ships.
Generate my screenshots →