Freeze the release matrix
Choose the exact stores, device sizes, languages, page order, and output format for the release. Validation and publishing should operate against this explicit matrix, not every draft target ever added to the project.
Microsoft Store targets require PNG; other presets enforce their own dimensions and accepted formats.
Run preflight
Preflight checks the selected matrix for missing assets and translations, unsafe bounds, invalid page counts, output dimensions, and target-format rules.
Treat errors as blockers. Review warnings in context and record why an intentional exception is acceptable before producing the final folder.
Render the batch
The native export engine receives the same scene as the editor and reproduces layer order, geometry, overrides, typography scale, backgrounds, and device frames without blocking the interface.
A batch records its progress and summary. Cancel it when the source project changes rather than mixing stale and current outputs.
- Write to a clean release destination.
- Use collision-safe filenames.
- Keep the recorded summary with the reviewed output.
Inspect the release folder
Open every file from every device family and language, then verify ordering and file counts against the matrix. Check actual pixels rather than trusting filenames alone.
If a problem is found, fix the project and render a fresh batch. Avoid hand-editing generated output because that breaks repeatability.
Prepare store connections
App Store Connect uses an issuer ID, key ID, app resource ID, and local p8 key. Google Play uses a package name and local service-account JSON.
Credential contents remain local and are not copied into ordinary project data. Confirm the store application identity before authorizing a dry run.
- Use credentials scoped to the intended app and action.
- Keep key files outside shared project exports.
- Remove obsolete store connections.
Dry run, confirm, and publish
A dry run reports the planned store changes without uploading them. Its approval is bound to a fingerprint of project state, selected languages and sizes, connection, and upload engine.
Any relevant change invalidates that approval. A confirmed upload replaces the intended screenshot group only while the fingerprint still matches, preventing a review of one release from authorizing another.