Cross-Platform App Screenshot Design: One Workflow for iOS, Android and HarmonyOS

One app, three sets of screenshots for iOS, Android and HarmonyOS: just thinking about it makes you want to give up, right?

Many indie developers make one set of iOS screenshots, scale them, and throw them at Google Play and Huawei AppGallery. The result? Cropping from the wrong size, rejections for the wrong device frame, text cut off on Android...

Cross-platform screenshot design is a hassle, but it's far less difficult than you think. The key is using the right method.

Screenshot specs for the three major platforms

For overseas developers: HarmonyOS is Huawei's operating system, and apps for it are distributed through Huawei AppGallery; in mainland China, Android apps are also distributed through phone makers' own stores such as Xiaomi, OPPO and vivo.

Size comparison

The core difference: the App Store is tall and narrow (19.5:9), while the other platforms use standard 16:9. You can't reuse images directly, but you can share the design logic.

Review requirement differences

A design-once, export-to-three workflow

Step 1: Design the "core content layer"

Don't start by opening a canvas at one platform's size. First make a pure content layer containing only text, app UI and feature icons, without device frames or backgrounds.

Principles for the content layer:

• Text takes up no more than 30% of the area
• The core visual is centered
• Leave 15% blank space on every side (to adapt to different ratios)

Step 2: Build "layout templates"

Make a layout template for each ratio:

19.5:9 template (App Store)

[  Headline (large)        ]
[                          ]
[  App UI + device frame   ]
[                          ]
[  Feature tags (small)    ]

16:9 template (Google Play / Huawei, etc.)

[  Head-  |                ]
[  line   |  App UI        ]
[  text   |  + device      ]
[  Feat 1 |    frame       ]
[  Feat 2 |                ]

16:9 has more horizontal space, so you can use a split layout with text on the left and the visual on the right.

Step 3: Swap device frames

This is the most commonly overlooked step. The three sets should use three different device frames:

• App Store → iPhone 15 Pro / iPhone 16 frame
• Google Play → Pixel 8 / Samsung Galaxy S24 frame
• Huawei AppGallery → Huawei Mate 60 frame

Why it matters:

1. Review compliance: both Apple and Huawei may reject screenshots that use a competitor's device frame
2. User trust: Android users who see an iPhone frame feel "this isn't for me"
3. Conversion: a matching device frame helps users picture themselves using the app

Step 4: Adjust copy and colors

Each platform has a different cultural feel, and small tweaks can improve results:

Step 5: Export and check

Pre-export checklist:

• Sizes exactly match the target platform
• Text is readable at thumbnail size
• Device frames are correct
• File sizes are within limits
• The number of screenshots is within the allowed range
• Nothing is cut off or covered

3 time-saving tips

Tip 1: Use Figma's component system

Create a Figma file containing:

• One "content" component (text + app UI)
• Three "layout" variants (19.5:9 / 16:9 portrait / 16:9 landscape)
• Three "device frame" variants

When you edit the content component, every layout updates automatically.

Tip 2: Generate in bulk with AI

If you don't want to adjust each one by hand, use AppShot Maker (appshotmaker.com). Enter your copy and images once, and it automatically generates screenshots for the App Store, Google Play, Huawei and other platforms, with the matching device frames and size specs.

Tip 3: Prioritize

If you only have time for two sets, the priority is:

1. App Store (users most willing to pay)
2. Google Play (widest reach)
3. Huawei/Xiaomi/OPPO (incremental growth in the Chinese market)

Summary

Cross-platform screenshots don't need to be designed from scratch three times. One content design + three layout adaptations = efficient output for three platforms.

Remember the 5 steps:

1. Make the pure content layer first
2. Build a layout template for each ratio
3. Swap in the matching device frame
4. Fine-tune copy style and colors
5. Check every item before exporting

A smart workflow doesn't do the work three times; it does it once and exports to three platforms.