PreviewSmith

Turn the SwiftUI previews you already wrote into store art

Mac

Design Tools

Developer Tools

Visit WebsiteSee on Product HuntApp Store ⧉

Hey Product Hunt 👋 I kept re-taking screenshots I had already written. Every release, the same lost afternoon: boot the simulator, navigate to the screen, capture, repeat across five device sizes, drag it all into a browser tab, write the same description again in a field that counts down from 4,000, discover the 13-inch iPad set is missing, start again. Meanwhile my Xcode project was full of #Preview blocks rendering those exact screens, every day, for free. PreviewSmith came out of that. Point it at an Xcode project and it renders the previews you already wrote, lays them out as a gallery you can search and inspect, and tells you which ones are already a legal App Store size. Drop one into a real device bezel — iPhone 17 Pro Max in Cosmic Orange, iPad Pro, MacBook Pro, iMac — add a title and a background, and it composites at the exact store pixel size, so nothing is resampled and nothing surprises you at submission. Then it does the half I didn't expect to build. Bump the version in Xcode and PreviewSmith will create that version in App Store Connect for you — release type, date, copyright, and the languages taken from the ones your project is already built for. It writes the copy too: name, subtitle, promotional text, description, keywords, What's New, one language at a time, every field counted against its real App Store Connect limit as you type. Edits stay marked until you send them, and anything you'd rather not send goes back to what App Store Connect last returned. A coverage grid shows the device sizes and locales you still owe. A checklist goes further and compares the languages your project ships against the ones the store holds — in both directions, because shipping a language with no store copy and writing store copy for a language you don't ship are both things I have done. It's a Mac app, macOS 26 and later, and it needs Xcode installed because it renders previews by driving it. One thing I'd rather say myself than have found: rendering previews downloads a small helper process. It's signed with my Developer ID and notarized, and the app and helper verify each other before they exchange anything. It exists because driving Xcode's mcpbridge and reading the files Xcode writes to its own temp directory are both impossible inside the App Sandbox, and everything in a Mac App Store bundle has to be sandboxed — so it can't be embedded. It adds no features. Happy to go into it properly if anyone wants to. Your API key lives in the keychain, behind Touch ID if you want it there. Your images and your copy stay in your document. Nothing goes anywhere except App Store Connect, by you, when you say so. Every image in this gallery was made in PreviewSmith. Seemed only fair. It's free for your most recent release on each platform, and a subscription opens up the rest. I'd genuinely like to hear how you handle screenshots and store copy today — especially if you've built your own thing to do it. Ask me anything.