Archive / Your AI-built app works. Now make the store screenshots

Your AI-built app works. Now make the store screenshots

Building the app is getting easier than getting it ready to publish. What Apple and Google ask for, four tools that make the screenshots, and what to check before you build your own.

For: Solo founders, Small business owners, New to AI

Topics: Websites, Marketing, Business development

Why I'm sharing it

A builder posted that making an app with Claude had become easier than preparing everything to publish it. The part that slowed them down was the App Store and Google Play screenshots. I've seen the same thing. The app runs, and then you find out each store wants its own sizes, counts and rules before you can submit.

So here is what the stores ask for, the tools I found that make the screenshots for you, and what a reply to that post taught me about building tools at all.

1. Check what each store asks for

Apple wants at least one screenshot for the iPhone size it lists as required, which on November 19, 2026 was the Dynamic Island display (for example 1179 x 2556 or 1206 x 2622 pixels, portrait). You can add up to 10 per device size, as JPG or PNG, with no transparency. If your app runs on iPad, you also need a 13-inch iPad set. Apple scales the smaller sizes from the larger ones, so you don't have to make every size.

Google Play wants 2 to 8 phone screenshots, PNG or JPEG, up to 8 MB each, with each side between 320 and 3,840 pixels, in 9:16 or 16:9. Its guidance asks you to show the real app, keep any tagline to 20% of the image or less, and leave out words like "Best", "#1" and "Download now". It also lists device images among the things to avoid, so check the frames before you upload a Play set. You'll need a 1024 x 500 feature graphic too.

Store rules change, so check Apple's screenshot specifications and Google's preview assets page on the day you submit.

Prompt

My app: [what it does, in two sentences]. Who it's for: [the person]. The screens I have: [list them]. 1. Pick the 5 screens that show what the app does best, in the order a new user should see them. 2. Write one headline for each, [6] words or fewer, in plain words. No "best", "#1", "free" or "download now", and nothing the app doesn't actually do. 3. For each screen, tell me what should be on it when I take the screenshot (sample data, which tab is open) so it looks real and contains no personal information. 4. List what Apple and Google currently require for screenshots, and say which rules you aren't sure about so I can check them on the stores' own pages.

2. Pick a tool to make them

Shipframe

A browser editor at getshipframe.com. You drop in your screenshots, each one lands in a phone frame, you pick a theme, edit the headlines, colors and fonts, and export. Its site says everything renders on your device and you don't need to sign up to start. The free version exports one size with a "Made with Shipframe" mark. Pro was $19 one time when I checked on November 19, 2026, and exports every App Store and Google Play size in one ZIP. This is the tool from the post that started this one.

Open Screenshot Generator

An open source editor (MIT license) on GitHub at dotnetdreamer/open-screenshot-generator. Its README calls it an open source Canva for store screenshots. It has templates, device mockups and text, and exports PNG images and MP4 preview videos. It runs in your browser with no account, and there is also a desktop app that can upload to App Store Connect and Google Play using your own developer credentials. One catch from the README: projects are saved in your browser, so clearing your site data deletes them. Export as you go.

fastlane

Free and open source, for when you'd rather script it than click. On iOS, snapshot runs your UI tests to capture screenshots on every device and in every language, frameit adds device frames and titles, and deliver uploads the result. It takes more setup than the two editors, and it pays off once you update screenshots with every release.

Prompt

Set up fastlane screenshots for this iOS project, one step at a time, and show me each change before you make it. 1. Check whether fastlane is installed and tell me how to install it if not. 2. Run fastlane snapshot init and explain the files it creates. 3. Write a UI test that opens these screens with sample data: [list]. Use no real names, emails or account details. 4. Set the devices to the sizes Apple currently requires, and the languages to [list]. 5. Run fastlane snapshot, then show me where the screenshots landed. Don't upload anything to App Store Connect. I'll do that myself.

app-media-creator

An open source project on GitHub called app-media-creator (MIT license). It aims to turn a logo, screenshots and a video into every App Store, Google Play and web asset in six languages, with optional Claude Code skills that write the headlines and store text. Its README says it is in early development, before version 0.1.0, with nothing published yet. Worth watching, not something to depend on today.

3. What a reply taught me

Under the Shipframe post, a developer replied that they had just built something similar for themselves and could have saved tokens if they'd seen the post earlier. Their project is app-media-creator. Three lessons from that reply and from the project itself.

Search before you build

Claude makes building a tool so easy that it can feel quicker than looking for one. It usually isn't. A few minutes of searching can save a day of building and the tokens that go with it. Make the search the first step of the plan, not an afterthought.

Prompt

Before we build anything, search for existing tools that already do this: [the job, in one sentence]. List up to 5. For each: the link, what it costs, the license if it's open source, whether it looks maintained (latest release or commit date), and what it doesn't do that I need. Then tell me plainly: use one of these, extend one of these, or build my own, and why. Don't write any code until I pick.

Claude can carry a build a long way when the work is laid out

The developer said Claude had been building their app on its own for about four hours when they replied. Whatever you think of that, look at how the repo is set up. Every requirement is a GitHub issue with size and priority labels. The work is split into milestones, from project setup to a first release. Changes are planned before they're built, and there are written rules for people and AI agents who contribute. That structure is what lets an agent pick up the next task without asking you. If you want Claude to work longer on its own, give it that kind of list first.

Borrow someone else's roadmap

The developer suggested looking at their issues and milestones for ideas. That works for any open source project close to what you're making. Its issue list is a free record of what people building this kind of thing ran into.

Prompt

Read the open issues and milestones of this GitHub project: [link]. My app or tool does: [one sentence]. List the features and problems there that would matter for mine, grouped as: I already have it, worth adding, skip. Keep each to one line and link the issue it came from. Don't copy their code.

4. Automate it once you ship updates often

The same reply laid out a three-step pipeline: capture screenshots of the app automatically, turn them into store images, then upload them with a script. You don't need it for your first release. Once you're updating screenshots every few weeks, fastlane's snapshot and deliver can handle the first and last steps, and an editor or a script handles the design in the middle.

Based on a post by the maker of Shipframe and a reply to it by the maker of app-media-creator. Open Screenshot Generator is by dotnetdreamer. The store rules, tool details and prices here come from Apple's and Google's help pages, fastlane's docs and each tool's own site or README, checked on November 19, 2026. If one of these is yours and you'd like credit by name, write to lenabosch@pm.me.

Use it for: Getting an app you built with AI ready to submit to the App Store or Google Play, starting with the screenshots.

Back to the archive