One scene that is not trapped in one player
Most 3D teaching content is made for a single player: one supplier's app, one kind of device, one contract. When the contract ends, the content goes with it.
MIHWAR (محور), the 3D and XR teaching platform the university owns, starts from the opposite end. A scene is built once and then leaves the platform in four ways. A student opens it in a browser with no install. A lecturer puts on a headset and opens it over WebXR. A student opens it on a phone in AR, from the same URL. A developer takes it into Unity or Unreal as glTF plus a scene manifest.
The point is simple: nothing built is trapped. If you would rather see it first, open the MIHWAR prototype.
WebXR and glTF in plain words
WebXR is a web standard that lets a page talk to immersive hardware. In practice, the page that shows a 3D model on a laptop can also ask a headset, or a phone's AR camera, to show it. There is no app-store step and no download: the link is the delivery. For a university, webxr for education comes down to one practical gain. A lecturer shares a URL instead of maintaining a separate build for every device.
glTF is an open file format for 3D. Think of it as the PDF of 3D models: the geometry, materials, animation and structure of a model in one readable package that many tools can open. It does not belong to the platform that wrote it.
The two fit together. glTF is how the content is stored; WebXR is one of the ways it reaches a viewer. Because both are open, the content and the way it is delivered can change independently of each other.
Four routes out of one scene
| Route | What the viewer needs | What carries the scene | Good for |
|---|---|---|---|
| Browser | A laptop, tablet or lab PC. No install | The page itself, rendered as real geometry | Lectures, lab sessions, homework, a first look |
| Headset over WebXR | A headset whose browser supports WebXR | The same URL | Group sessions and walking through a place or a model |
| Phone AR | A phone that supports AR | The same URL | Placing a model in the room for a quick check |
| Unity or Unreal | A developer and the engine | glTF files plus a scene manifest | Custom builds made by a university team or a partner |
Why open formats avoid lock-in
Lock-in rarely arrives as a trap. It arrives as convenience: a proprietary format, a hosted library, a viewer that runs in one app only. Together they mean the university rents access to its own teaching material, and open formats are what make webxr for education safe to adopt.
Open formats change the arithmetic in three ways. First, readability: a glTF file can be opened in other tools, so the library is not locked behind the platform that wrote it. Second, exit: when the university can export every model and scene, ending a supplier contract becomes a project plan rather than a loss of content. Third, reuse: the same model serves the browser, the headset, the phone and the game engine without being rebuilt for each.
That is why MIHWAR stores the library as glTF in the university's own storage. Every model, scene and 360° capture carries a declared licence and a named owner, so the library still works the day any supplier contract ends. In a per-seat subscription library, by contrast, the university rents content that somebody else owns. We make that wider argument in our post on a university-owned 3D library versus a per-seat subscription.
What the prototype does today
MIHWAR is a working prototype built by Nplay for Interactive Solutions, Amman, and prepared for a Jordanian university. It is not a mock-up and not a video: models are real geometry rendered in the browser, the level builder composes scenes, and the export writes files. Nothing needs an install, plugin or network connection to try it, and a 22-stop tutorial of about six minutes covers three roles: student, instructor and university.
Take the high-bypass turbofan in the model viewer. It is sectioned so the gas path is visible; run the animation and the fan, compressor and turbine turn on one shaft. Its learning outcomes include tracing the gas path from inlet to exhaust. That model is a glTF asset. The same asset can sit in a browser lesson, appear in phone AR, and reach a developer's Unity or Unreal project, without anyone rebuilding it.
A scene is more than one model, which is why the engine route also carries a scene manifest. It describes the composed scene alongside the glTF files, so a developer receives the experience a lecturer built rather than a folder of loose parts. Places work the same way: a 360° capture with teaching hotspots can have the library's models standing inside it.
What a university IT team should check
- Ownership: does every asset carry a declared licence and a named owner?
- Storage: are the files kept as glTF in the university's own storage, not only on a supplier's servers?
- Exit test: can you export a scene and the library, open the files in a second tool, and confirm they still work?
- Devices: which headsets and phones on campus run WebXR and AR from a URL, tested on your own network?
- Baseline: does the no-install route run on the lab PCs you already have?
- Engine route: is there a loader for the engines your developers use, and is it labelled reference or production?
- Review gate: does an academic in the owning college approve each asset before students see it?
- Roadmap: are working features kept apart from planned ones?
Honest limits, and what is reference only
In the prototype the 3D models are indicative rather than teaching-grade. The 360° captures are painted rather than photographed. Four stages of the ingest pipeline are represented rather than executed.
The Developers screen needs its own warning. The Unity and Unreal loaders there are reference code. The REST endpoints are design, not deployment: they show what an API would look like, and nothing in production depends on them. A packaged Unreal plugin and a public API sit in phase two of the roadmap, months 7 to 12 of an engagement, not in the prototype.
Devices have limits too. In any webxr for education plan, remember that WebXR reaches the headsets and phones whose browsers support it. Native headset breadth beyond what WebXR reaches is research from year two of the roadmap, not costed and not promised.
For content built to these open formats, see our 3D content studio. For the full buying questions, use the XR platform evaluation checklist for universities in Jordan.
Webxr for education: frequently asked questions
What does WebXR for education mean in one sentence?
It means a lesson is a web link that can open on a laptop, in a headset or in phone AR, so the lecturer builds one scene instead of one build per device.
Do students need a headset?
No. The first route is a browser with no install, and the phone route uses the same URL. A headset is an option for sessions where being inside the scene helps.
What is glTF and why should a university care?
glTF is an open file format for 3D models and scenes. A library stored in it can be read, exported and reused in other tools, so the university is not dependent on one supplier to open its own content.
Is the Unity and Unreal route ready for production?
Not yet. The loaders in the prototype are reference code and the REST endpoints are design, not deployment. A packaged Unreal plugin is planned for phase two of the roadmap.