Save time. Reduce rework. Release with clarity.

The platform brings assets, localizations, release notes, and preparation checks into one workspace. Maestro capture kits and Fastlane screenshot import support repeatable capture workflows, while version history and field-linked findings reduce the effort of locating files and resolving supported issues. Time savings depend on your team’s workflow; no fixed savings estimate is claimed.

The dashboard summarizes your app portfolio, including draft, in-review, and live app counts, assets, language coverage, and items needing attention. The Release Center computes readiness from the assets, copy, notes, and details recorded for a release. These are operational preparation indicators; they do not include download, revenue, conversion, or store rejection-rate analytics.

The pre-release workflow brings together saved listing-copy checks, permission and configuration pre-review, computed release readiness, and personalized release guidance. Check missing text, store field limits, draft markers, supported permission declarations, and gaps in saved release content. Findings include suggested actions and store references. These are preparation checks; they do not run the app or predict store approval.

Yes. Open Team review on an app’s Store assets page. Any owner or admin of that organization can approve a file or request changes with feedback, and every member can comment. Each screenshot, icon, or other creative version keeps its own discussion and decisions. Replacing the file starts a fresh review. Permissions follow each organization’s existing roles, including owner-only workspaces. Internal sign-off does not submit the app to Apple or Google.

Yes. Open Screenshot automation in your app’s Assets tab. Define up to 10 screens with optional tap and wait element IDs, preview the YAML, and download a Maestro capture kit with instructions. Run it on your machine or CI, then import the captured PNGs through the asset uploader. Existing Fastlane snapshot or screengrab users can import their captures through the same workflow. Hosted execution, automatic CI result fetching, and automatic screen discovery are not included. Android needs a compatible installed app; iOS simulator capture requires a simulator-built .app on macOS with Xcode, rather than a device IPA.

Yes. In Releases → Release guidance, answer questions about your app’s category, login, purchases, permissions, privacy, and audience. Follow-ups cover OTP delivery and repeatable demo access for reviewers, astrology and dating considerations, social or random-chat safety, and SMS or call-log access. The resulting iOS or Android checklist includes relevant store links, completion tracking, and a download. Answers and progress are saved in this browser per user, app, and release; they do not sync with teammates or other devices. The checklist reflects your answers and does not inspect your build or guarantee approval.

Yes. In your app’s Releases tab, open Permission & configuration pre-review. iOS accepts a built XML Info.plist, plus optional PrivacyInfo.xcprivacy and release entitlements. Android accepts a readable merged release AndroidManifest.xml, plus optional network security XML. Files are checked locally for supported configuration issues and review follow-ups. The report does not inspect app binaries, verify runtime consent or SDK behavior, or predict approval.

Yes. Add a rival’s bundle ID or package name in your app’s Competitors tab. The first check saves a baseline; later checks show changes to public app names, descriptions, Google Play short descriptions, and screenshot URLs or order. Basic includes 1 competitor per app; Team supports up to 5. Monitoring uses the US storefront. Use Check now to refresh a rival’s listing; scheduled checks are currently disabled. History shows when a change was detected. App Store coverage uses the iPhone screenshot gallery from Apple’s public API.

Open an app → Releases → Release copy check. You can also open it from Localizations after saving your edits. The release copy check reviews saved App Store or Google Play listing text for required fields, length limits, draft markers, template tokens, and store-specific patterns such as duplicate Apple keywords or Google title formatting. It reports checks passed, blockers, and review flags per language, with suggested fixes, field links, and store policy references. English promotional and assurance phrase checks run only for English locales.

No. Copy-check percentages describe automated checks passed, not approval or rejection probabilities. Configuration reports assess only the uploaded files and selected features. Flags need human review; neither report verifies the app binary, runtime behavior, screenshot accuracy, or every store requirement. Apple and Google make the final review decision.

Yes. Register apps for the App Store and Google Play, then organise their artwork, listing copy, and releases in the same workspace. Fields and asset requirements follow the platform you choose.

Publishing still happens in App Store Connect or Google Play Console. Releaseyour.App helps you prepare the assets, copy, release notes, and review information, and track readiness and release status in one place.

Prepare phone and tablet screenshots with crop or fit controls, and generate store and browser icon sizes from a master icon. Team also includes App Store header resizing and iPhone Duo asset lanes. Google Play feature graphics are checked against the required 1024 × 500 dimensions.

iOS apps include an App Store product-page preview with saved copy, icons, screenshots, and video previews. Switch the listing language and device assets to review them together. The final layout is determined by the App Store.

Assets and localized copy have version history, including options to restore earlier versions. Each release has its own version, build, status, and localized What’s New text, so you can revisit the context of previous updates.