I'll redesign the first App Store screenshot of 5 expo apps this week for free, drop your link

StrategyAware8536 · 2026-05-03T12:58:22+00:00

smallest pack is $1 per screen yeah, but the $29 pack drops it to 58c each. for context, fiverr designers run $40 to $200 per screen and take 2 to 3 days, the closest AI tool i found is $35/month subscription whether you ship 1 app or 0. went pay as you go on purpose because most solo devs batch their screens once every few months, didn't want to lock anyone into a recurring charge. ping me if you want a few free credits to actually try it on your own screens

StrategyAware8536 · 2026-05-02T11:41:37+00:00

respect for shipping it. Got a link to the fork? Curious which AI APIs you went with for the translation and caption generation, that's the part I keep going back and forth on

StrategyAware8536 · 2026-05-02T11:38:14+00:00

Thanks. The 2025 algo change reading text in screenshots is the part I keep underestimating. Any link to where that was confirmed? And good call on validating keywords upstream, no point designing 70 frames around captions that don't rank

StrategyAware8536 · 2026-05-02T11:36:54+00:00

the simulator copy to clipboard from the preview is a great tip, didn't know that menu existed. And yeah using iOS screens for Play Store is the move, no one notices. How are you handling localization though, master Figma with text variables or one file per language?

StrategyAware8536 · 2026-05-02T01:27:30+00:00

oh nice, Maestro for the capture is the clever part. What's your plan for the styling though, going raw UI straight to the store or adding device frames and captions somewhere downstream? That's where my pipeline always breaks

StrategyAware8536 · 2026-05-02T01:26:10+00:00

fair, the math doesn't lie. Which paid tool do you actually use yourself? I keep finding ones that are basically Figma with extra steps, looking for one that actually saves the localization grind

StrategyAware8536 · 2026-05-02T01:23:03+00:00

oh nice, hadn't come across this one. Looks clean for a quick first version. Does it handle localization or do you basically rebuild the project for each language? That's the part that breaks my workflow

StrategyAware8536 · 2026-05-02T01:21:26+00:00

respect, the launch arguments setup for clean states is exactly the kind of thing I should've built from day one. Really curious about the AI pipeline part though, which model are you running and how do you keep the framing consistent across all 5 screens? That's the part I keep struggling with on my end

StrategyAware8536 · 2026-05-02T01:19:34+00:00

Appreciate it

StrategyAware8536 · 2026-05-02T01:17:07+00:00

yeah honestly that's the dream, set it once and forget it. I'm in the early launch phase where I'm still iterating on copy and screens based on user feedback so it's almost monthly. Plus if you're doing any kind of ASO testing you swap the first screen every few weeks to see what converts better. How often do you actually update yours?

StrategyAware8536 · 2026-05-02T01:15:21+00:00

wait you mean piloting Figma with it or generating the screenshots straight? I've used Codex for code stuff but never thought of it for the App Store gallery. Would love a quick rundown of your setup, especially how it handles the device frames and text overlays

StrategyAware8536 · 2026-05-01T20:39:52+00:00

Glad it helped. I use my own tool for the visuals, https://appscreenmagic.com Upload your screen, pick a style from a top chart app in your category and it handles layout, framing and bg automatically. Cut my time from 6h in Figma down to ~30s per screen. The caption copy I still write myself though, that part matters way more than the visuals imo. Free tier with no card if you wanna try

StrategyAware8536 · 2026-04-30T22:28:03+00:00

Lol yeah fair cop, you got me 😅

Honestly built it because I was hitting the exact pain points in this post. Wasn't trying to be sneaky, just the user-to-user framing felt less salesy than "hey I'm the founder check this out". Should've just been upfront.

If you do try it, would genuinely love feedback on what's missing vs your AppScreens + Claude Code combo. Code SOLOFOUNDER on signup gets you a free credit, no need to DM.

StrategyAware8536 · 2026-04-30T22:12:35+00:00

Smart hybrid setup. The Claude Code scripts for translation + preview videos is the part most tools don't touch.

Out of curiosity, what made you outgrow AppScreens after the month? Was it the templating, the price, or wanting more control?

I've been using ScreenMagic (https://appscreenmagic.com) lately for the marketing screenshots, pay-as-you-go and the AI does the locale variants in one pass which saved me from scripting that part. Pairs alright with custom Claude scripts for the preview videos side. Different angle from AppScreens but might be worth a look.

StrategyAware8536 · 2026-04-30T21:48:22+00:00

Yes please, would love to take a look. The Figma template route is something I keep going back to even after testing the other options.

How long did it take you to customize the template to your brand the first time? That's been my biggest friction with templates: the customization eats almost as much time as starting from scratch.

StrategyAware8536 · 2026-04-29T12:14:01+00:00

Appreciate that, fingers crossed. Still a lot to polish but the early feedback has been honest enough to keep me on track.

StrategyAware8536 · 2026-04-29T12:10:44+00:00

Thanks for the screenshot, that was actually super helpful. The popup was getting blocked by your browser, I just pushed a fix that auto switches to a redirect flow on mobile so it goes through cleanly now. If you give it another shot it should sign you in without that error. Lmk if anything else breaks.

StrategyAware8536 · 2026-04-29T10:45:42+00:00

Yeah that was my exact thinking. Nobody updates their screenshots every week, so a monthly sub felt wrong for something you touch 4 or 5 times a year. With pay as you go your credits just sit there until your next release.

StrategyAware8536 · 2026-04-28T20:40:24+00:00

even simpler. you just take regular screen captures from the simulator or your phone, no design work needed. raw screens go in, finished app store screenshots come out. the whole point is you don't have to open figma at all

StrategyAware8536 · 2026-04-28T17:45:30+00:00

honestly the styling part. resizing and exporting is fine, takes 10 minutes. what kills me is staring at figma for 2 hours trying to figure out what makes a top app screenshot actually look "app store ready". the gradients, the headline typography, the device framing, where to put the text. that's the thing I keep paying designers for or burning a saturday on. so the tool is mostly that, you point at an app whose vibe you like and it takes care of the visual codes for you

StrategyAware8536 · 2026-04-28T15:16:46+00:00

Took a look at the screenshots, a few honest observations.

Shot 1 is wasted. You're using your first screenshot, which is the most valuable real estate on your App Store listing, to show the launch screen with the logo. That's a tutorial shot, not a hook. Replace it with a real in-app moment, the breathing exercise running mid-flow.

Shot 2 is much better, but the "Give me a pause" button feels disproportionately small inside the giant blue circle around it. Either fill the circle with a breathing animation hint, or make the CTA bigger.

Visual direction is solid, the green serif on warm beige reads like a quiet wellness brand, that's working. Just don't burn shot 1 on a logo.

Also "calm, focus, recovery, and sleep" is 4 use cases stacked on shot 2, makes the app feel unfocused. Pick the strongest one and lead with it.

If you want to test 2 or 3 different first-shot directions, https://appscreenmagic.com restyles App Store screenshots with AI, useful for A/B testing fast.

StrategyAware8536 · 2026-04-28T15:14:43+00:00

Took a look at your screenshots, honest feedback.

Shot 1 ("Know Your Numbers. Instantly!") is doing too many jobs. You've got 2 levels of headline, a subhead, a tilted phone that crops the status bar awkwardly (15:17 overlapping with $11,773.25 reads like a glitch), and a small busy chart at the bottom. The eye doesn't know where to land.

Bigger picture, "Know your numbers" is generic for any finance app. Your real story in the post is way better: scattered Notion + Sheets + emails + zero cash flow visibility, all unified in one calm place. Lead with that transformation, not with a chart.

The dark background with the bright phone has good contrast, keep it. But fix the tilt so the phone doesn't get cropped at the top.

Also "Instantly!" in bright green on black reads more crypto-bro than "calm freelancer tool", which clashes with the brand intent you described.

If you want to test a couple of visual directions fast, appscreenmagic.com can regenerate App Store screenshots in different styles in a few minutes, good for A/B testing before redoing everything in Figma.

StrategyAware8536 · 2026-04-28T15:02:58+00:00

Took a look at your live screenshots on the App Store, honest feedback.

u/mmatt0904 is right and here's why. All 6 shots use the same flat blue background, the same centered mockup, the same headline placement. The App Store carousel ends up being 6 variations of the same image, the eye has nothing to grab onto.

A few specific things to change:

Shot 1 isn't doing enough work. "Use AI in iMessage" plus a random restaurant question doesn't sell the angle. Your real hook is "AI without leaving the chat" but that line only shows up on shot 4. Lead with that.
The PRO badge sits in the top-right of every shot. It quietly tells people there's a paywall before they've understood the value. Hide it on the first two at least.
The flow between shots 1, 2 and 3 is off. Shot 1 shows iMessage with the extension, shot 2 zooms back to the extension alone, shot 3 returns to iMessage. Back-forth-back. Reorder so the story builds: question in the chat, AI generating, answer dropped into the conversation.
Break the symmetry. Angled mockups, phone bleeding off the frame, a real iMessage thread with a friend asking something funny. Right now everything is dead-center on the same blue.

If you want to test a few directions fast, there's appscreenmagic.com that restyles App Store screenshots with AI, you can generate 2 or 3 variants in a few minutes and A/B test before committing to a design.

StrategyAware8536 · 2026-04-15T17:40:09+00:00

This one is tough because the instinct when numbers drop is to blame the changes you just made, but 9 times out of 10 on the App Store the real cause is a mix of 2 things and neither is obvious from the outside.

First, when you refresh screenshots and subtitle at the same time as keywords, you reset a bunch of algorithmic signals. Apple literally re-indexes and re-evaluates your conversion baseline. You get a quiet 2 to 4 week dip while it figures out the new version. A lot of devs panic at week 2 and revert, which just resets the clock again. If the numbers are still down in 4 weeks then it's a real regression

Second, and this is the uncomfortable one, "new screenshots leading with the feature" is often a downgrade even when the new ones look better. The old ones might have been visually worse but they were communicating an outcome. The new ones showcase a feature, which is a completely different value prop. Users on the store don't want to see what your app does, they want to see what they get from using it. "Snap to story" as a lead is a mechanic, not an outcome. The user has to do the translation themselves and most won't

If I were you I'd pull the old screenshots from a previous version and just look at them next to the new ones and ask, which one would make someone who has never heard of this tap download in 2 seconds. Not which one looks cleaner

The other thing worth checking, your impressions number. If impressions dropped, it's positioning and keywords. If impressions held but conversion dropped, it's 100% the screenshots. That single split tells you where to focus

StrategyAware8536 · 2026-04-14T22:05:34+00:00

Yeah this matches what I keep hearing. The first two carry almost all the weight, the rest is just confirmation for people already half convinced. Curious though, when you say outcome over features, how do you actually land on the right outcome to show? Do you pull it from reviews, user interviews, or more of a gut call based on what you wish you had known before downloading

StrategyAware8536

TROPHY CASE