doppelt.digital Application Platform Documentation
English Deutsch

Store metadata: title, description & screenshots

What the stores need, where it lives in the repository, and how screenshots are generated automatically.

On this page

All store content of your app lives version-controlled in the app repository – the pipeline uploads it automatically when publishing.

Texts: the fastlane/metadata structure

There is one folder of text files per language (de-DE, en-US, …):

iOS – ios/fastlane/metadata/<language>/:

File Content
name.txt App name in the store
subtitle.txt Subtitle
description.txt Description
keywords.txt Search keywords
release_notes.txt What’s new
support_url.txt, marketing_url.txt, privacy_url.txt Links

Android – android/fastlane/metadata/<language>/:

File Content
title.txt App name in the store
short_description.txt Short description
full_description.txt Description

In addition, the respective repository area contains: app_icon.png (icon), google_data_safety.csv (Android data safety), plus app_privacy.json and app_rating_config.json (iOS privacy and age rating).

Screenshots: generated automatically

You don’t have to create store screenshots by hand – the pipeline generates them from your app’s UI tests:

  1. Define which screens are captured (test/goldens/Framefile.json) and which marketing texts appear above them (test/goldens/<language>/title.strings).
  2. Commit an empty file named .doppelt-digital-create-new-screenshots to the repository root and push to main.
  3. The pipeline renders the screens in all project languages, places them in device frames (Frameit), and stores them in the metadata folders.
  4. On the next publish, the new screenshots are uploaded to the stores; the pipeline cleans up the marker file itself.
Tip
Screenshot generation uses your app’s screenshot test mode (SCREENSHOT_TEST_MODE), which shows e.g. demo data – so the images always look tidy.

See also