agentleFS
mirzaaghazadehmirzaaghazadeh/iwsdk-webxr-skills/skills/custom/horizon-launch-roadmap/SKILL.md

horizon-launch-roadmap

Skill1 starsChanged 31 days agoMITView on GitHub

Plan and sequence the launch of an IWSDK / WebXR game or 2D web app on Meta Quest: choose between hosted web, the Browser new tab page and a Horizon Store PWA; pick 2D vs immersive; list the irreversible decisions (Android package id, signing key, origin and Digital Asset Links, Early Access, pre-order and Coming Soon windows, Data Use Checkup auto-approval, age group, web IAP limits, Meta VR Glasses input and targeting); map each phase to the skill that does the work; and build a dated timeline counting back from launch day, plus post-launch growth tools. Use when the user asks "how do I publish my WebXR game", "should I ship as a PWA or just a website", "what's the release process for a Quest web app", "plan my launch", "when should I submit", "can I do early access / pre-orders", "should I support Meta VR Glasses", or starts a new IWSDK project 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

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the Store app sells an unlock, though, the public site would give the full game away: serve the full game only to the installed app (a …

    line 44
  2. Very specific:

    Before quoting any rule or date, re-verify with metavr docs search "<rule>" or metavr docs fetch <url> if "Last verified" is more than a …

    line 117

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Launch roadmap for a Quest web app (IWSDK / WebXR / 2D PWA)

Made by Navid Mirzaaghazadeh · part of iwsdk-webxr-skills · MIT

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 merged). Review has two stages, technical (the VRCs) then content ("completeness, polish, and value", publish-app-review, 2026-07-07).

Step 1: pick the distribution path

PathWhat users getReviewMoneySource
Hosted URL in Quest BrowserOpen a link; Enter VR buttonNoneYour own web payments (outside Meta billing)web index; web-hosting
Browser new tab page featureCurated tile in Quest BrowserMulti-step (QA, content, technical); 4 weeks at the top of the shelf, then ranked by monthly traffic; not guaranteedSame as hostedbrowser-new-tab (2026-07-22)
Web Launch linkshttps://www.oculus.com/open_url/?url=<encoded-https-url> sends a link from a computer or phone to Quest BrowserNoneSame as hostedweb-launch (2026-07-22)
Horizon Store PWA (this library's focus)Library app, store page, launches like a native appFull Store review (VRCs)Free download only; sell add-ons through Digital Goods IAP, WebXR PWAs only, no subscriptionspwa-overview; ps-iap; Dashboard Pricing tab (2026-10-24)

The paths combine: the Store PWA is a wrapper around the same hosted site, so you can keep the site public. Meta: "A web app can remain available through its website without a PWA package." If the Store app sells an unlock, though, the public site would give the full game away: serve the full game only to the installed app (a start-URL query such as ?app=1 set in Bubblewrap's startUrl, or window.getDigitalGoodsService present) and show a "get it on the Store" page to everyone else. A query string is easy to copy, so this deters, it doesn't protect. Also gate the unlock itself on listPurchases() (horizon-store-listing-assets).

Horizon Worlds is a different product (worlds built in Meta's Horizon desktop editor and hosted by Meta, no APK, no VRC review). A WebXR or IWSDK project does not port into Worlds; pick Worlds only for hosted social creations. Background: docs/research-meta-web.md in this repo.

Step 2: decide early (one-way doors)

DecisionWhy it's hard to undoSource
2D vs immersiveSets horizonOSAppMode, the intent category, auto-enter and which VRC column applies (2D has fewer Required VRCs). Switching later means a rebuilt APK and a different review barpwa-packaging; publish-quest-req
Android package id"Every update to an existing Store app must use the same package identifier." Don't accept Bubblewrap's <reversed-host>.twa default by accidentpwa-packaging
Signing key"Every future update must use the same signing certificate." Lost key = new app. Two offline backups plus the passwordspwa-packaging; Packaging.2
Origin (host)Baked into the APK and checked through /.well-known/assetlinks.json. Moving needs a new APK version and assetlinks on both hosts until users update. GitHub Pages project sites can't serve the origin rootpwa-packaging; horizon-web-store-publish
Version-code schemeOnly goes up across every channel. Bubblewrap bumps it on update unless told not toBubblewrap source; hz-store-submit
Monetization modelA PWA can't be a paid app. The Dashboard says "PWAs are always free on Meta Horizon Store, but you can still sell add-ons and in-app purchases", and its Paid app price list is empty. A pay-once game becomes a free download with a durable unlock add-on (for example the first levels free). That needs horizonBilling and the App ID in the APK, an add-on, and a Data Use Checkup. Web IAP works only in WebXR PWAs and has no subscriptions, so a 2D app or a subscription business needs another plan (web payments outside the Store, or native)ps-iap (2026-10-14); Dashboard Pricing tab (observed 2026-10-24)
Early AccessOnly for newly published apps; turning it off is irreversibleearly-access (2025-12-17)
Coming Soon / pre-ordersOnly during the initial submission; pre-order price can't change; date can't move to within 2 weekspre-launch-listings (2026-08-06)
Data Use CheckupNeeded for Digital Goods IAP and getLoggedInUserId(). Auto-approval ends at the first review submission or a raised channel limit; test those features beforeps-iap; publish-data-use (2026-10-14)
Age groupMixed Ages WebXR PWAs must call getUserAccountAgeCategory() on every launch; Children apps get no Platform SDK features. 2D PWAs have no Digital Goods service (Mixed Ages for 2D: unverified, ask Meta)ps-iap; age-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; the Store shows hand-capable titles first to people without them, and every Bubblewrap TWA declares hand support. Design every flow for hands (and IWSDK gaze-and-pinch) from the startapp-compatibility (2026-10-13); Connect recap (2026-09-24)
Device targetingLIVE must keep a forward-compatible build (Future devices); every build in a submission must be one; a launched device can't be dropped from all buildstarget-builds-by-device (2026-09-04)

Step 3: phases and skills

PhaseDoSkills
0. SetupNode and IWSDK project (npm create @iwsdk@latest); headset in developer mode; Dashboard org + app; verify the orghz-quest-verify-first, metavr-cli, hz-new-project-creation, hz-iwsdk-webxr (plus IWSDK's own skills)
1. BuildInteraction, UI, comfort, MR features; choose WebXR features per device; gaze-and-pinch for VR Glasseshz-iwsdk-webxr, quest-browser-webxr, hz-immersive-designer, iwsdk-vr-glasses
2. HostProduction HTTPS origin you control at the root; staging origin for testshorizon-web-store-publish (references/hosting.md), hz-store-pwa
3. Package and testBubblewrap build, verify, sideload, ALPHA/BETA (200 users default, up to 2,500)horizon-web-store-publish, hz-vr-debug
4. Platform featuresDigital Goods IAP, user ID, age category, server checks; create the add-on (Monetization > Add-ons; it can't be published until the DUC is done); fill the DUChorizon-store-listing-assets (references/policy-pricing.md)
5. Performance and complianceOVR Metrics 45-minute runs; VRC audit; fix FAILs and RISKshorizon-web-vrc-checklist, quest-browser-webxr, hz-perfetto-debug
6. ListingArt, metadata, IARC, age group, privacy policy, pricehorizon-store-listing-assets
7. 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 (Dashboard, by the user)hz-store-submit, horizon-web-vrc-checklist, horizon-store-listing-assets
8. Live opsWeb redeploys via staging; APK updates for native changes; subscribe to analytics alerts; sales, bundles, promo codes, keys; price A/B tests (US only); yearly DUChorizon-web-store-publish, horizon-store-listing-assets

Step 4: timeline, counting back from launch day L

WhenMilestoneRule
Before any uploadPackage id, key, origin, mode fixed; org verified; DDA signedSee Step 2
≤ L-360 dComing Soon page (optional)Up to 360 days out, only in the initial submission (older overview page says 180)
≤ L-90 dPre-orders (optional)Paid apps or free apps with paid IAP; charged 24 h before launch
L-6 to L-4 weeksRelease candidate in RC; VRC audit clean; listing complete; production origin frozenLeave room for one rejection cycle
≥ L-2 weeksSubmit for ReviewMeta: at least two weeks before launch
≥ L-14 dRelease date set (pre-order launches)Date ≥ 14 days out
After approvalRelease now or schedule; wishlists openNo release date before approval
LLaunchCopy future APK builds to Production; web changes go live on deploy, so freeze risky changes around launch. Subscribe to threshold alerts (analytics need > 100 lifetime active users)
L + weeksGrowth experimentsPrice A/B test: ≥ 3 days setup, up to 90 days, US only, 30+ days away from a sale. TBYB isn't available for 2D apps (immersive PWAs: unverified)
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

Plan for review taking longer than two weeks (hz-store-submit: holidays and resubmissions stretch it).

Web-specific risks to track

  • Bubblewrap vs release-manifest rules: Meta's template emits targetSdk 32 / minSdk 23 while the manifest page asks new apps for targetSdk 34 (see horizon-web-store-publish). Upload a first build early, weeks before submission, to learn whether Store checks accept it. One immersive PWA's 32 / 23 build reached Test Status Complete on 2026-10-24; that's not a documented exemption.
  • Unreviewed changes: web deploys reach Store users without review. Keep the reviewed experience, metadata (Content.2) and age-appropriate content stable; test on staging first.
  • Hosting is now production infrastructure: uptime, TLS renewal and the assetlinks file decide whether the Store app launches at all.

Before quoting any rule or date, 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.

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.