Goldie packages App Store and Google Play screenshot production, plus App Store preview rendering, into a public CLI with a coding-agent skill. Argent replays the configured flows in an iOS simulator or Android emulator; Goldie adds bezels, backgrounds and headlines, joins preview clips, and checks the output against store upload rules. Developers can start that pipeline through a compatible agent or run the CLI themselves. Goldie's repository documents both routes.
Agent-assisted and manual routes
The packaged skill works with agents that support the skills format. In the documented workflow, a developer asks for app-store screenshots from the application repository; the agent asks which stores to target, explores the app, writes the flows and configuration, and opens Goldie's browser-based studio. Follow-up instructions modify the same files. The README describes this agent workflow.
Manual operation starts with a goldie.config.ts file whose scenes point to Argent flows under .argent/flows. The goldie doctor command checks tools, simulators and flows; goldie all captures and frames screenshots, renders the preview, and verifies the output; goldie studio opens the assets for adjustment. Generated files go under out/screenshots/<device>/<locale>/ and out/previews/<device>/<locale>/. Those commands and paths are specified by the project.
The division of responsibility is explicit: Argent performs the flow replay, while Goldie handles the resulting store assets. Goldie describes itself as framework-agnostic because it drives the app through a simulator or emulator, and the project lists SwiftUI, UIKit, Jetpack Compose, Flutter, React Native and Kotlin Multiplatform among the applicable frameworks. The repository explains this simulator-level approach.
Host and store constraints
Goldie requires Node 20 or newer and ffmpeg on the system path. Creating App Store screenshots requires macOS with Xcode's iOS simulators, while the Android emulator used for Google Play screenshots can run on macOS, Linux or Windows. The installation requirements are documented in the README.
The studio can switch devices, backgrounds, templates, bezels and fonts, as well as edit copy for individual tiles. It saves those choices in goldie.design.json, which the CLI then uses when rendering. Goldie's design documentation lists these controls and the saved file.
The documented output is 1320 × 2868 for iPhone screenshots, 886 × 1920 H.264 for an App Store preview, and 1080 × 1920 for Google Play screenshots. Apple previews must run for 15 to 30 seconds. The repository specifies these dimensions and the Apple duration window.
For Android, the pixel-10-pro device key renders Play Store phone screenshots from the same scenes used elsewhere, but a flow works across both platforms only when its selectors match. Goldie also renders a portrait promotional video from the emulator for separate posting to YouTube; Apple's 15-to-30-second rule does not apply to that Google Play workflow. The Android documentation distinguishes these outputs.
UI changes remain a maintenance cost
The project recommends release builds because debug builds can add LogBox banners to captures. It also warns that flows fail when the app changes, requiring developers to ask an agent to repair them or re-record them with Argent. Both limitations appear in the README's remarks.
Analysis: Goldie's defensible value is process integration, not proof of design quality. It combines scripted app states with saved presentation settings and exposes their configuration to an agent-assisted workflow. The unresolved trade-off is selector maintenance: because the project explicitly warns that flows break as the application changes, teams still need to repair or re-record scenes as the UI evolves. That interpretation follows from Goldie's documented workflow and maintenance warning.
Top comments (0)