Choose a source deck worth adapting
Start with a clear product story: one audience problem, one useful idea and one app action. Finish the opening and demonstration before expanding into more languages. A confused source produces a queue of confused versions.
Create the deck in YASF and review it as a complete post. Keep the product brief as the source of truth for what the app does. Use real screenshots wherever the interface delivers the promise.
Add language versions inside the same deck
Use YASF to add the languages you need. The versions reuse the visuals and do not consume extra translation credits. Keep each one attached to the source story so the campaign stays organised.
Review the text in each language before exporting. Check the hook, examples, line breaks, app name and close. Replace a screenshot when the audience needs to see a different interface language.
Give every export an angle and a language
Use a naming system you can understand when the download folder fills up. Keep the images, caption and destination for one version together. Your publishing queue should make the next action obvious.
A simple table is enough to run the first campaign. Record a new row for each angle-language pair.
| Source story | Language | Files | Review | Next action |
|---|---|---|---|---|
| Study recall | English | study_recall_en | Copy and screenshot checked | Publish |
| Study recall | Spanish | study_recall_es | Local wording checked | Publish |
| Small habit | English | small_habit_en | Copy checked | Prepare screenshot |
| Small habit | Spanish | small_habit_es | Adaptation in progress | Review wording |
Let local questions shape the next source story
Keep the results from each audience beside the version. Notice which questions repeat and which examples need more explanation. Use those observations to choose the next deck, not just to translate the old one again.
As the campaign grows, keep the routine intact: source story, language versions, local review, organised export and publishing. YASF gives you the production line. You choose where the next story goes.
YASF — a campaign from the YASF homepage
YASF
VintHelper
Questions & answers
Do translations need a separate image-generation run?
YASF language versions reuse the existing deck visuals. Focus the work on the text and the product details for the audience.
How many languages should I organise at first?
Choose the markets your product is ready to serve. Start with a queue you can review and publish, then add languages using the same source-version-export routine.









