Portfolio Checklist for XR Designers After the Workrooms Exit

Portfolio Checklist for XR Designers After the Workrooms Exit — Your 2026 Playbook

Hook: Meta’s shutdown of Workrooms in early 2026 left many XR designers asking: how do I show I’m platform-agnostic, future-ready, and valuable to employers who no longer buy into a single vendor stack? If you worry your demos live only on one headset or in one walled garden, this checklist fixes that problem.

In 2026 the XR hiring landscape favors designers who can prove they deliver across headsets, the web, mobile, and mixed-reality toolchains. Below is a practical, prioritized checklist of 10 portfolio pieces and demos every XR designer should have — plus presentation templates, hosting options, metrics to track, and examples of how to turn each item into an interview-winning case study.

Meta ended Workrooms and stopped business Quest sales in February 2026. That’s not the end of XR — it’s a reminder to be cross-platform, web-first, and narrative-driven.

Why this checklist matters in 2026 (quick overview)

Late 2025 to early 2026 showed a decisive shift: enterprises pulled back from single-vendor VR suites while browsers and standards matured. Web-based 3D (WebXR/WebGPU), broader OpenXR adoption, and AI-assisted asset pipelines now enable richer, platform-agnostic demos that run on phones, desktops, and headsets.

This means hiring managers expect designers who can:

• Ship interactive demos that run in a browser and degrade gracefully.
• Show cross-device collaboration flows (desktop → phone → AR headset).
• Document constraints, performance budgets, and accessibility choices.

The 10 essential portfolio pieces (start here)

Each item below includes: what to build, what files to include, how to host, and what to say in the case study. Aim to make each piece a 2–4 minute storytelling asset for interviews.

1. Web-based interactive scene (three.js / Babylon / model-viewer)

   What to show: A lightweight, interactive scene that runs in a modern browser and demonstrates core XR interactions (gaze, touch, locomotion, selection) without requiring a headset.

   • Deliverables: Hosted live demo URL + GitHub repo + a downloadable glTF/GLB and a compact build.
   • Tech notes: Use WebGPU/WebGL fallback, draco compression, and progressive LODs. Include a small script showing detection of device capabilities and graceful degradation.
   • Story: Explain constraints, performance budget (FPS, draw calls), and how you preserved interaction parity across devices.

2. Cross-platform collaboration case study (core of “platform-agnostic” proof)

   What to show: A documented project that enabled real-time collaboration between users on different devices (desktop + mobile + AR headset).

   • Deliverables: Demo video (2–3 min), architecture diagram (WebSockets/ WebRTC/Relay), user flows, and sample server code or architecture notes.
   • Impact metrics: latency targets, sync accuracy, and user task completion rates from your usability test.
   • How to present: Focus on decision trade-offs — why you used web tech for persistence, which features required native clients, and how you validated the UX.

3. Platform-agnostic prototype (OpenXR + fallback paths)

   What to show: A prototype built to OpenXR where possible, with explicit fallback paths for non-OpenXR devices (iOS/ARKit and web).

   • Deliverables: Video demo, README showing build/ deploy steps, and a list of inputs mapped across devices.
   • Why it matters: Hiring teams want to see you can design to an abstraction (OpenXR) rather than lock into vendor SDKs.

4. Mini demo reel + annotated clips (90–120 seconds)

   What to show: A tight showreel highlighting interaction design, spatial UI, and real end-user outcomes. Annotate clips with your role, tools, and an outcome metric.

   • Deliverables: 1080p mp4, chapter markers, and a text transcript for accessibility.
   • Pro tip: Start reel with the problem and end with a measurable impact (e.g., reduced task time by 30%).

5. UX research & test artifacts (study reports & videos)

   What to show: Excerpts from user tests, task analysis, and key insights that informed design changes.

   • Deliverables: One-page study summary, anonymized session clips, before/after changes, and metrics.
   • Why it wins interviews: Demonstrates you can validate design choices with users instead of assuming them.

6. Performance & accessibility audit

   What to show: A short audit for one of your demos outlining FPS targets, memory budgets, occlusion culling, and accessibility accommodations for low-vision and locomotion-impaired users.

   • Deliverables: Audit PDF, prioritized fix list, and before/after performance numbers.
   • Tip: Include how you measure metrics: Web vital analogs (frame timing), network payload sizes, and binary sizes for headset installs.

7. Interactive UI component library (spatial UI patterns)

   What to show: A small library of repeatable spatial UI components (menus, tool palettes, contextual help) implemented in web/engine of choice.

   • Deliverables: Live storybook-like demo, code snippets, and design tokens (units, scale, contrast ratios).
   • Why: Demonstrates systems thinking and reuse — crucial as teams move away from monolithic vendor toolsets.

8. Creative technical demo — shader/haptics/physics

   What to show: One technically ambitious piece — a shader effect, tactile haptics pattern, or realistic physics interaction you built.

   • Deliverables: Source shader, short screencast showing it in use, and notes on performance trade-offs and fallbacks.
   • How to narrate: Show why the technique mattered for UX (clarity, affordance) not just aesthetics.

9. Asset & pipeline documentation (from concept to runtime)

   What to show: A clear pipeline for modeling, texturing, LODs, and runtime compression that reduced build sizes or load times.

   • Deliverables: Flow chart, tool list (Blender/ Maya/ Substance/ AI tools), and before/after asset size reductions.
   • Example metric: Reduced average model size by 70% using draco + texture atlasing and achieved 90% first-frame load improvement.

10. Business or education case study (outcomes, not just tech)

    What to show: A project where XR solved a real business or training problem — ideally with measurable ROI or learning outcomes.

    • Deliverables: Executive summary (one page), outcome metrics, testimonial or project stakeholder quote, and your role breakdown.
    • Why it closes deals: Post-Workrooms, businesses want clear outcomes from XR investments. Show them.

How to package each piece for maximum impact

Each portfolio piece should follow the same concise case study structure so recruiters and hiring managers can scan quickly. Use this template:

1. Project title + one-line impact (e.g., “Remote Design Reviews — reduced signoff time by 40%”)
2. Context & goal (constraints, platform targets, team size)
3. Your role & contributions (design, prototype, architecture)
4. Key decisions & trade-offs (why web-first, why OpenXR, fallback choices)
5. Outcome & metrics (quantitative where possible)
6. How to explore (live demo, video, repo)

Tools, templates and hosting — practical recommendations (2026)

Don’t just show files. Make demos dead-simple to open.

Hosting & live demos

• Netlify / Vercel — fast web-hosting for WebXR builds (automatic deploys from GitHub).
• GitHub Pages — good for static three.js or model-viewer demos.
• PlayCanvas — for engine-hosted web experiences that run in browsers without heavy build chains.
• Cloud streaming for heavy prototypes — record a short demo and provide a link instead of requiring a local install.

Portfolio platforms & file management

• Use a lightweight portfolio website (static site generator or Webflow) and embed demos. Avoid siloed vendor galleries.
• Host source artifacts in public or private GitHub repos and include clear README run steps.
• Include downloadable assets (glTF/GLB, USDZ) and consider CDN hosting for large files.

Templates you can steal

• One-page case study PDF template (problem → approach → impact)
• 90–120s demo reel script template (hook → challenge → outcome)
• Performance audit checklist (FPS, draw calls, binary size, network payloads)

Metrics & storytelling that hiring managers care about

In interviews, the numbers and decisions will stand out. Track and show:

• Load time reductions (e.g., first interactive time)
• Framerate targets and achieved averages (90Hz/120Hz where applicable)
• Task completion or learning outcome improvements from user tests
• Server costs or payload reductions for collaboration features

Advanced strategies: future-proofing your portfolio

Beyond the 10 pieces, adopt these 2026-forward tactics to stay competitive.

• Design to abstractions: Favor OpenXR/WebXR/Open Standards so your work translates as SDKs change.
• Web-first experiments: The 3D web continues to be the quickest way to show interactive work to recruiters.
• AI-assisted annotations: Use AI to auto-generate condensed transcripts, accessible captions, and changelogs for prototypes.
• Data-driven narratives: Pair UX outcomes with telemetry snapshots (anonymized) to prove your assumptions.

Real-world example: a cross-platform case study outline

Use this mini-template to convert an existing project into a platform-agnostic portfolio piece.

1. Project: "Virtual Design Reviews"
2. Context: Team of 5, remote, required cross-device sketching and annotation
3. Deliverable: Browser-hosted collaborative canvas + optional AR view
4. Your role: Interaction lead — built web controller and spatial annotation system
5. Tech: three.js + WebRTC for sync, WebXR fallback for AR viewers
6. Outcomes: Reduced review cycles from 5 to 3; 25% more stakeholder participation
7. Files: Live demo link, architecture diagram, short 90-second clip

Common pitfalls and how to avoid them

• Only showing headset footage: Convert to web demos or add a browser fallback. Recruiters often can’t run a headset.
• Too much tech, not enough outcome: Lead with the problem and how the design solved it, then show the tech as the how.
• Missing documentation: Include run steps and a one-paragraph technical summary with each demo.

Quick production timeline — build this portfolio in 8 weeks

Use this sprint plan if you're rebuilding your portfolio after Workrooms exit.

1. Week 1: Inventory existing projects and pick your top 6 to convert to platform-agnostic pieces.
2. Weeks 2–3: Build web-based demos and record polished videos for heavier experiences.
3. Weeks 4–5: Write case studies, create 90–120s reel, and perform performance audits.
4. Week 6: Assemble portfolio site, embed demos, and link GitHub repos.
5. Weeks 7–8: Polish accessibility, add transcripts/captions, and prepare interview one-pagers.

Checklist recap — what to include right now

• 1 live web-based interactive scene
• 1 cross-platform collaboration case study
• 1 OpenXR-friendly prototype with fallbacks
• 1 annotated demo reel (90–120s)
• 1 UX research summary
• 1 performance & accessibility audit
• 1 interactive UI component library
• 1 creative technical demo (shaders/haptics)
• 1 pipeline & asset documentation
• 1 business/education case study with outcomes

Closing: The Workrooms exit is a pivot, not an endpoint

Meta’s decision to discontinue Workrooms and to limit business sales of Quest hardware in early 2026 is a clear signal: enterprises will favor flexible, measurable XR investments. Your career benefit? Designers who can demonstrate cross-platform fluency, web-forward demos, and measurable outcomes will be the most in-demand.

Start by converting one existing headset-only demo into a web-first interactive today. Then pick one collaboration case study to document end-to-end. In two weeks you’ll have two powerful pieces that show you adapt to the market — not to a single vendor.

Actionable next steps

• Convert one demo to a browser-based playable by the end of the week.
• Create a 2-minute video case study for a cross-platform collaboration example.
• Publish both on a simple portfolio site and include a one-page PDF case study for each.

Need a template? Use the one-page case study structure above for each project. If you want peer feedback, ask for a focused critique: "Can you find the outcome metric in under 20 seconds?"

Call to action

Ready to make your portfolio platform-agnostic and interview-ready for 2026? Download the printable 10-item checklist and the one-page case study template from smartcareer.online, or book a 30-minute portfolio review to get actionable edits tailored to your work.

Related Reading

• Hot-Water Bottles vs. Electric Space Heaters: Which Saves More in a Cold Snap?
• 13 Beauty Launches Salons Should Stock Now: A Curated Retailer Checklist
• From Karlovy Vary to Streaming: Firsts in European Films Landing Global Buyers
• Designing Incident-Ready Architectures: Lessons from X, Cloudflare, and AWS Outages
• Use AI Tutors to Scale Your Content Team: Onboarding Templates from Gemini Experiments