Build your first release workspace.

Fast path

Quick start

You can understand the full product with one small project. Store credentials are optional until you want to sync or publish.

1. Create a project. Add a name, iOS bundle ID, Android package name if needed, and choose a local folder.
2. Choose locales and shots. Keep en-US, add one second locale, and name 3–5 screens that tell your app's story.
3. Add raw screenshots. Use Auto Capture with an installed simulator/emulator build, or use Manual Import with images you already have.
4. Write and design. Add headline/subtitle copy, choose a background and device frame, then tune one screenshot in Preview.
5. Render locally. Select output sizes, run Render, inspect Diagnostics, and reveal the generated folder.
6. Validate publishing. Configure either store connector, enable Dry Run, choose the content scope, and run preflight.

Mental model

Core concepts

• Workspace: one local .beralo folder containing the complete release project.
• Locale: your source language or a localized market such as en-US, ja, or fr-FR.
• Shot: a product screen with its own key, display name, deep link, delay, and localized overlay copy.
• Capture set: a selected simulator/emulator plus the target store size and orientation.
• Preset: the final pixel dimensions for an iPhone, iPad, Android phone/tablet, Chromebook, or feature graphic output.
• Tuning scope: where a visual change applies—globally, by locale, by shot, by preset, or a combination.
• Source locale: the locale used as the base for bulk metadata and store locale mapping.
• Publish plan: the resolved stores, content types, locales, preset buckets, and actions for one run.

Module 1

Foundation

Foundation defines the identity and shape shared by every later stage.

Basics

Confirm the project name, Apple bundle ID, and optional Android package name. The connector badge shows whether Apple, Google, both, or neither store is ready.

Locales

Add languages from the supported catalog, enable only the markets you are preparing, and use Auto map to resolve project locale codes to App Store and Google Play locale identifiers.

Shots

Give each shot a stable key and human-readable name. Add iOS and Android deep links when Auto Capture should open a specific screen; increase the per-shot wait when data or animation needs time to settle. Feature Graphic is a separate 1024×500 shot type for Google Play.

Module 2

Capture & import

Auto Capture

Create one capture set for each device size you need. Beralo uses the app already installed on the selected simulator or emulator, applies the locale strategy, opens each shot's deep link, waits, and saves the raw image.

• App launch strategy: passes language arguments at launch and is usually fastest.
• System override: changes the simulator/device language when the app depends on system locale state.
• Clear app data: use when cached onboarding, language, or demo state leaks between locales.
• Status bar override: creates consistent iOS store screenshots when supported.
• Orientation: follow the preset, or force portrait/landscape per capture set.

Manual Import

Import one screenshot into a selected locale/shot, select multiple images in shot order, or import a locale folder. Common filename formats such as home.png, 01_home.png, and 1.png are matched to shots. Existing files can be skipped or replaced.

Module 3

Creative

Text

Write a headline and subtitle for every locale and shot. Edit one cell, paste structured copy in bulk, copy a translation prompt, or fill empty targets from a source locale without overwriting completed work.

Preview and tuning

Preview the final composition at any locale, shot, and preset. Drag the screenshot, title, subtitle, and widget directly; resize or rotate text boxes; and use Tuning for precise values.

• Solid, gradient, image, or split-image backgrounds
• Built-in None, Simple, and Clay frames plus downloaded device frames
• Screenshot position, fit, radius, scale, rotation, and 3D tilt
• Font, weight, color, alignment, wrapping, stroke, underline, and visibility
• Decorative widget image with fit, size, position, opacity, and scope
• Change history and reset controls for safe experimentation

Choose scope before tuning. A change can affect all locales and shots, the current locale, one selected shot, or only the current locale-shot pair. Preset-specific overrides let phone and tablet layouts diverge without duplicating the project.

Render

Select one or more enabled presets and render the complete locale-shot matrix. You can pause, continue, or restart long runs. Diagnostics reports missing raw images and text overflow before export. Free output includes a small watermark; Pro output does not.

Module 4

Store

Listing metadata

Beralo keeps Apple and Google fields separate while presenting them in one locale workspace.

• App Store: app name, subtitle, support URL, marketing URL, full description, keywords, release notes, and promotional text.
• Google Play: title, short description, full description, and release notes.

Character counters reflect the target store's limits. Work in a single-locale form or use Bulk Update across locales. Store Sync pulls selected live fields; you choose whether to fill empty fields or overwrite local content.

Monetization metadata

Sync Apple subscriptions, Google Play subscriptions, and Google one-time products, then localize the customer-facing copy. Apple supports display name and description. Google subscriptions support title, description, and up to four localized benefits.

Module 5 · Pro for live delivery

Publish

Publish is deliberately explicit. Select Apple and/or Google, choose screenshots, listing metadata, and monetization metadata independently, then inspect the resolved plan.

1. Choose the scope. Stores, content types, screenshot preset sets, replace/append mode, and optional version override.
2. Run preflight. Resolve missing credentials, render output, locale mappings, field limits, and Google bucket conflicts.
3. Use Dry Run. Validate and simulate the current plan without changing a live listing.
4. Review store changes. When available, compare local listing fields with the live store before continuing.
5. Publish. Track Apple and Google screenshot batches and copy all logs when a store API needs investigation.

Google Play phone, 7-inch tablet, and 10-inch tablet buckets can use one selected preset or a mixed set. Chromebook screenshots are rendered locally but must currently be uploaded manually in Play Console. Google screenshot batches keep a checkpoint so an interrupted run can resume without repeating committed batches.

Credentials

Store connectors

App Store Connect

Create an App Store Connect API key under Users and Access → Integrations. Enter the Issuer ID and Key ID, then import the one-time .p8 private key. Beralo stores the secret in Keychain.

Google Play

Enable the Google Play Android Developer API in Google Cloud, create a service account and JSON key, then invite that service-account email in Play Console with the listing permissions required for your app. Import the JSON into Beralo; the credential is stored in Keychain.

Local-first storage

Project files

A workspace is portable because its non-secret state lives together. The exact subfolders grow as features are used:

MyApp.beralo/
  project.json
  raw/                 # original captures and imports
  renders/             # final PNGs by preset and locale
  exports/             # dated folders and zip archives
  logs/                # capture, render, and publish diagnostics
  store-snapshots/     # local store state used for review/history

Back up or version the folder like any other project asset. Store secrets are not included because they remain in Keychain.

Common fixes

Troubleshooting

The wrong language appears after locale changes

Switch to System override if launch arguments are insufficient, enable Clear app data before each locale, and confirm the app does not restore a saved language preference.

A screenshot is black, incomplete, or still animating

Increase that shot's delay, confirm the deep link opens the intended state, and verify demo data is present before capture.

Text is clipped after translation

Open Render → Diagnostics, then adjust wrapping, box dimensions, font size, or a locale-specific tuning scope. Do not shrink every locale to fix one long translation.

A store locale is blocked

Open Foundation → Locales, review Apple and Google mappings, use Auto map, and manually resolve regional variants that do not have an exact match.

Google publish stops after some screenshot buckets

Keep the saved checkpoint and rerun the same scope to resume. Clear the checkpoint only when the preset selection, files, or intended bucket routing has changed.

Optional account

Account & Pro

You do not need an account for the editor, capture/import, localization, render workflow, dry-run validation, or local watermarked export. Sign in with Google only to activate and sync Pro across your Macs.

Pro unlocks live store publishing, pre-publish diff, history, rollback, and watermark-free exports. Annual and lifetime purchase options are described on the pricing page →.