What to know

Apple lets you assign a primary and a secondary category. The primary category is important for discoverability because it affects where the app appears when people browse or filter App Store results.

Choose the category that best matches the app’s main job, not the category with the most attractive label. Use the secondary category only when it describes a real part of the product. For Games and Stickers, Apple also provides subcategories in some cases.

Use a simple decision rule: what problem does the app solve most often, what would a new user expect to find under, and which category best matches the current build? Compare the answer with the first screenshot, subtitle, description, and onboarding flow. If those stories disagree, fix the product-page story before choosing a category.

Record the reason for each choice in the release brief. Recheck the category against the current product, metadata, screenshots, and App Review requirements before submission.

Review the secondary category as a truth check, not extra keyword space. If the app only touches a topic once, the category may confuse users and reviewers. Revisit both choices when the product adds a major workflow or changes from a tool into a broader service.

Separate category research from keyword research. A category helps people browse and understand the app’s place in the store. It is not a substitute for relevant metadata. Keep the category explanation, keyword evidence, screenshot message map, and product brief together so the page tells one consistent story.

Check the decision in the U.S. storefront and every other locale you support. Category names, subcategories, and user expectations can differ by storefront. Save the selected values, the Apple reference used, the date checked, and the owner who approved the change so a future update does not begin from memory.

Compare candidate categories in a small table: primary user job, strongest supporting screen, expected browse context, possible mismatch, and evidence from the current build. Choose the category with the clearest product proof, then document why a nearby category was not selected. This keeps the decision grounded in user understanding rather than a hoped-for ranking effect.

Review primary and secondary categories together with the page message. If the first screenshot and subtitle point to one job while the category suggests another, a new visitor has to resolve the conflict. Fix the product-page story or choose a more accurate category before submission.

Treat category selection as a versioned product decision. Save the storefront, category values, Apple reference, build number, date checked, owner, and approval. Reopen it when the main workflow, audience, or supported content changes, not only when the metadata team starts a new release.

Keep category and keyword decisions in separate rows. A keyword describes language a person may use. A category describes where the app belongs when people browse. A phrase can be useful in metadata without being a truthful category, and a category can be accurate without supplying a new keyword.

Reopen the decision when the main workflow, audience, content source, pricing model, or supported region changes. Compare the new product brief with the old category evidence and screenshots. If the app has become a different kind of tool, update the page story before trying to preserve the old classification.

Ask a reviewer outside the metadata team to describe the app from the selected category and first screenshot. If they expect a feature the build does not provide, record the mismatch and resolve it before submission. This quick comprehension test is more useful than choosing a category because it sounds broad or competitive.

Use a candidate table with category, primary user job, supporting workflow, browse context, possible mismatch, storefront, and reviewer decision. Select the category with the clearest current proof, and record why close alternatives were rejected instead of relying on memory or competitive assumptions.

Run a release-triggered category check when the main workflow, audience, pricing model, content source, or supported region changes. Compare the new build and first screenshot with the approved category rationale before keeping the old choice.

Keep a no-change outcome available. If the category is accurate but the page message is unclear, fix the name, subtitle, screenshots, or onboarding story rather than changing classification to compensate for a product-page mismatch.

For a simple decision example, a journaling app should compare the category that matches its daily writing workflow with nearby categories suggested by one optional feature. Choose the primary category from the main job a new user can complete, then use the secondary choice only when the second workflow is real, visible, and supported by the build.

ASOgenic can keep category decisions beside the metadata and screenshot evidence so the team can explain the choice later. It can flag mismatched claims, but your team makes the final category decision from the current product and Apple’s category list.