If you want to distribute VR training apps to a fleet of company headsets, there are three families of route: the public store, a managed store your admins deploy from, and private distribution reserved for your organization. Private distribution itself splits three ways — a business release channel, a self-hosted APK, or delivery through a third-party MDM. Everything a vendor sells you is a variation on those.
For training, the answer is almost always managed or private. Internal course content rarely belongs in a public listing, and there is a harder constraint behind that preference: Meta's own documentation for Meta for Work states that public Horizon Store apps are discoverable by anyone with a Quest device, and that admins cannot directly deploy public store apps to device groups (Meta developer documentation, 2026). If the plan is "twenty headsets, one course, updated next quarter", the public store is the one route that does not do that job.
The routes at a glance
Each route differs on one axis that matters more than any other: who performs the install. If the answer is "the trainee", you have a discovery problem solved and a deployment problem open. If the answer is "an admin, from a console, to a group", you have something that scales to a fleet. The table below is the short version.
| Route | How the app reaches the device | What it costs you | Fits when |
|---|---|---|---|
| Public store | The user finds and installs it | Nothing to run, no group deployment | Self-serve or consumer audiences |
| Managed store | Admin browses in Admin Center and installs to devices | Eligibility and an organization to set up | Commercial apps on a managed fleet |
| Private: business release channel | Organization key, invite, app added to the app library | A one-time exchange with the developer | A custom or customer-specific build |
| Private: self-hosted APK | Admin adds the APK's URL in Admin Center | Hosting, URLs and version discipline are yours | You want full control of release cadence |
| Private: third-party MDM | Developer supplies the APK, customer installs via their MDM | Whatever your MDM already costs | You already manage the fleet with an MDM |
Public store: discovery, not deployment
The public store answers one question well: how does a stranger find your app? Meta describes public Horizon Store apps as discoverable by anyone with a Quest device, and states plainly that admins cannot directly deploy those apps to device groups. That single sentence rules the public store out as a fleet mechanism, whatever else it does for you.
That does not make it useless for a training vendor. A public listing is a shop window, a trust signal and a way for a prospective customer to try something before signing anything. What it will not do is get a course onto forty headsets on a Monday morning. Companies that discover this late usually discover it while walking around a room with a controller in hand, logging into each device by hand.
Managed store: admins deploy, users see it
The managed store is the middle ground. Meta's documentation describes eligible apps that admins can browse in Admin Center and deploy to managed devices; managed users can then see those apps in their store, and admins can install them directly. You get a catalogue and group deployment in the same place, without hosting anything yourself.
This is the least dramatic option and often the right one. Nobody on your side signs a developer agreement, nobody maintains a download server, and the app you deploy is the same commercial build the vendor ships to everyone else. The limit is eligibility: it works for apps that exist in that catalogue, so a build made specifically for your company will not be there.
Private distribution, three ways
Private distribution means the app is not listed publicly and reaches only your organization. Meta documents three mechanisms, and they differ mainly in who holds the file. Pick based on how much of the pipeline you want to own, not on which sounds most sophisticated — all three end with the same APK running on the same headset.
Business release channel
Here the developer publishes to a business release channel in the Meta Horizon Developer Center. The admin provides an organization key, and through that key receives an invite to the private app, which they then add to their app library. It is a short exchange: you send an identifier, you get access, the app shows up where your other apps live.
The practical appeal is that the vendor keeps doing vendor work. They build, they publish to the channel, and your library reflects it. The practical cost is a dependency on their release process, which is fine when they ship regularly and irritating when they do not.
Self-hosted APK
The second route skips the developer platform entirely. Meta documents that admins can add the URL of a self-hosted APK directly in Meta Admin Center. You put the file somewhere you control, you point the console at it, and that is the distribution channel.
This buys the most control and hands you the most homework. Someone owns the storage, the access rules on that URL, and a naming convention that tells a tired admin at 8am which build is the current one. Teams that do this well keep one canonical URL per channel and treat a version bump as a deliberate act rather than a file overwrite.
Third-party MDM
The third route uses tooling you may already have. Meta describes it simply: the developer supplies the APK and the customer installs it through their MDM service. No release channel, no store, no eligibility question — the file arrives by whatever means you agree on, and your existing management platform pushes it.
If your organization already runs an MDM for headsets, this usually wins on effort alone, because it adds nothing new to operate. Other headset vendors and independent MDM products exist in this space too, with their own consoles and their own terminology for the same idea.
Fleet management is the other half
Getting the APK onto the device is roughly half the problem. The other half is what the device does once it has the app: whether it boots into training, whether a trainee can wander into the browser, and whether one person can act on fifty headsets without handling fifty headsets. That is fleet management, and it is a separate purchase decision from distribution.
The feature list from PICO's Business Device Manager is a fair map of the territory: batch enrolment to bring in a large number of devices at once, real-time remote management to monitor, reboot, shut down, wipe data and factory-reset, content deployment for apps, files and LBE maps, a customizable home screen offering a custom home, kiosk mode or the PICO default, quick configuration deployment that saves configuration packages and pushes them to devices or groups, and flexible user management with custom roles, teams, access management and SSO login (PICO Business Device Manager, 2026). Other vendors package similar capabilities differently, so compare consoles rather than adjectives.
The home screen deserves attention because it is what a trainee actually sees. Locking a headset to one app removes an entire category of support tickets, and we covered the mechanics in how VR kiosk mode works for training headsets. Distribution and kiosk mode are usually configured in the same session, by the same person, in the same console.
Updates: the part teams underestimate
Version one is exciting and everyone shows up for it. Version four lands on a Thursday, has to reach devices in three sites, and must not interrupt a session already running. Ask about the update path before you choose a distribution route, because that is where the real recurring cost sits.
The rule of thumb is straightforward. Where the vendor holds the file — managed store, business release channel — updates arrive on their cadence and your job is to approve and roll out. Where you hold the file, as with a self-hosted APK, nothing moves until someone on your side moves it. Neither is wrong. What hurts is choosing the self-hosted route for the control, then discovering nobody owns the update ritual.
Choosing a route
Start from the fleet, not from the app. Fewer than five headsets in one room and no MDM: a managed store or a business release channel keeps life simple. A managed fleet across sites: use the MDM you already run, and treat the APK as an artefact the vendor hands you. A custom build made for your company: private distribution is the only sensible answer, and the choice between the channel and self-hosting comes down to who you want owning releases.
Hardware choice narrows these options before you make them, which is why we wrote about choosing enterprise VR headsets after Meta's exit. If you are working out which courses will ride on top of this pipeline, the VR course catalog shows what is ready to deploy, and the Skillsive platform handles the training-record side once the app is on the device. The distribution decision is boring, reversible with some effort, and worth twenty minutes before you buy the headsets rather than the week after.
