MyXR Lab: two kinds of admin, and a classroom inside a headset.

MyXR Lab is Virtualtech Frontier’s XR learning platform, and I worked on both ends of it: the web dashboard institutions use to run it, and a headset course for future EV technicians.

Content is tiered by age — under 12, teens 13–17, and TVET or polytechnic learners 18–23 — in 60–120 minute modules split into roughly 15-minute sections. Assets stay low-poly so standalone headsets keep their frame rate: lag and nausea are what the team defined as a poor XR experience.

“Admin” hid two different jobs, so I mapped them as two separate trees instead of one flow full of conditional states.

The Master Admin at VTF registers, edits and removes institutions, drills into analytics from institution to class to student, and manages each institution’s admin account. The Super Admin at a school or polytechnic only works inside their own institution: their account, their classes, their students and their assessment reports.

Permission boundaries became navigation boundaries — each role’s dashboard only lists the modules that role can use. Tenancy is fixed at activation: the school name on a Super Admin’s form cannot be edited.

The second workstream was a headset course on electric vehicles for TVET learners — taught in VR first, then practised hands-on in mixed reality — built from a product requirement document I co-wrote with the team.

The PRD’s case for VR: simulate real workshop tasks and SOPs, give hands-on practice without real-world risk, and allow safe failure with immediate feedback. Its learners — school leavers, community-college students and early-career trainees — prefer tasks to memorising theory.

I researched EV types and components first, then wrote the login and module & level selection sections. In VR the entry experience decides whether a trainee comes back, so both had to be effortless.

The PRD’s comfort rules — teleport-only movement, sessions capped at 15–25 minutes, every instruction voiced — set the frame for the whole course. Inside that frame, each panel I designed answers a specific rule.

An EV holds more structure than a learner can take in at once, so the lesson breaks it into visual layers that the learner switches on in sequence.

Structure, power source and energy flow are three separate toggles, and a component opens an info panel only when the learner asks for depth. The learner sets the complexity curve instead of absorbing it all at once.

The four EV types get the same treatment. Every spec panel keeps one layout and one order — energy source, range, energy flow, key features — so whoever reads one can compare the other three without relearning the frame.

Text that is hard to read in a headset is tiring, so I tuned font size and box placement for readability and comfort first, looks second.

I ended with three variants: a standard box with back and next, an auto-advance box for narration, and a floating box with a portrait for each speaker, all in one glass style I set for the whole UI. Each speaker keeps one colour — teal for B.O.O.My, green for Professor Farahdi, red for Professor Kaldor — so the learner knows who is talking before reading a word.

When the story asks for a choice, there are only two options, and the next arrow stays disabled so a decision can’t be skipped.

A learner has to tell instruction from narrative at a glance, so tutorial, hint, info and safety panels each got their own labelled header, separate from the character dialogue.

The safety note is the loudest of them: every high-voltage circuit, up to 800V DC, is orange-coded and must be treated as live until de-energisation is verified. It is the one panel nobody should skim.

For the assessment module I designed drag-and-drop matching instead of a quiz: the learner shows they understand by putting things where they belong.

Two tasks share one frame. First, drag each EV type and its energy-flow chain onto the matching cutaway car. Then grab the right energy source from the parts shelf and fit it to the car in front of you. One Current Task panel at the top holds the single instruction in play, and Boomy confirms progress in the same dialogue style as the rest of the course.

Everything went to the team as working files: the admin flow file for both roles, my two PRD sections, and a UI kit for the EV course.

The kit holds three dialogue variants for three speakers, four panel types, the layer toggles, the EV category screen with its four spec panels, and the drag-and-drop assessment.

Client feedback isn’t interference — it is the brief getting more accurate. In a studio, the design has to serve the business behind it.

Handoff is a design skill too: Figma layers organised so a colleague can work in them, and a Figma deck rebuilt as a genuinely editable PowerPoint because that was what the client could use.

Next, I would put the dialogue boxes and layer toggles in front of trainees wearing a headset and check two things: can they read a full box comfortably, and do they switch layers on their own or wait to be told?