Getting Started with ASOFlow
A focused workflow for editing and localizing App Store metadata on your Mac.
A focused workflow for editing and localizing App Store metadata on your Mac.
Before you begin
Use a Mac running macOS 14 or later. To manage a real app, you need internet access and an Individual or Team App Store Connect API key with access to that app. Basic manual editing does not require an ASOFlow registration or password.
You can begin with Explore Sample to learn the workflow offline.
1. Connect and choose your workspace
Choose Connect Your App, select the key type, enter Key ID and any required Team Issuer ID, then import the .p8 key. Choose to remember it in Keychain or use it only for the session.
After validation, select the app, platform and version. Check that all three match the release you intend to edit. Use the app menu or Choose App / Version… when switching workspaces.
2. Edit your local draft
In Edit, work by language or compare a field across languages. Change the text you intend to update and resolve field-limit warnings.
Apple snapshots and local drafts are separate. Fetching remote content does not automatically approve your edits.
3. Request optional translation or ASO candidates
In Translate, choose the relevant source and target languages. Use alignment for existing translations, maintain glossary terms and protect manually refined wording.
Starting an AI action sends selected text and relevant context to ASOFlow’s backend and DeepSeek. The inline notice describes this processing. AI needs available service allowance; results are candidates for your review.
For subtitle and keyword ideas, supply an accurate brief and useful seed terms. Choose and refine the final text yourself. ASOFlow does not provide verified search-volume or difficulty metrics.
4. Review and approve
Compare the proposed text with the current values. Check language, factual accuracy, branding and validation warnings. Approve only the fields and languages you intend to change.
Unchanged approved human translations are preserved. When source wording changes, you decide which updates to accept.
5. Preview and confirm the Apple write
Refresh Apple successfully, resolve conflicts, and inspect the Dry Run. Confirm the current preview to write the approved metadata.
A metadata save is separate from review submission. In supported versions, prepare screenshots and review details, select an eligible build already uploaded to Apple, inspect the submission preview and explicitly confirm submission. ASOFlow does not upload build binaries or automatically release apps. Apple determines eligibility and review outcomes.
6. Check results
Review per-item outcomes in History. If part of a batch fails, retain successful results and refresh Apple before previewing failed items again. An uncertain result must be checked against Apple before retrying.
Extend to more languages
Use Add Languages… for missing locales. This flow can use the current local source draft, including edits not yet synced to Apple. Check the selected source before generating. Generate candidates, edit each language, fix validation issues, preview and explicitly confirm the save. A multi-language operation can use several AI requests.
Helpful habits
- Keep a concise glossary for product names and recurring terms.
- Review one meaningful change at a time.
- Check the app, platform and version before every write.
- Keep backups and avoid putting sensitive information in AI input.
- Return to welcome with Home or ⌘⇧H; use Continue to resume when available.
Need help? Visit Support or email support@hip958.com.