---
title: "How I Automated my App Store Assets Workflow"
slug: how-i-automated-my-app-store-assets-workflow
url: https://listedarticles.com/articles/how-i-automated-my-app-store-assets-workflow
canonical_url: https://www.natashatherobot.com/p/automated-app-store-assets
content_type: blog_post
language: en
published_at: 2026-10-28T12:56:25.000Z
updated_at: 2026-10-29T14:13:59.734Z
author: "NatashaTheRobot"
author_url: https://www.natashatherobot.com/
authored_by: human
publisher: "NatashaTheRobot"
publisher_url: https://www.natashatherobot.com/
topics: ["iOS Development", "AI", "Indie Development"]
license: all-rights-reserved
word_count: 1864
reading_minutes: 8
citation: "NatashaTheRobot, NatashaTheRobot. \"How I Automated my App Store Assets Workflow.\" 28 Oct 2026. https://www.natashatherobot.com/p/automated-app-store-assets (all-rights-reserved)"
# The full text follows. The web page shows an extract and sends readers
# to the source above; quote the citation and link the canonical URL.
---

# How I Automated my App Store Assets Workflow

> Solo iOS developer NatashaTheRobot describes how she finally solved the long-standing stress of producing App Store screenshots and marketing assets for her own apps: after years of Keynote, Sketch and screenshot tools, she built an automated, AI-assisted asset flow that lets her act as the 'storyteller' rather than the designer, and argues designers now need to deliver many more variants for product pages, A/B tests and localizations.

*NatashaTheRobot · October 28, 2026*

When I work with companies, I get to focus on problem solving with code, which I enjoy, while they have a designer or a team of designers on staff who focus on thing like app store assets and marketing. It’s great! But as a solo developer working on my own apps, I don’t have the budget to hire a great designer. They are very very expensive! And come with the overhead of finding one, having them dedicate the time to you, taking a long time, the back-and-forth, etc. So to this day, I’ve been the “designer” for my own apps and I’m not a fan.

I like coding and thinking through building apps, but I always get bottlenecked at the App Store Release step. Over the years, I’ve tried my best, but always failed. I defaulted to just showing only the simulator screenshots. At one point, I used Keynote to design screens, since it already has good colors and fonts. I used Sketch. But this all boils down to one problem - I’m not the person who can pick the right colors and fonts and backgrounds. I also tried apps that make app screenshots “easy” but these are either too complicated, designed for designers, or too limited, with only a few presets. I avoid updating app assets like a plague, keeping the old ones around, even when my app release has significant changes.

Well, when Apple announced the addition of having to make iPhone Duo assets AND headers, that got me very very very stressed and panicked. I easily optimized my app for iPhone Duo in code, but the assets were the bottle neck I just didn’t want to face. So I went ahead and released my app with code only without submitting the new Duo assets to make it ready for the Day 1 Duo release date. In the meantime, I decided to use AI to automate this whole process and never have this level of stress again.

*P.S. I was also extremely impressed by [@mufasaYC](https://x.com/mufasaYC)’s blog post outlining his process for creating 18 SETS of localized App Store Assets FOR EVERY DEVICE. This is the level of ambition we should all strive for in the age of AI. [Read it here](https://thetasks.app/blog/how-we-made-our-app-store-screenshots/).*

## Attempt 1: Make an App!

A few weeks ago, I made myself an Mac app called [BezelStudio](https://tools.natashatherobot.com/bezel-studio-apple-device-mockups) for quickly adding bezels and backgrounds for any dropped-in simulator screenshots. I use it for posting about my apps in blog posts, X, etc. I use it all the time and absolutely love it!

So my first idea for helping me with my app store assets problem was building a similar app. Claude now gives Max users $200 in API credits per month, so I decided I can make an app that uses the credits to help make the whole process easier. Since it’s my personal app, I can just use the API key directly and don’t have to worry about spending and all that.

I thought of all the ways I used to make screenshots and what I did and didn’t like about them and came up with a few super super cool ideas and features that I went down the rabbit hole of building out with Claude for the past two weeks! Here are some super cool ideas I had:

- Use [Xcode’s new MCP SwiftUI Previews](https://www.natashatherobot.com/p/faster-swiftui-development-in-claude) command to take preview screenshots of all the screens on all devices that included the word “PRODUCTION” in it’s Previews title. No running simulators and manual screenshots! The app also included a prompt for the agent to add the production previews needed if they didn’t exist!
- I already built the whole bezel system multiple times, including in my [BezelStudio app](https://tools.natashatherobot.com/bezel-studio-apple-device-mockups) and my [SwiftUI Previews mod](https://tools.natashatherobot.com/#swiftui-preview), so this app had the same functionality. It would auto-add device bezels that match the screenshot, and I could change the bezel colors. I even had my own “stock bezels” made in case I wanted to rotate the device (Apple’s official bezels do not allow for rotation and modification). Once I selected the bezel design for one screen, it applied it across the same device screenshots.
- Since the Claude API doesn’t generate images, I had the app identify app colors from the screenshots and generate a prompt for Opus 5.5 to generate three variations of metal shader code as a background. Each metal shader was generated, then converted into PNG images for a unified pattern background across screens. This solved my biggest problem of not being able to design nice backgrounds for my app asset screens.
- I had Claude’s API analyze all my screenshots across devices and “link” similar ones. For example, the Search screen on iPhone is matched to the Search screen on Mac and iPad, even though they all look slightly different. That way, when I added header text to the iPhone app asset, the same screen on iPad / iPhone Duo / Mac also got the same header! That removed the “grunt work” of having to copy / paste the same text over and over again across devices.
- It would select good colors for me for text and background. This is super cool as well, since that is definitely my design weakness.

So this was all super cool and I enjoyed thinking through the product I wanted and working with Claude to build it. Then I started using it…

## Throwing it all away!

Well, the whole product was a complete dud…

First, it didn’t make sense to make the SwiftUI previews because you need to seed the right information, the right settings, and scroll to the right parts to tell your app story. Anyway, the simulator is definitely required. Obviously! Cool idea in theory, stupid in practice!

So I got Claude to first go through my app, run it on all the simulators and take screenshots of all the screens. Then I realized that none of this makes it better!!

The problem is that making app store assets is extremely custom per screen! The hard part is actually figuring out the story, figuring out how to tell it, customizing each exact app point. Some app store screens should not be just a screenshot! There was too much customization that was needed, and this product just didn’t make sense. I threw a lot of tokens-worth of work all away!!

But this is the cool thing about building with AI now. In the past, I wouldn’t have even been able to make this product at all. Or if I did, it would have taken ALL my time and focus and many months of work to get it “just right” before realizing that it was actually a stupid idea. And I might have stuck with it regardless trying to “fix it” because of the investment I made. And if I didn’t make this app, I would have always had this idea stuck in my head as another great idea I can’t follow through with.

So despite the significant work and spend, I’m so happy to have gotten it out of my head, felt the idea, and learned the bigger picture. That app store design is custom and cannot be made into a simple app. It is complicated and I need a more complicated solution!

## The Solution: Partial Automation

I saw on X that people were using Claude to make small videos. So instead of diving into screenshots, I worked with Claude to make a 30-second preview of my app. WOWWWWWW!!!! What an experience!

For one, I once made an app preview for one of my apps and the problem is showing your app functionality in 30 seconds. This required some serious work and editing which I don’t enjoy. Well, Claude can step through your app just based on the scenes you describe IN WORDS and make the preview for you with the right timing!!! Game changing!!

I had it then go ahead and make the max THREE previews across ALL the devices. This would have taken me FOREVER, and since I don’t enjoy this, I wouldn’t have bothered to invest the time.

So where is the automation part? A lot of the running of the simulator through the preview “journey” is seeded with code and automation. That part can be kept as code for future runs. Now when my app has a small UI change, Claude can re-run the same journey on each simulator and recapture the full movie with no prompting from me! I also had it write an AGENTS.md file in the folder where the previews are saved that includes app-specific details for generating the previews, such as the fonts and colors used.

But I want this applied to my next app as well! So I had Claude analyze the whole session, what it learned, all the settings and libraries it used, including all the app store sizing requirements, and create a generic “app-previews” skill for the next session agent to use. No wasting tokens running into the same technical issues in another app!

I then did the same thing for the static assets. I worked with Claude to build each asset by first making one for the iPhone, seeing how it looked, then, once approved, have it build the same version for iPad / iPhone Duo / Mac. WOWWWWW!!!! And once I was done, I again had it write the app-specific asset design information in an AGENTS.md and create a general skill focused on the process of generating assets, including sizing information from Apple. It also did the headers!!! Very very well!

However, the main thing that happened is that I was no longer stressed doing the “grunt work” like figuring out what colors look decent. I was able to focus entirely on my app’s value proposition and how to best show it to the users through these assets. And honestly, this is the first time I was able to do this, and it feels GOOD!!!!

When we ask “who am I” now that AI can do my job, THIS IS IT!!! I could never get to the higher level thinking of telling a story, which I’m actually very good at, especially for MY OWN APP that I’m super passionate about! because I was stuck in the stress of grunt work that I’m NOT good at!! I was not reaching anywhere close to my full potential before AI.

## Are Designers “Finished”?

I think it’s funny when people say that any career is finished because of AI. AI just does the annoying grunt work for you! You just have to elevate and take things to the next level that just wasn’t possible before. As I described above, I wasn’t able to get to the “storyteller” level even though that was within me. Now I can! And this is just the start. I’ll grow this skill that I didn’t get to build before because it wasn’t possible.

So are designers finished? No. But they have to super elevate, [like @mufasaYC did](https://thetasks.app/blog/how-we-made-our-app-store-screenshots/). Before, if 3 different assets were acceptable as the initial options, now the designer must deliver 20 or even 100! They need to diversify against product pages, A/B tests, localizations! There is no more excuse!

---

*Originally published at [NatashaTheRobot](https://www.natashatherobot.com/p/automated-app-store-assets).*
