Most indie iOS developers have a screenshot problem they stopped talking about.

Not because it’s solved. Because it’s too slow and painful to keep complaining about.

You set up Fastlane frameit at some point. You got it working, mostly. Then iOS updated and device bezels changed. Then you added a new language. Then you realized you had 35 screenshots to regenerate and kept deferring it.

That’s not a tooling complaint. That’s a workflow that doesn’t scale.

Marteso is built to be the Vercel for iOS apps: a platform where pushing to GitHub triggers your deployment pipeline automatically. For App Store submissions, that pipeline starts with screenshots.

The problem with the current Fastlane approach

Fastlane frameit is a capable tool. It’s also manual, brittle, and not designed for developers managing multiple languages, multiple devices, and multiple app versions simultaneously.

Here’s what the typical Fastlane screenshot workflow looks like in practice:

  • Write UI tests
  • Configure snapshot lane in Fastfile
  • Run fastlane snapshot locally (20–40 minutes per run)
  • Frame screenshots with fastlane frameit
  • Manually verify localized output for each language
  • Handle broken frames when device images update
  • Repeat every release

If you support 5 languages and 3 device sizes, that’s potentially 60+ screenshot files to verify. By hand. Every time.

50% faster and fully automated

Marteso’s screenshot pipeline is 50% faster than Fastlane frameit. More importantly, it removes the manual steps entirely.

The workflow: write one UI test, connect your GitHub repo, push. Marteso picks up the webhook, runs your test, and generates device-framed, localized screenshots for every App Store language you support.

You don’t run anything locally. You don’t manage device frames. You don’t loop through language configurations.

The screenshots live in your release pipeline, ready for App Store Connect the next time you submit.

Why localization is the key

Most apps ship English screenshots to every storefront. That’s the path of least resistance, and it costs you.

App Store users in Germany, Japan, Brazil, and France convert better when screenshots reflect their language. That’s the basic behavior of any user who discovers apps through their native-language storefront.

The reason indie developers don’t localize screenshots is that it multiplies the work. One device frame × 6 languages × 3 device sizes = a project you keep deferring.

Marteso collapses that multiplier. The same UI test run that generates your English screenshots generates your localized ones. If your app strings are already translated, you’re done.

How it connects to the rest of your release pipeline

Marteso is not a standalone screenshot tool. It’s the submission layer for App Store releases.

The screenshot pipeline sits alongside binary signing, version management, metadata editing, localization management, and keyword tracking in a single platform. The same GitHub webhook that triggers your screenshots can also trigger your binary build.

For an indie developer, that means going from a GitHub push to a release candidate with correct, localized screenshots in every language, without touching Xcode’s Organizer or running Fastlane locally.

Explore the screenshot pipeline in the Marteso demo at app.marteso.com ([email protected] / demo1234). The demo apps walk through a full release workflow including metadata, screenshots, and App Store Connect submission.