About Screenshots.live
Screenshots.live automates the busywork between mobile code and the App Store. Built by a developer who got tired of manually re-exporting the same screenshots for 13 locales every release.
Who builds this?
Eric Isensee — Founder
Engineer based in Germany. Building Screenshots.live since 2024 with a focus on the API surface developers actually want — YAML configs, deterministic renders, and CI/CD-friendly defaults. Previously shipped mobile and backend systems across e-commerce, fintech, and developer tooling.
Why does Screenshots.live exist?
App store screenshots are the highest-leverage marketing asset in mobile — they decide whether a user installs your app. They're also the most labor-intensive: every release means re-exporting the same compositions for iPhone 6.5", iPhone 6.7", iPad 12.9", iPad 11", Android phone, Android 7" tablet, and Android 10" tablet. Multiply by every locale you ship in. That's 50+ images per release for a single-locale app, 600+ for a 12-locale app.
Manual exports break under that load. Designers context-switch. Locales fall out of sync. Releases slip. Screenshots.live solves this by treating screenshots as code: design once in a visual editor, render programmatically via an API or a Fastlane plugin, ship every variant in one CI run.
Who is it for?
- Mobile developers and tech leads who want screenshot generation to live in CI/CD instead of a designer's backlog.
- ASO specialists running A/B tests and need variant generation that doesn't require Sketch+Photoshop acrobatics.
- Indie developers and small teams shipping in multiple locales without a dedicated design team.
- Marketing teams at SaaS companies who need to keep store assets in sync with product copy changes.
How do we build this?
Three principles drive the product:
- API-first. Every visual editor capability is also exposed as REST. Templates, items, renders, fonts — all addressable by API key. If a workflow can be done in the editor, it can be done in CI/CD.
- Deterministic renders. The same template + variables produces the same pixels every time. No flaky LLM outputs in the render path. Critical for diff-based screenshot tests and reviewable CI artifacts.
- Locale fan-out by default. Multi-locale rendering isn't a feature flag — it's how the product works. One template, every supported locale, in one API call.
Where can I learn more?
- Read the Build with AI guide for autonomous agent workflows.
- Check the blog for ASO playbooks and automation case studies.
- Browse the 2026 screenshot size reference.