agentleFS
Sign inStart free
mirzaaghazadehmirzaaghazadeh/unity-meta-quest-skills/skills/custom/horizon-launch-roadmap/SKILL.md

horizon-launch-roadmap

Skill1 starsChanged 30 days agoMITView on GitHub

Plan and sequence a Unity Meta Quest game launch on the Meta Horizon Store: which skill to use at each phase, the irreversible decisions (package name, signing key, Early Access, pre-order and Coming Soon windows, Data Use Checkup auto-approval, Meta VR Glasses input and targeting), and a dated timeline counting back from launch day (Coming Soon up to 360 days, pre-orders up to 90 days, submit at least 2 weeks ahead, release date at least 14 days out), plus post-launch growth tools (alerts, price A/B tests, Try Before You Buy). Use when the user asks "how do I publish my Quest game", "what's the release process", "plan my launch", "when should I submit", "can I do early access / pre-orders", "should I support Meta VR Glasses", or starts a new Quest game meant for the store.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
SKILL.md

Horizon Store launch roadmap for a Unity Quest game

Made by Navid Mirzaaghazadeh · part of unity-meta-quest-skills · MIT

This is a routing and planning skill. Each phase points to the skill that does the work. Since 2024-07-31 every Quest app ships through the Meta Horizon Store; App Lab is merged (distribution-options). Review has two stages: technical (the VRCs), then content ("completeness, polish, and value", per publish-app-review, 2026-07-07). Press coverage of the 2024 App Lab merge said subjective-quality rejections would end. Meta's current page still describes a content review, so plan for one.

Decide early: one-way doors

DecisionWhy it's hard to undoSource
Package nameMust be unique and is the app's identity on the Storepublish-mobile-manifest
Signing keystoreEvery update must use the same key. Back it up in two placeshz-store-submit (Meta skill)
Version code schemeOnly goes up, across every channel and draftpublish-mobile-manifest; unity-prepare-for-publish
Early AccessCan be enabled only for newly published apps. Disabling is irreversibleearly-access (2025-12-17)
Coming Soon / pre-ordersCan be created only during the initial submission. Pre-order price can't change. You can't move the release date to within 2 weeks of todaypre-launch-listings (2026-08-06)
Data Use CheckupAuto-approval ends at the first review submission or a raised channel limit. Test every Platform SDK feature before thatpublish-data-use (2026-10-14); hz-store-submit
Age groupMixed Ages requires the Get Age Category API within 30 days. Children apps lose all Platform SDK featuresage-groups (2026-04-02)
Org verificationWithout it you can't publish, update or recertifypublish-organization-verification
Input model (Meta VR Glasses)VR Glasses (spring 2027) ship without controllers, and the Store shows hand-capable titles first to people without them. Retrofitting hands late is expensive; decide at design time whether every flow works with hands (and gaze)app-compatibility (2026-10-13); Connect recap (2026-09-24)
Device targetingLIVE must always keep a forward-compatible build (Future devices), and every build in a submission must be one. A launched device can't be dropped from all builds; you can only hide the app with Purchase-Blocked Devicestarget-builds-by-device (2026-09-04)

Phases and skills

PhaseDoSkills
0. SetupUnity ≥ 6000.0.66f2, Meta XR SDK, OpenXR, URP; Dashboard org + app; verify orghz-quest-verify-first, unity-cli, hz-new-project-creation, hz-unity-meta-core-sdk, quest-unity-project-settings
1. Build the gameInteraction, UI, comfort, MR features; hands and gaze if you target VR Glasseshz-unity-meta-interaction-sdk, hz-unity-meta-quest-ui, hz-immersive-designer, hz-unity-meta-mixed-reality-utility-kit, meta-vr-glasses-unity
2. Platform featuresEntitlement, achievements, IAP, leaderboards, presence; create add-ons (Monetization > Add-ons; publishing one needs the DUC)hz-unity-platform-sdk (fill in DUC before submitting; steps in horizon-store-listing-assets §4)
3. Internal and external testingSigned builds to ALPHA/BETA (200 users default, up to 2,500); test usershorizon-store-publish-unity, metavr-cli, hz-vr-debug
4. Performance and complianceOVR Metrics 45-min runs; VRC audit; fix FAILshorizon-vrc-checklist, hz-perfetto-debug, hz-unity-code-review
5. ListingArt, metadata, IARC, age group, privacy policy, pricehorizon-store-listing-assets
6. SubmitA draft build in the Production (LIVE) channel attached on the Build tab (only those can be attached), age group self-certified, sharing preferences confirmed, then Submission tab > Submit for Review (the user's click)horizon-store-publish-unity Step 7, hz-store-submit
7. Release and live opsRelease now or schedule; subscribe to analytics alerts; sales, bundles, promo codes, keys; price A/B tests (US only) and Try Before You Buy once there is data; updates via production; yearly DUC recertificationhorizon-store-listing-assets (references/policy-pricing.md), horizon-store-publish-unity

Timeline, counting back from launch day L

WhenMilestoneRule
≤ L-360 dComing Soon page live (optional)Up to 360 days before launch, created during initial submission, needs approval. The older monetization overview says 180 days
≤ L-90 dPre-orders open (optional)Up to 90 days before launch; paid apps or free apps with paid IAP; charged 24 h before launch
L-6 to L-4 weeksRelease candidate in RC channel; full VRC audit passes; listing completeLeave room for one rejection cycle
≥ L-2 weeksSubmit for ReviewMeta: submit at least two weeks before the target launch
≥ L-14 dRelease date set (pre-order launches)Full release submission with a date at least 14 days out
After approvalChoose release now or a scheduled date; wishlists openYou can't set a release date before approval. Managed releases go through the account manager
LLaunchCopy future builds to production to update users. Subscribe to threshold alerts (crash rate > 5%, Quest 3 FPS < 72, 1-star ratings, startup > 19 s); analytics need > 100 lifetime active users
L + weeksGrowth experimentsPrice A/B test: starts ≥ 3 days after setup, up to 90 days, US only, keep it 30+ days away from a sale. TBYB: first trial at ≤ 50% audience (30-day experiment)
Spring 2027Meta VR Glasses on saleAn approved Production build marked Future devices reaches them with no new APK
L + 1 yearDUC recertificationOtherwise the app is removed from the Store

Plan for review taking longer than two weeks. Meta's hz-store-submit says holidays and resubmissions stretch it.

Before telling the user a date or rule

These rules change. Re-verify with metavr docs search "<rule>" or metavr docs fetch <url> if "Last verified" is more than a few months old, and cite the URL in the answer.

Sources

Pages moved from developers.meta.com/horizon/ to /vr/ (old links redirect).

Last verified: 2026-10-24

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free