AR / VR / XR Developer
XR developers must communicate spatial concepts — field of view, presence, degrees of freedom — to designers, product managers, and platform reviewers who may never have worn a headset. This path builds the vocabulary to document interactions, write release notes, explain performance constraints, and pitch spatial experiences clearly across technical and non-technical audiences.
Topics covered
- spatial computing
- visionOS
- XR input methods
- MR/AR/VR distinctions
- performance optimization
- WebXR
Vocabulary spotlight
4 terms every AR / VR / XR Developer should know in English:
Computing that blends digital content with the physical world, allowing interaction in three-dimensional space
"Apple Vision Pro marked a major step forward for spatial computing as a consumer platform."
A camera-based feed of the real world displayed inside a headset, enabling mixed-reality experiences
"In passthrough mode, virtual objects appear to sit on your real desk."
The angular extent of the observable world visible through a headset at any moment
"The wider field of view in the new headset makes peripheral content feel more natural."
Six degrees of freedom — the ability to track position and rotation on all three spatial axes, enabling full room-scale movement
"Without 6DoF, users cannot lean in to inspect objects placed in the scene."
The subjective feeling of "being there" in a virtual environment; a key quality metric for immersive experiences
"Latency above 20 ms breaks presence and causes simulator sickness."
A visionOS window mode that takes over the full field of view for a fully immersive experience
"We use an immersive space for the 3D model viewer so nothing distracts from the object."
📚 Vocabulary Reference
Key terms organised by category for AR / VR / XR Developers:
Spatial Concepts
Tracking & Input
Platforms & APIs
Performance
Recommended exercises
Real-world scenarios you'll practise
- Documenting XR UI interactions in a design spec so a designer unfamiliar with 3D space can understand the interaction model.
- Explaining spatial audio positioning to a sound designer new to XR development.
- Writing visionOS App Store release notes that highlight the immersive features without using jargon.
Recommended reading
Frequently Asked Questions
What English skills do AR / VR / XR Developers most need to improve?+
AR / VR / XR Developers most commonly need to improve: technical vocabulary (the correct English terms for domain concepts), collocation accuracy (using the right verb for each action), written communication (bug reports, PR descriptions, technical docs), and spoken communication for standups, code reviews, and stakeholder meetings.
How long does the AR / VR / XR Developer learning path take?+
The AR / VR / XR Developer learning path contains 20–40 hours of material studied comprehensively. Most learners focus on the highest-priority modules first and return to the rest over time. Spending 30 minutes per day for 4–6 weeks produces noticeable improvement in workplace English.
What vocabulary should a AR / VR / XR Developer prioritise first?+
Start with the vocabulary that appears most in your daily work — terms you read in documentation, use in commit messages, and hear in meetings. The AR / VR / XR Developer path begins with the most frequent vocabulary clusters before moving to advanced communication patterns.
Are there interview exercises for AR / VR / XR Developer roles?+
Yes. The AR / VR / XR Developer path includes role-specific interview question modules with model answers and key phrases — the actual questions interviewers ask and the vocabulary needed to answer them fluently. There is also a dedicated Interview Practice hub for general interview skills.
Does this path include pronunciation help?+
Yes. The path links to pronunciation exercises for the technical terms most commonly mispronounced in this domain. The Pronunciation hub includes drills for acronyms, silent letters, word stress, and minimal pairs — all in IT context.
What are the most common English mistakes AR / VR / XR Developers make?+
The most common mistakes: incorrect collocations (using the wrong verb with a technical noun), false friends from L1, tense errors when narrating past incidents or walkthroughs, and using overly formal or overly casual register in written communication.
How do I improve my English for code reviews?+
Learn the standard code review collocations: approve a PR, request changes, leave a nit, address feedback, block a merge, resolve a conversation. Use hedging language for suggestions: "This might be cleaner as…", "Have you considered…?". The Collocations section includes a dedicated Code Review set.
Can I use this path alongside my daily work?+
Yes — the path is designed for working professionals. Each exercise set takes 10–15 minutes. The most effective approach is to study a vocabulary module before a meeting or task where you'll use that vocabulary, then practise immediately after. Context-linked practice produces much faster retention.
Is the content free?+
Yes, completely free. No registration required, no payment, no time limit. All vocabulary modules, exercises, glossary entries, and learning path guides are open access.
How do I track my progress through this path?+
Progress is tracked in your browser's local storage — completed exercise sets are marked with a checkmark when you return. No account is needed. You can bookmark specific modules and use the exercises overview to see which sets you've completed.