ASC GUI · Native for Mac · In development

Prepare your next
App Store release.
On your Mac.

Edit localized listings, arrange media, and manage review and release workflows in one native workspace.

See the workflow

Built for developers updating their Apple apps.

Illustrative workspace: Field Notes version 2.4, English and Spanish listings, a local draft, Save, and a build inspector.
Workspace concept · Illustrative demo data, not a product capture. View image ↗

Native Mac workspace

Local drafts

Explicit Save

Reusable release workflows

A place to prepare

Prepare changes.
Save when ready.

App Store Connect is Apple’s service for managing your App Store apps. ASC GUI brings listing and release work to your Mac, with local drafts and a deliberate Save to send changes to Apple.

01 / LISTINGS

Give every locale
the same attention.

Edit descriptions, keywords, What’s New, and URLs. Keep the app, version, and language in view as you prepare each listing.

02 / REUSE

Keep the useful parts
of your last release.

Preview and reuse selected text from the previous released version. Bring in saved review contact details and URL defaults.

03 / DRAFTS

Pick up where
you left off.

Listing edits and staged media stay in a local draft between sessions. Save sends the prepared changes to App Store Connect.

Screenshots & app previews

Put your media
in order.

Bring in the assets you’ve already made. Arrange screenshots, play app previews, and select poster frames before uploading.

  • Keep media with its localization and device group
  • See capacity and validation as you prepare
  • Stage additions and removals before saving
Illustrative media composer for Field Notes, with three ordered screenshots and an app preview staged for the English listing.
Media concept · Illustrative demo data. View image ↗

The release workflow

One release.
Clear next steps.

From a local draft to a release request, each action has a purpose. Saving, submitting for review, and releasing are separate decisions.

  1. 01

    Connect.

    Add your API key. Choose a profile, an existing app, and a version.

  2. 02

    Prepare.

    Edit each localized listing, arrange media, and choose a compatible processed build.

  3. 03

    Save.

    Send prepared changes to App Store Connect. Check Activity if an update needs attention.

  4. 04

    Submit.

    Inspect supported requirements, select versions, and confirm submission. Apple decides the review outcome.

  5. 05

    Release.

    Use the version’s release policy, or request manual release when Apple reports the version eligible.

Saved automations

Repeat your
release workflow.

Save the inputs, review the plan, and follow each platform through the run.

  • Prepare Release — prepare changes and run supported checks. This can update App Store Connect; it does not submit for review.
  • Submit for Review — submit reviewed versions and inspect Apple’s status. Newly created versions need an additional metadata and media review first.
  • Release Approved Versions — request release for eligible versions, with a result for each platform.

Runs need ASC GUI running on your Mac. Quitting interrupts local execution; sleep pauses follow-up. Check status and explicitly continue interrupted work after returning. Requests already accepted by Apple can continue independently.

Illustrative Prepare Release plan for Field Notes version 2.4, with separate pending iOS and macOS targets before a run.
Automation concept · Illustrative demo data. View image ↗

When work needs attention

Check the result.
Then continue.

When an update is uncertain, Activity gives you a place to check its status. Review conflicting local and remote values, then continue from the recorded result.

See the conflict.Review your local draft alongside values from App Store Connect.

Check before retrying.Inspect uncertain operations before sending remaining changes.

Follow each platform.Separate results show which targets completed and which need attention.

A direct connection to Apple

Your drafts on your Mac.
Your key in Keychain.

Connect directly to App Store Connect with a team or individual API key. Access depends on your key’s permissions and the app’s current state.

  1. 01

    Add your key.

    Open Settings and add an App Store Connect API key. Credentials are stored in this Mac’s Keychain.

  2. 02

    Choose your workspace.

    Select a named profile, an existing app, a platform and version, then a localization.

  3. 03

    Prepare your update.

    Keep drafts locally. Saving content, uploading media, and checking release status connect to Apple’s services.

A few details

Good to know.

Is ASC GUI available to download?

ASC GUI is in development. Download availability, pricing, and final system requirements have not been announced.

What will I need?

A compatible Mac, an existing app in App Store Connect, and a valid API key with access to the work you want to perform. Final macOS and hardware requirements will be confirmed with the release.

Which platforms can I manage?

The current workspace supports version workflows for iOS, macOS, tvOS, and visionOS, subject to your app’s eligibility and Apple’s restrictions. iPhone and iPad media belong to the iOS workflow. ASC GUI itself runs on Mac.

Do I need Xcode Cloud? Can I upload a build?

Xcode Cloud is optional. Choose an existing compatible processed build in App Store Connect, or start an already configured Xcode Cloud workflow and follow its progress. ASC GUI does not archive, sign, or directly deliver IPA or PKG files. Keep using your existing build delivery workflow.

Does it work offline?

Drafts and staged media are stored locally. Connecting, opening or refreshing a workspace, uploading, checking status, submitting, and releasing require Apple’s services.

Can automations run while my Mac is off?

No. Automations run locally while ASC GUI can execute. Quitting interrupts execution and sleep pauses local follow-up. After returning, check status and explicitly continue. Waiting steps also have a limited observation period and may need a new status check. Apple can continue processing requests it has already accepted.

Does it replace all of App Store Connect?

No. ASC GUI focuses on listings, media, versions, review, and release work. Age ratings, App Privacy, pricing and availability, agreements, and some compliance or product requirements still need Apple’s website. Supported checks do not certify that every Apple requirement is complete.

Does it translate listings or create screenshots?

No. You edit localized text and manage existing media. ASC GUI does not generate translations, listing copy, screenshots, or videos.

Does submitting mean my update is live?

No. Submission, Apple’s review decision, and distribution are separate stages. Release requests depend on eligibility, and each platform has its own result. ASC GUI does not guarantee approval or simultaneous publication.

Where is my API key stored?

In this Mac’s Keychain. ASC GUI uses it to authenticate direct requests to App Store Connect. Local drafts stay on your Mac until you save their content to Apple. App Review demo passwords are excluded from saved drafts and automation history and may need to be entered again.

ASC GUI for Mac

Your next update.
A familiar workspace.

Prepare locally. Save deliberately. Follow the release.

See the workflow

In development. Release details will be announced here.