Start your first listing system
Use this order if you need a clean launch workflow before you worry about tool comparisons or isolated tactics.
Guides
Editorial guides for app-store growth teams
Playbooks you can cite inside launch planning, asset QA, and multilingual release reviews.
Guides
48 pagesOperational articles for launch planning, review, and asset handoff.
Current section
Compare
6 pagesDecision pages that explain the gap between manual ops and structured workflows.
Open this section
Glossary
12 pagesEntity definitions and ASO vocabulary written for both teams and AI retrieval systems.
Open this section
Case studies
3 pagesNarrative case studies with concrete workflow, decisions, and outcomes.
Open this section
Start here
If you start from this section, follow one of these reading orders.
Each path begins with a key page in this section, then moves into neighboring sections so readers can keep momentum instead of stopping after one article.
Build a screenshot system that can ship
Start with the narrative model, then move into copy, design brief, and a launch case that shows the system working end to end.
Topic paths
Start from a problem path, not just from a content type.
These topic paths connect the current hub to neighboring definitions, comparisons, and case studies so readers can keep moving through one problem instead of one section.
Launch-system foundations
Start with the pages that connect listing workflow, approval state, and launch readiness.
Screenshot production and handoff
Move from screenshot strategy into design-ready execution without dropping the message architecture.
Review control and regenerate discipline
Use these pages when iteration cost, approval state, and regenerate choices need tighter control.
All pages
Browse the full editorial guides for app-store growth teams
If you already know the asset or question type you need, jump straight into the full index below.
3 min read2026-08-08
Which project fields actually change your generated listing copy
A field-by-field breakdown of how description, category, brand tone, and competitors shape generation quality, and why a thin input produces a thin first draft.
Treat the four core project inputs as a briefing document, not a form β output quality is a direct function of input detail.
project setupinput qualitygeneration promptslisting copy
Read the full page3 min read2026-08-08
Running one project across App Store and Google Play
How selecting both target platforms in one project keeps App Store and Google Play copy consistent instead of drifting across two separate projects.
One project per app story, not one project per store β split projects only when the underlying product story actually diverges.
App StoreGoogle Playproject setupmulti-platform
Read the full page3 min read2026-08-08
Generating multiple languages from a single project
Why keeping every target language inside one project prevents factual drift across locales, and what shared generation still can't replace.
One shared input set per app, one review pass per language β the first prevents factual drift, the second catches everything generation can't judge.
multilinguallocalizationproject setupbilingual
Read the full page3 min read2026-08-08
Choosing a brand tone: what each of the seven options changes
A breakdown of the seven brand tone options and how each shifts word choice, rhythm, and formality in generated copy.
Tone is a per-app decision, not an account setting β re-evaluate it every time a new project starts.
brand tonevoiceproject setupcopywriting
Read the full page3 min read2026-08-08
Using the competitors field to avoid generic listing copy
Why leaving the competitors field blank produces generic copy by default, and how to fill it in even when an app feels like it has no direct competitor.
If the field feels hard to fill in, the honest answer is usually "what users would use instead of this app."
competitorsdifferentiationpositioningproject setup
Read the full page3 min read2026-08-08
How the pricing model field changes your generated messaging
How Free, Paid, Freemium, and Subscription each shift the value argument generated copy makes, and why this field needs to match reality.
Pricing model shapes the value argument the copy makes, so it needs to match reality before generation, not after.
pricing modelfreemiumsubscriptionmessaging
Read the full page3 min read2026-08-08
Screenshot style vs. screenshot recipe: what's the difference
Style controls the visual look of each frame; recipe controls how the full set is sequenced. A guide to the 26 styles and 6 recipes and when to use each.
If screenshots look good but don't communicate, the problem is almost always the recipe, not the style.
screenshot stylescreenshot recipevisual designscreenshots
Read the full page3 min read2026-08-08
Writing screenshot highlights that produce usable captions
Why the screenshot highlights field is different from the app description, and how to write moment-based highlights instead of a feature list.
If two generated screenshots end up saying nearly the same thing, the highlights field usually didn't give the generation enough distinct material.
screenshot highlightscaptionsscreenshot copyproject setup
Read the full page3 min read2026-08-08
Linking an existing App Store or Google Play listing to a project
How adding existing store URLs signals a relaunch rather than a cold start, and what those fields don't automatically do.
The URL fields tell the workflow this is an update, not a launch β but the actual continuity still has to be written in by hand.
relaunchexisting listingproject setupApp Store URL
Read the full page3 min read2026-08-08
Why the contact email and website fields matter for App Store review
Contact email and website URL are compliance-critical fields under Apple and Google review guidelines, not incidental metadata.
A stale contact value can stall a review for reasons that have nothing to do with the listing copy itself.
App Store reviewcompliancecontact infosubmission
Read the full page3 min read2026-08-08
What a project's status actually tracks
Status reflects setup and generation progress, not copy quality β why that distinction matters once a team runs more than one project.
Status answers "where is this project in the process," not "is this project's output good."
project statusworkflowproject managementtriage
Read the full page3 min read2026-08-08
How workflow checkpoints keep a review from restarting
Progress tracks how far a project has moved; checkpoint tracks what's actually been reviewed. Why regenerating content invalidates a prior checkpoint.
Progress tells you how far the project has come; checkpoint tells you what's actually been reviewed.
review checkpointworkflow progressreview workflowproject tracking
Read the full page3 min read2026-08-08
Handing off generated listing copy to design and submission teams
Why structured output makes handoff straightforward, and why handoff belongs after a review checkpoint rather than right after generation.
Handoff is a review-gated step, not a generation-gated one β what gets handed off should be what's been checked.
handoffdesign handofflisting copyreview workflow
Read the full page3 min read2026-08-08
Organizing more than one app under a single account
How to name and structure projects for triage once a team or agency is running several apps or clients at once.
A project list is only useful as a management tool if its names and statuses are kept current.
project managementmultiple appsagency workfloworganization
Read the full page3 min read2026-08-08
How text and image regenerate quotas work separately
Text regenerate, image regenerate, and full generation draw from three separate quota pools β why that separation exists and how it affects planning.
Match the regenerate type to the actual problem before spending quota.
regeneratequotatext regenerateimage regenerate
Read the full page3 min read2026-08-08
Free plan vs Pro: what actually changes
The free plan is a one-time evaluation tool with a lifetime cap; Pro moves to a recurring allowance built for ongoing production.
Free answers "does this workflow fit us"; Pro answers "how do we run this workflow at real volume."
free planPro planbillingquota
Read the full page3 min read2026-08-08
How upgrading from monthly to yearly billing works
Why the yearly upgrade charges in full with a separate refund of unused monthly time, rather than a single discounted charge.
The yearly upgrade is full price now, refund of unused time separately β not a single discounted transaction.
billing upgradeCreemprorationsubscription
Read the full page3 min read2026-08-08
Managing your subscription through the Creem billing portal
Why payment method, invoices, and cancellation route to Creem's own portal, and which actions still happen inside the app.
Account-level payment management lives in the portal; plan-level changes tied to app state live in the app.
billing portalCreemsubscription managementinvoices
Read the full page3 min read2026-08-08
What the Sync from Creem button actually does
Sync re-reads the real subscription status from Creem on demand, closing the rare gap left by a delayed or missed webhook.
A mismatch between what was paid and what's displayed is almost always a stale local record, not a failed payment.
billing syncCreemwebhooksubscription status
Read the full page3 min read2026-08-08
How the referral program tracks and rewards signups
Referral rewards are credited as extra full-generation quota, but only after the invited account verifies their email β not at signup alone.
A referral only pays out once the invited account is verified, not once they sign up.
referral programgrowthquota rewardaccount
Read the full page6 min read2026-07-30
App Store title and subtitle best practices
How to treat the App Store title and subtitle as one 60-character message unit: keyword ownership, duplicate-word rules, truncation, and screenshot alignment.
The title and subtitle are one indexable message unit. Assign each field a keyword job and remove every duplicated word between them.
App Store titlesubtitleASOmetadata
Read the full page7 min read2026-07-30
ASO keyword research workflow
A repeatable keyword research process: seed terms, autocomplete expansion, relevance-first filtering, intent clustering, and assigning every cluster an owner field.
Keyword research is finished when every cluster names the field it owns β not when the spreadsheet reaches 500 rows.
keyword researchASOkeyword clusteringmetadata
Read the full page6 min read2026-07-30
Apple keywords field best practices
How to spend Apple's 100-character keyword field: mechanical rules that free characters, overlap stripping, and per-market localization.
The keyword field is pure index space. Every character should carry a term the title and subtitle could not fit.
keywords fieldApp StoreASOmetadata
Read the full page6 min read2026-07-30
App description structure that converts
How to structure an app description for skimmers and the store index: the 170-character opening, benefit paragraphs, proof, and per-store variants.
The first 170 characters are the whole description for most visitors. Structure the rest for scanning, and fork Play and App Store variants deliberately.
app descriptionconversion copyGoogle PlayApp Store
Read the full page6 min read2026-07-30
App Store screenshot size planning
Screenshot size requirements as a coverage problem: anchor masters per device class, derive the rest, and validate the full matrix before submission.
Design masters at the largest size per device class and derive the rest β the expensive mistake is a coverage cell nobody planned, found on submission day.
screenshot sizesApp StoreGoogle Playasset production
Read the full page6 min read2026-07-30
Google Play vs App Store listing differences
The field-level differences that change how you write: index behavior, hidden keywords, short description weight, and how to share one strategy across two stores.
One message hierarchy, two placement maps: Play indexes the description, Apple gives you a hidden keyword field, and copy-pasting between them leaks performance on both.
Google PlayApp Storecross-store strategymetadata
Read the full page7 min read2026-07-30
Chinese App Store localization guide
Localizing a listing for Chinese-speaking storefronts as a strategy port: storefront selection, native keyword research, and semantic parity review.
If your Chinese keyword list could have been produced by a translator who never opened the App Store, the localization has not started yet.
Chinese localizationApp Storebilingual ASOkeyword research
Read the full page7 min read2026-07-30
How to review AI-generated listing copy
A three-layer review process for AI-drafted store copy: truthfulness against the build, differentiation against competitors, and mechanical keyword-placement checks.
AI moves the bottleneck to review. Check truth, difference, and placement in that order β and refuse regenerates that cannot name their failure.
AI copyreview workflowASOquality control
Read the full page7 min read2026-07-30
App Store metadata rejection causes and fixes
The five recurring metadata rejection groups and the pre-submission review pass that catches them before Apple does.
Most metadata rejections are predictable. A five-group pre-submission pass catches them before Apple does; when one lands, fix the class across all locales.
app reviewrejectionApp Storemetadata QA
Read the full page7 min read2026-07-30
The four-week pre-launch ASO timeline
A dependency-ordered pre-launch timeline: research, metadata, creative, then QA and freeze β with rules for compressing it safely.
Any stage may be shortened; none may be reordered or skipped. When launch pressure forces a cut, cut scope β never the QA gate.
launch timelineASOrelease planningQA
Read the full page7 min read2026-07-30
What to automate in ASO (and what not to)
A task-level map of ASO automation: monitoring, validation, and asset derivation reward automation; positioning, claim approval, and narrative design do not.
Machines draft and check; people decide and approve. Automate anything you can verify faster than you can produce β never anything you cannot verify at all.
ASO automationworkflow designAI toolsreview control
Read the full page7 min read2026-07-30
How to evaluate an ASO tool before you commit
A buyer-side evaluation sequence: written job list, trials on your own app and locales, exit-cost testing, and pricing by the fraction you will actually use.
If you cannot name the three tasks a tool must take over β with their current hours β you are not evaluating tools yet, you are watching advertisements.
ASO toolstool evaluationprocurementworkflow
Read the full page7 min read2026-07-30
The post-launch ASO optimization loop
The ongoing ASO process after launch: weekly observation, monthly diagnosis, one change per cycle with a written expectation, and read windows you actually respect.
Launch-week ASO gets the attention; compounding returns live in the loop β observe, diagnose, change one thing, and wait long enough to read the result.
ASO processoptimization looppost-launchmetrics
Read the full page7 min read2026-07-30
How to audit an app store listing
A surface-by-surface audit in discovery order, scoring each surface for currency, coherence, and competitiveness against today's rivals.
Audit in the order users travel, attach evidence to every finding, and convert the top defects into single-variable changes β never a big-bang rewrite.
listing auditASO processconversionQA
Read the full page7 min read2026-07-30
App store localization checklist
A four-stage checklist covering translation, localization, and operations: scoping, native research, the parity pass, and the no-stale-locales rule.
A locale is either complete and current, or a documented, dated, owned exception β the third state is silent decay.
localization checklistglobal releaseApp StoreGoogle Play
Read the full page6 min read2026-07-30
Which locales to localize first
A data-driven prioritization method: rank markets by un-localized traction and language sensitivity against honest per-locale costs, then ship in readable waves.
Localize where you already have traction you are under-serving, at a pace you can maintain forever β a locale you will abandon should not launch.
locale prioritizationlocalization strategymarket expansionASO
Read the full page7 min read2026-07-30
Screenshot headline and subheadline templates
A template library organized by frame job β outcome, proof, mechanism, fear reduction, decision β with worked examples and the rewrite test that kills generic fills.
A template earns its place when the filled result could not be pasted onto a competitor's screenshot β generic after filling means rewrite or reassign.
screenshot copytemplatesheadlinesconversion copy
Read the full page7 min read2026-07-30
Store listing A/B testing: PPO vs Play
How to run listing experiments with Apple's PPO and Google Play's store listing experiments: hypotheses, read windows, and rolling winners into the system.
If you cannot state what a test will teach you when it loses, it is not an experiment yet β it is a slot machine with analytics.
A/B testingPPOPlay experimentsconversion
Read the full page7 min read2026-07-30
Ratings and reviews as ASO inputs
The review feedback loop: rating as a weekly conversion metric, monthly review-language mining per locale, user vocabulary into copy, and well-timed rating prompts.
If review language never changes your listing copy, you are paying for user research and filing it unread.
ratingsreviewsfeedback loopASO
Read the full page7 min read2026-07-30
Version control for listing assets
Why listing packages need versioning: canonical homes per asset, submission snapshots, change logs with reasons, and a restore path you have actually tested.
If you cannot produce last month's exact listing package for any locale in ten minutes, you have optimism, not version control.
version controlasset managementbackupsrelease ops
Read the full page7 min read2026-07-30
Keyword rank tracking workflow
Track a small field-derived keyword set weekly, define action thresholds in advance, and wire every metadata change to the terms that measure it.
Every tracked keyword must answer 'what decision does your movement trigger?' β a term without an answer is being watched, not tracked.
rank trackingkeywordsASO metricsworkflow
Read the full page6 min read2026-07-30
Using Apple's promotional text well
The only listing field updatable without review: what belongs in 170 characters, expiry checks, locale timing, and claims that still get you rejected.
Promotional text is the listing's news ticker β anything true this week that was not true last month. An empty field beats a fossil promotion.
promotional textApp Storeconversionmetadata
Read the full page6 min read2026-05-08
Screenshot copy workflow for app stores
How to move from message hierarchy to screenshot headlines, supporting copy, and design handoff without splitting ASO and creative review.
Use screenshot recipes and review checkpoints to turn store positioning into executable screenshot sequences.
screenshot copyApp StoreGoogle Playdesign handoff
Read the full page6 min read2026-05-08
Bilingual app listing review workflow
A review workflow for teams shipping English and Chinese listing assets without letting meaning drift across metadata, screenshots, and QA.
Review bilingual launch assets as one message system instead of two unrelated translation passes.
bilingual ASOlocalizationreview workflowlaunch ops
Read the full page6 min read2026-05-08
Turn screenshot recipes into design briefs
A guide for converting screenshot strategy into a handoff brief with visual intent, copy hierarchy, and review checkpoints before design execution starts.
A screenshot recipe becomes useful when it tells design what each frame must prove, not just what text to paste on top.
screenshot recipedesign briefhandoffcreative ops
Read the full page6 min read2026-05-08
When to regenerate listing assets
A practical decision guide for choosing between manual edits, text regenerate, and screenshot regenerate without wasting quota or review attention.
Treat regenerate as a workflow decision with visible tradeoffs, not a reflex every time a stakeholder asks for another option.
regeneratequota controlreview workflowlisting ops
Read the full page8 min read2026-05-07
App Store ASO workflow
A step-by-step workflow for turning positioning, metadata, screenshots, and review gates into one release-ready asset system.
Use one project-level workflow to align store copy, screenshot intent, review checkpoints, and launch-week handoff.
ASOlaunch workflowApp Storerelease ops
Read the full page6 min read2026-05-07
App Store release QA checklist
A pre-submission checklist that covers naming, metadata, screenshot storytelling, locale consistency, and stakeholder review.
Use this checklist to catch the gaps that usually surface after screenshots, keywords, and translated copy leave draft status.
QA checklistApp StoreGoogle Playlocalization
Read the full page