3-minute product tour
One visible path from idea to store listing.
Beralo is modular, but it is easiest to understand as one release pipeline. Each stage produces exactly what the next stage needs.
- 01Define
Create one local workspace with app identity, locales, shots, and store connectors.
- 02Capture
Run installed simulator/emulator builds by deep link, or import screenshots you already have.
- 03Compose
Write localized screenshot copy, design the frame, and render every market and device size.
- 04Prepare
Edit Apple and Google listing fields, subscriptions, and in-app product copy with live limits.
- 05Publish
Resolve the release plan, run preflight and Dry Run, then deliver the selected scope.
Start small
A project is just a folder you control.
Create a workspace with one locale and a few shots. Beralo keeps captures, copy, renders, diagnostics, and release state together, while store credentials remain in Keychain.
- No account is required to begin
- Add iOS, Android, or both
- Expand locales and device sizes when the release needs them
Create once, adapt deliberately
Separate raw product screens from store design.
Capture or import the clean app UI once. Localized copy, backgrounds, frames, and layout live in the creative layer, so a marketing change does not force another device run.
- Bulk localized headline and subtitle editing
- Per-locale and per-shot overrides
- Phone, tablet, and feature graphic outputs
Move only what you intend
Turn publishing into an inspectable plan.
Choose the channel and content scope, run preflight, resolve locale targets, and validate with Dry Run. Live publishing is a separate, explicit action.
- Apple and Google can run together or separately
- Screenshots, listing copy, and monetization copy have independent switches
- Logs and resumable screenshot batches help with store API failures
Continue when you are ready
Build the first workspace for free.
Use the complete creative workflow locally, then decide whether live publishing is worth Pro.