Why an XR platform is a procurement decision, not a demo
Choosing an XR platform for universities Jordan and the Gulf can still rely on in five years mostly comes down to what happens after the demo. Demos show the best model in the catalogue. They rarely show who owns it, who checked it, which course module it serves, or what happens to your students' work when the contract ends.
The nine questions below are the ones we would ask from the buyer's side of the table, and they apply to any supplier, including us. We show how MIHWAR answers each. MIHWAR (Nplay for Interactive Solutions, Amman) is “the 3D and XR teaching platform the university owns”: a working prototype prepared for a Jordanian university, not a deployed service. We say where its answers stop.
Nine questions, and how one platform answers them
| Question | What to look for | How MIHWAR answers |
|---|---|---|
| 1. Ownership and export | Named owner, open format, export on demand | Named owner on every asset; glTF in the university's own storage |
| 2. Licence declaration | A licence recorded on every asset | Declared licence beside every owner |
| 3. Coverage by module | An auditable module list per college | Planning target of about 660 assets across eleven colleges |
| 4. Review workflow | Named academic reviewer, queue, publish step | Four production routes, one academic review gate |
| 5. Devices and WebXR | One scene on every device | Browser, headset over WebXR, phone AR, Unity or Unreal |
| 6. LMS link | A plain statement of what is connected | Progress would come from the LMS in a real deployment; not connected in the prototype |
| 7. Analytics for deans | Coverage, contribution, outcomes | Planned for months 7 to 12 |
| 8. Roadmap honesty | Now, planned and research kept apart | Four tiers, the last not costed or promised |
| 9. Pilot first | A trial a lecturer can run alone | Browser, 22-stop tutorial, about six minutes |
Ownership, export and the licence declaration
Start here, because everything else depends on it. A per-seat subscription library gives access, not ownership: when the subscription stops, the access stops. Ask where each file lives, in what format and who can open it without the supplier. Open formats such as glTF matter because any 3D tool can read them. We set out the economics in university-owned 3D library vs per-seat subscription.
Then ask about licences. Every asset should carry a declared licence and a named owner, so a lecturer knows whether a model can be shown at an open day or shared with another college. In MIHWAR every model, scene and 360° capture carries both.
Student contribution adds one more question. MIHWAR's student marketplace idea, a way for students to earn from models they contribute, is a proposal for the university's legal office only. It touches intellectual property, student contracts and tax, we expect it to change in review, and we promise no earnings. Settle student intellectual property before the first upload.
Coverage mapped to modules, and a review workflow that scales
Catalogue size is the number suppliers advertise and buyers should distrust. Ask for three numbers instead: how many of your modules are mapped, how many assets carry a defensible licence, and how many an academic in the owning college has checked. MIHWAR's planning target is about 660 assets, described as covering every practical module in eleven colleges: a number a university can reach, audit and own.
Coverage needs production routes. MIHWAR has four: student coursework, campus capture, AI-assisted generation and commissioned modelling, all through the same academic review gate. A student uploads, an academic reviews, and the asset joins the library. Because the library grows by coursework rather than by purchase order, cost per module falls each year instead of recurring. See student-built 3D content for a university library.
Ask whether the platform handles places as well as objects. A lecturer can capture a ward, a hangar or a dig site on a consumer 360° camera and add numbered teaching hotspots; see 360° captures with teaching hotspots.
For AI generation, ask whether a human decides after the draft. In MIHWAR's AI Studio a draft model comes back in under a minute and a human decides whether it is fit for students. In the prototype the geometry is synthesised in the browser as a stand-in for a provider call; the review gate, licence declaration and flow are real. Status: generation live, review gate live, provider calls specified. Detail in AI 3D generation and the review gate.
Devices and WebXR reach, the LMS link and analytics for deans
Devices. Ask for the same content on every device. MIHWAR runs one scene in a browser with no install, in a headset over WebXR, on a phone in AR from the same URL, and in Unity or Unreal as glTF plus a scene manifest. WebXR reaches what a headset's browser can reach; native headset breadth is year 2 research, not promised. See one scene, four ways out.
The LMS. Ask exactly what is connected. In the prototype the student home shows tasks set by instructors, such as contributing a model or building an experience from three library models. Course progress would come from the LMS in a real deployment; the prototype does not connect to one.
Deans. Deans need coverage per module, contribution per college and attempt outcomes. In MIHWAR these are scheduled for months 7 to 12. If a supplier shows a dashboard, ask whether it is live data or a design.
Roadmap honesty: working now, planned, and research
| Tier | What it covers | Status |
|---|---|---|
| Working now | Ten capabilities, including the model viewer, 360° hotspots, level builder, review queue and export | Try it today |
| Months 1 to 6 | Eight planned items | Planned |
| Months 7 to 12 | Seven items, including lecturer-led multi-user sessions, an Unreal SDK plugin, AI generation behind the review gate, a public API and analytics for deans | Planned |
| Year 2 onwards | Five research items, including native headset breadth beyond WebXR and cross-institution library sharing | Not costed, not promised |
What the MIHWAR prototype does not do yet
- 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 developer REST endpoints are design, not deployment.
- It is a prototype: no deployment, contract, users or results are claimed.
Pilot first, then decide
A supplier who states its limits is easier to trust, and a pilot turns trust into evidence. The best test of an XR platform for universities Jordan lecturers will use is one a lecturer can run without IT help. MIHWAR's guided tutorial has 22 stops, takes about six minutes and covers three roles: student, instructor and university.
Then pilot one college and one set of practical modules. Decide beforehand what you will measure, such as modules mapped, assets reviewed and time from upload to publication, and what result would make you stop. The same questions apply across the Gulf, and to our campus use case. To put them to us, write to info@nplay.tech or request a conversation.
XR platform for universities Jordan: frequently asked questions
What should a university ask first when choosing an XR teaching platform?
Who owns each asset, in which format, and whether the university can export everything if the contract ends.
Is a bigger asset library always better?
No. What counts is how many assets map to your course modules, carry a defensible licence and were checked by an academic in the owning college.
Do students need headsets?
Not with a browser-first platform. MIHWAR runs in a browser with no install, in a headset over WebXR, and on a phone in AR from the same URL.
Is MIHWAR available now?
It is a working prototype built by Nplay and prepared for a Jordanian university, not a deployed service. Write to info@nplay.tech to discuss a pilot.