Make screenshots
in your coding chat.
Connect AiSCent to your coding agent, then ask it to run the App Store screenshot workflow. AiSCent supports project detection, Simulator capture, locale and device coverage checks, App Store Connect comparison, and approved uploads. You review the real image files and any screenshot marketing copy.
Ask in your coding chat
Tell your agent which Xcode project, device sizes, and storefronts you want. AiSCent provides release tools behind the scenes.
Check the real image files
Your agent runs supported build and Simulator capture workflows. AiSCent organizes and compares the output, including checks for identical files reused across different language or script groups.
Approve the upload
Review actual app screens and any separately designed marketing copy. Then approve the matching screenshot sets for App Store Connect.
What makes an App Store screenshot set work?
Each frame should make one point: the customer benefit, the product in use, or proof that the app solves the job. Use the real app screen as evidence and give the story a clear headline. A row of unexplained simulator captures rarely does that work.
Does AiSCent translate the app itself?
No. AiSCent captures and manages screenshots; it does not create finished marketing overlays or translate your app interface. Localize the app in Xcode and create or review any sales copy separately. Check every storefront for natural wording, readable layout, and the correct image before publishing.
Can an AI coding agent run screenshot capture?
Yes. Compatible agents such as Claude and Codex can use AiSCent's MCP tools to detect an app, capture selected locales, compare output, and upload screenshots. The MCP connection is configured once; the screenshot workflow stays in your coding conversation.