LilacpaneReview three different language layers
When turning a Chinese screenshot set into an English one, a common problem is an English headline above a Chinese interface. Another is a correct file uploaded to the wrong locale. Separate three things before editing: the language shown by the app, the headline added to the image, and the localization selected in App Store Connect.
Apple distinguishes store-metadata localization from language support inside the app. Some content, including screenshots, initially defaults to the primary language when a localization is added. Review it explicitly. See Apple's app-information localization guide.
This workflow uses Chinese and English as an example. The planning table and sample copy are editorial suggestions to help organize production; they are not a forecast of download growth.
Write a content matrix before editing the canvas
Give each screen a stable identifier based on the feature it explains. Record the meaning first, then each language's copy and the corresponding source screenshot. When the interface changes, the matrix shows which visuals need attention without relying on modification dates.
| Screen | Purpose | Chinese example | English example |
|---|---|---|---|
| 01 / organize | Show tasks grouped by project | 让每个项目井井有条 | Keep each project organized |
| 02 / focus | Show today's work | 专注今天要做的事 | Focus on today's tasks |
| 03 / review | Review completed work | 回顾已经完成的工作 | See what you've completed |
These examples assume a fictional task app. Write your own copy around features that actually exist. A translation should not turn “organize” into “automatically complete” or introduce a promise unsupported by the captured interface.
Add columns for source filename, locale, reviewer, and status. Concrete states such as “capture needed,” “layout needed,” “review needed,” and “ready to upload” tell you what remains more clearly than an approximate completion percentage.
Prepare the real interface in the target language
If the app supports the target language, switch it and capture the same scenario again. Review dates, numbers, currencies, units, and example content. An English navigation bar above a list of unrelated Chinese project names can make the set look unfinished.
Keep the example story consistent. A project shown in the first screenshot should remain the same project when opened in the second. Use fictional data with natural wording in each language. Also remove private notifications and account details; the public screenshot preparation checklist covers that stage.
If the app does not support the target language, be clear about the real product scope. Do not edit the screenshot to imply that an unavailable interface translation has shipped. Store copy can be localized while still describing the actual product accurately.
Reuse the visual style and review each language's layout
Import the prepared captures into Lilacpane and keep the device appearance, background, and main text style consistent. Then review line breaks for each language. Start with two test images: the shortest headline and the longest or most difficult one. If both work, continue with the rest.
Avoid shrinking all English text just to fit the space originally occupied by Chinese. Remove repeated meaning, choose a natural short phrase, and adjust the text position and surrounding space. The image should explain the main value of that screen, not reproduce an entire manual.
Languages such as Arabic and Hebrew also require direction and alignment checks. Apple's right-to-left design guidance covers those considerations. Capture and review the actual localized interface instead of horizontally flipping a finished screenshot.
Use Lilacpane for device framing, backgrounds, and text layout. Prepare and review translations separately. Available editing and export options depend on the current app version.
Organize exports by locale and device
Put the locale in the folder structure and the feature identifier in the filename. For example: appstore/en-US/iphone/01-organize.png and appstore/zh-Hans/iphone/01-organize.png. These are file-management examples; naming a folder does not configure the store locale.
When uploading, check platform, app version, language, and device category again. Apple's upload guide explains how to add assets for other localizations and sizes through Media Manager.
- The captured interface uses the intended language.
- Headlines describe the shipped feature accurately.
- Longer copy fits without becoming too small.
- Demo dates, units, and content have been reviewed.
- Screen identifiers, folders, store locale, and device wells match.
- The uploaded order agrees with the content matrix.
Common questions
Can the English version reuse the Chinese screenshots?
Backgrounds and device styling may be reusable. Review every language-dependent element, including the interface and demo content, before deciding that a file can be shared.
How many languages should I start with?
Start with languages you can support, proofread, and maintain. Finish and review one complete set before expanding an unfinished collection.
Does this workflow require automatic translation in Lilacpane?
No. Prepare reviewed translations and source captures first, then use Lilacpane for framing and composition.
Official references
