Advanced Mixed Reality Development and Best Practices
summary
Top 10 development checklist focused on practical wins: use remote rendering (Unity/Unreal) to offload GPU-heavy scenes, reduce CAD meshes with Simplygon/Pixyz or Umbra dynamic LOD, and prefer the Mixed Reality Toolkit for full-hand input and UI. On-device inference via WinML/ONNX drops object recognition from ~700ms on CPU to ~80ms on GPU. Cross-device persistence and sharing work using Azure Spatial Anchors (anchors re-localize and persist across HoloLens/iOS/Android); demos and GitHub code are provided.
AI-written summary · about
chapters (12)
- 0:00Introduction to session
- 2:53Treat Hololens as mobile device
- 10:03Use Hololens instinctual inputs
- 11:07Design UI for 3D freedom
- 15:20Let apps live in real world
- 17:47Optimize stabilization plane
- 19:55Share Holograms globally
- 23:46Learn deep neural networks
- 28:05Understand AR cloud basics
- 33:22Enable cross-platform anchors
- 40:25Demo persistent multi-user content
- 48:14Summary and resources
related talks
46mHoloLens 301: Advanced Mixed Reality Development and Best Practices
23mFuture of User Interaction: Mixed Reality, AI and IoT
36mMixed Reality - 3 Axes of Improvement
10mMixed Reality check
50mDeveloping for Mixed Reality with HoloLens
01h 03mDiscussion on Experiences and Getting Started in Mixed Reality
31mPower of Azure in Mixed Reality
01h 00mReal World HoloLens Mixed Reality Development with Unity - Be Part of the Future