1. Home
  2. Blog
  3. Publishing on Meta Quest

From Prototype to the Meta Horizon Store: How a Meta Quest App Gets Published

The steps between a working build and a live store page, from a studio that has taken its own game all the way through.

18 November 2026 · RRH Studio · 7 min read

Inside Cooking Tornado: the food truck parked on a Tokyo street at night.

A build that runs well on your own headset is a big milestone, but it is not yet a product. Between that build and a page on the Meta Horizon Store sit several steps that each take time. We went through all of them with Cooking Tornado, which launched worldwide on 17 November 2026. Here is the path, in order.

1. Build for the Headset From Day One

Meta Quest 3 and 3S are powerful, but they are mobile devices. An app must keep a steady frame rate even in its busiest moment, start reliably every time, and recover cleanly when the headset sleeps and wakes. Test on the real headsets early and often, and build comfort options in from the start: snap and smooth turning, seated play and clear ways to recentre.

2. Set Up and Verify Your Organisation

Apps are published by an organisation on the Meta Horizon developer dashboard. Meta asks companies to verify the business before some platform features can be used, and paid apps or in-app purchases also need payout details and tax forms. Start this early: verification and tax questions can take days to settle.

3. Create the App and Choose the Listing Type

Creating the app gives it an ID and a store page to fill in. One choice deserves thought: a Coming Soon listing lets players find the game in the store and add it to their wishlist before launch, and Meta tells them when it is released. It can only be chosen with the first submission, so decide before you submit.

4. Declare Your Data Use

The Data Use Checkup lists every platform feature the app uses, such as the user ID, age group or in-app purchases, with the reason for each. Meta checks it against your privacy policy, which must say plainly what you collect, how it is used and how people can ask for it to be deleted.

5. Age Group and Content Rating

Every app certifies the age group it is made for and completes a content rating questionnaire, which returns ratings for regions around the world. Answer carefully: details such as in-game purchases or what is shown on a sign in the background can change the result.

6. Store Assets

The store page needs cover art in several sizes, screenshots, a trailer, short and long descriptions and the right genres. Meta’s asset rules are strict, for example about text and claims on cover art, so plan the art direction around them rather than fixing it at the end.

7. Meta’s Review

Submitted builds go through Virtual Reality Checks, which test that the app works as described, performs well, follows the platform’s rules and behaves correctly in situations like launching from the library or waking from sleep. If a check fails, Meta explains which one, and a fixed build is submitted again. Each round takes time, so build a margin into the launch plan.

8. Release

Once approved, the release can be scheduled for a date and time of your choice. Check the store settings one last time: an app released with Early Access turned on sits in a separate Early Access section rather than among new releases. Add-ons for in-app purchases are created and published separately, and promotional tools such as store sales open once the app is released.

9. After Launch

Launch day is a start. Watch the store analytics and player reviews, answer players, fix what they find, and keep the store page and trailer current. Updates go through review too, so plan them in.

Need a Hand With It?

We have done every one of these steps for our own game and can take your Meta Quest app through them, or build it with you from the first prototype.

Publish Your App on Meta Quest

Tell us where your project is today and when you want it on the store.