Cost To Hire Extended Reality Developers By Experience Level
Expect to pay $25–$60/hr for entry-level, $60–$100/hr for mid-level, and $100–$175+/hr for senior and expert contractors, while equivalent full-time roles often map to $55,000–$90,000, $90,000–$140,000, and $140,000–$180,000+ respectively.
Experience strongly predicts delivery speed, architectural quality, and the hidden cost of revisions. The following ranges align with typical XR competencies and the complexity organizations expect at each level.
Entry-Level (0–2 Years): What Can You Realistically Expect?
Entry-level professionals generally land between $25–$60/hr (or $55,000–$90,000 salaried) and perform best on scoped tasks in stable toolchains.
They are ideal for well-defined tickets, prototypes, and content pipelines where senior guidance is available. Budgets stay predictable when non-blocking tasks—UI wiring, prefabs, unit testing, scene assembly—are delegated to this level.
-
Typical Capabilities: Implementing simple AR features, basic VR interactions, prefab management, UI, integrating SDK examples (e.g., ARCore plane detection), light optimization with guidance.
-
Best-Fit Work: Proof-of-concepts, internal demos, tutorial-grade tasks, content updates, regression fixes, analytics hooks under supervision.
-
Risks To Budget: Over-reliance on “figure it out on the fly,” unclear specifications, and insufficient code review can inflate rework time.
-
Sample Weekly Spend: 20–30 hours × $40/hr ≈ $800–$1,200 for prototype assistance.
Mid-Level (2–5 Years): Where Velocity Meets Reliability
Mid-level XR engineers usually command $60–$100/hr (or $90,000–$140,000 salaried) and move comfortably from feature design to production-grade implementation.
They manage end-to-end features, assess trade-offs, and catch pitfalls early. If you want to progress beyond a demo into something shippable, this bracket is often the backbone of your delivery.
-
Typical Capabilities: Feature architecture, performance tuning for mobile headsets, integrating third-party content/SDKs, multiplayer basics, asset pipelines, platform deployment (Quest, Pico, Vision Pro, HoloLens).
-
Best-Fit Work: Mid-scope features—hand tracking interactions, object occlusion, networked lobbies, spatial mapping-based gameplay, in-app purchases.
-
Risks To Budget: Scope creep without product guardrails; platform-specific edge cases (e.g., ARKit vs. ARCore) that multiply QA time if not planned.
-
Sample Monthly Spend: 160 hours × $80/hr ≈ $12,800 for a feature sprint across a single platform.
Senior (5+ Years): Why Premium Rates Can Lower Total Cost
Senior and expert XR developers typically charge $100–$175+/hr; top-tier specialists can exceed $1,000/day for highly specific integrations (advanced shaders, SLAM tuning, bespoke rendering pipelines).
Though pricier per hour, seniors optimize architecture and de-risk the riskiest parts of the roadmap—reducing downstream rework and time-to-market.
-
Typical Capabilities: Cross-platform architecture, custom render pipelines, shader/HLSL/GLSL mastery, advanced optimization (GPU/CPU), CV/ML-assisted features (segmentation, body tracking), platform portability (OpenXR).
-
Best-Fit Work: Enterprise-grade builds, large-scale environments, multi-user synchronization, hardware integrations (depth sensors, eye tracking, hand tracking), compliance-conscious deployments.
-
Risks To Budget: Under-utilization—if tasks are too junior, you pay a premium for work a mid-level can do. Keep their focus on the highest-leverage problems.
-
Sample Three-Month Budget: 12 weeks × 30 hrs/week × $140/hr ≈ $50,400 for specialist leadership and delivery of critical systems.
Experience Versus Total Cost: A Quick Comparison Table
A compact view helps translate rates into practical budgets for XR deliverables.
|
Level |
Typical Hourly |
Common Salary (Annual) |
Best-Fit Scope |
Example 6-Week Cost (30 hrs/week) |
|
Entry |
$25–$60 |
$55k–$90k |
Prototypes, UI, SDK samples |
~$4,500–$10,800 |
|
Mid |
$60–$100 |
$90k–$140k |
Production features |
~$10,800–$18,000 |
|
Senior |
$100–$175+ |
$140k–$180k+ |
Complex systems |
~$18,000–$31,500+ |
Cost To Hire Extended Reality Developers By Region
Expect higher rates in the United States, Canada, and Western Europe (often $80–$175+/hr), competitive rates in the UK and ANZ ($70–$160/hr), and excellent value in Eastern Europe, Latin America, India, and Southeast Asia (typically $30–$90/hr), with outliers above or below depending on specialization.
Regional variation reflects cost of living, market maturity, and how saturated a location is with platform-specific talent (e.g., Apple Vision Pro, HoloLens, Quest). Here’s how the landscape generally breaks down.
Regional Benchmarks At A Glance
The following ranges are directional and assume professional-grade contractors or agencies capable of shipping production work.
|
Region |
Typical Hourly |
Senior Specialist Outliers |
Common Notes |
|
United States |
$90–$175+ |
$200–$250+ |
Highest demand; deep Unity/Unreal talent; strong enterprise work. |
|
Canada |
$80–$160 |
$175–$200 |
Toronto, Vancouver hubs; strong gaming/film pipeline skills. |
|
Western Europe (DACH, Nordics, Benelux) |
$80–$160 |
$175–$220 |
Strong enterprise AR, industrial XR, premium agencies. |
|
United Kingdom |
$75–$155 |
$170–$210 |
London ecosystem; creative studios; hybrid work norms. |
|
ANZ (Australia, New Zealand) |
$70–$150 |
$160–$190 |
Smaller pool; strong creative/gaming cross-over. |
|
Eastern Europe (Poland, Ukraine, Romania, etc.) |
$40–$100 |
$110–$140 |
Excellent value; robust Unity/Unreal; often great English. |
|
Latin America (Brazil, Argentina, Mexico, etc.) |
$35–$95 |
$100–$130 |
Time-zone friendly to US; fast-growing WebXR talent. |
|
India |
$30–$85 |
$90–$120 |
Large talent pool; rapid AR/VR upskilling; strong cost/value. |
|
Southeast Asia (Vietnam, Philippines, Indonesia) |
$30–$85 |
$90–$120 |
Competitive rates; strong mobile optimization skills. |
|
East Asia (Japan, South Korea) |
$80–$160 |
$170–$220 |
High-end R&D, device OEM collaborations. |
|
Middle East (UAE, KSA) |
$60–$140 |
$150–$180 |
Smart city/enterprise XR investments on the rise. |
Why Geography Still Matters For XR
Rates are interwoven with hardware availability, enterprise demand, and platform maturity in each locale. In places with strong media/film industries, expect top-tier technical artists and shader specialists; in regions with thriving mobile ecosystems, expect excellent Quest/mobile optimization skills.
-
Time Zone Fit: Near-shore teams command a premium for real-time collaboration.
-
Device Focus: Vision Pro, HoloLens, and ruggedized enterprise AR often require rare skills—raising rates where that talent clusters.
-
Regulatory/Compliance: Certain markets add cost for data privacy workflows and certification.
Cost To Hire Extended Reality Developers Based On Hiring Model
Compared to a single FT hire, contractors and studios shift cost toward hourly/project rates but reduce long-term overhead, while full-time roles trade higher fixed costs for deeper institutional knowledge.
Your hiring model affects not only price but also velocity, continuity, and IP stewardship. Choose it based on the phase of your XR journey—prototype, pilot, or scale.
Model-By-Model Reality Check
This table frames common models with the budgets you’ll typically see and when each shines.
|
Hiring Model |
Typical Cost |
Best For |
Watch-Outs |
|
Full-Time (On-Payroll) |
$55k–$180k+ salary + benefits |
Long runs, platform stewardship, building internal XR capability |
Ramp time, fixed overhead, retention risk in hot markets |
|
Independent Contractor |
$40–$175+/hr |
Specific features, spikes in workload, specialized tasks |
Requires clear scope and PM rigor |
|
Staff Augmentation |
$50–$160/hr |
Flexible capacity with vetted talent |
Vendor lock-in if you don’t cross-train |
|
Dedicated Near-Shore Team |
$30–$110/hr per role |
Ongoing product work aligned to your time zone |
Management overhead; ensure documentation culture |
|
Agency / Boutique Studio |
$15k–$500k+ per project |
End-to-end delivery, art + code + QA + PM |
Overhead premium; ensure code ownership & handover plan |
|
Hybrid (Core FT + Specialist Contractors) |
Mixed |
Complex roadmaps with periodic spikes |
Coordination cost; requires effective tech leadership |
Where budget meets risk: A single great senior contractor can de-risk a pilot faster than three juniors, but you must keep their hands on strategic tasks. As you approach production, blend models—an internal lead, a mid-level FT engineer, and short bursts of specialist contractors for shaders, performance, or device-specific problems.
Explore adjacent skills pipelines to complement your XR stack: Hire Apachetapestry Developers.
Cost To Hire Extended Reality Developers: Hourly Rates
Across roles and stacks, hourly rates cluster around $30–$175+, driven by engine choice (Unity/Unreal/WebXR), device targets (Quest, Vision Pro, HoloLens), and specialized techniques (shaders, CV/ML, networking).
The table below benchmarks common XR roles and the premium associated with niche skills.
Benchmarks By Role, Engine, And Skill
These ranges assume professional contractors capable of production delivery.
|
XR Focus Area |
Typical Hourly |
Notes |
|
Unity XR Engineer |
$50–$150 |
Bread-and-butter for Quest/mobile; great talent availability |
|
Unreal Engine XR Engineer |
$70–$175+ |
Often pricier; top in visual fidelity, film/games crossover |
|
WebXR / Three.js |
$45–$125 |
Strong for browser-based demos, marketing, retail try-ons |
|
Technical Artist (Shaders, Materials) |
$70–$175+ |
HLSL/GLSL mastery; performance wins on mobile headsets |
|
3D Generalist (Game-Ready Assets) |
$40–$100 |
Blender/Maya/Substance; pipeline integration matters |
|
Computer Vision / SLAM Specialist |
$85–$200+ |
OpenCV, custom ML models, depth/occlusion; niche premium |
|
iOS ARKit / Vision Pro |
$75–$180+ |
SwiftUI + RealityKit + spatial computing patterns |
|
Android ARCore |
$60–$140 |
Plane tracking, anchors, camera pipelines, JNI integrations |
|
Multiplayer/Netcode (XR) |
$70–$160 |
Latency management, authoritative servers, prediction |
|
Performance Optimization |
$80–$175+ |
GPU/CPU profiling, foveated rendering, asset budgets |
|
Platform Porting (OpenXR, Quest↔Vision Pro) |
$85–$175 |
Abstraction of input, rendering, and UX per device |
|
Hardware Integration (Sensors, Eye/Hand Tracking) |
$90–$200+ |
SDKs, calibration UX, safety constraints |
Pricing dynamics to expect:
-
Unity vs. Unreal: Unreal specialists typically charge more due to high-end rendering and film crossovers.
-
Vision Pro & HoloLens: Spatial computing expertise often commands a premium.
-
Shaders and Performance: The fastest way to save battery and win FPS—hence premium rates.
What Role Do Specializations Play In Cost?
Specialization raises price because it compresses time-to-impact—experts solve hard problems in hours rather than weeks, avoiding costly dead-ends.
When an expert owns the hardest system (render pipeline, SLAM, netcode), the entire project benefits. Budget allocation should reflect this leverage.
Which Specializations Typically Drive Premiums?
Specialties with steep learning curves or scarce supply come with higher sticker prices.
-
Rendering & Shaders: Custom HLSL/GLSL, post-processing, foveated rendering, XR-friendly material systems.
-
Computer Vision: Body/hand tracking, scene understanding, segmentation, markerless occlusion.
-
Spatial UX: Ergonomics, gaze/gesture input, comfort guidelines to avoid sim sickness.
-
Optimization: Memory budgets, draw calls, GPU profiling, streaming pipelines.
-
Networking: Multi-user state sync, prediction, lag compensation with XR input complexities.
-
Device-Specific SDKs: Deep familiarity with Vision Pro, Quest, HoloLens idiosyncrasies.
Should You Split Work Between Generalists And Specialists?
A short, targeted specialist engagement often unblocks generalists and elevates the whole codebase. Bring in expert help early for architecture and late for optimization and porting; rely on generalists for continuous feature throughput.
Are You Paying For Tools, Hardware, And Licenses Too?
Yes—beyond talent rates, plan for devices, software licenses, and testing infrastructure, which can add $2,000–$20,000+ over a project depending on scale.
Underestimating non-labor costs is a common reason XR budgets slip. Map them explicitly into your plan.
Typical Non-Labor Cost Line Items
Even if modest, these items keep quality and velocity healthy.
-
Headsets & Devices: Quest, Vision Pro, HoloLens, Pico, iPhones/iPads for ARKit—multiple units for parallel dev and QA.
-
3D Tools: Blender (free), or Maya, ZBrush, Substance subscriptions; paid asset packs for speed.
-
SDKs/Services: Analytics, crash reporting, multiplayer backends, object storage/CDN for assets.
-
Build Machines & CI: Mac minis for iOS builds, Windows rigs with strong GPUs, CI minutes.
-
Test Lab: Different headsets, controllers, and room setups to simulate real environments.
-
Compliance & Security: If you’re in regulated spaces, expect audits and pen-testing.
How Project Scope And Platform Choices Shift Budget
Expect +20–60% budget deltas when moving from single-platform to multi-platform, and +15–40% when choosing fidelity-heavy pipelines or networked features.
Platform complexity multiplies QA, performance tuning, and UX adaptation. A “simple” port is rarely simple.
Platform Scope Examples
Concrete scenarios help right-size budgets before you commit.
-
Single-Platform VR (Quest) Interactive Demo: 8–12 weeks; $30k–$90k depending on fidelity and custom art.
-
AR Product Try-On (iOS + Android): 12–16 weeks; $60k–$180k—add assets, occlusion, lighting realism, and e-commerce integration.
-
Multiplayer VR Training (Quest + PCVR): 16–28 weeks; $120k–$350k+—netcode, voice, analytics, admin dashboards.
-
Enterprise Field-Service AR (Vision Pro + HoloLens): 20–36 weeks; $200k–$600k+—hands-free flows, device MDM, offline resilience, compliance.
Should You Hire One Multidisciplinary Generalist Or A Small Team?
For anything beyond a narrow prototype, a small team outperforms a solo generalist on throughput and quality, even if the hourly bill is higher.
The time saved on context-switching and the ability to parallelize tasks outweigh the coordination cost for most production efforts.
A Minimalist Team That Scales
Start lean, then add specialists at the edges.
-
Core Duo: 1 Senior XR Engineer + 1 Mid-Level Engineer → Architecture + continuous feature delivery.
-
Add As Needed: Technical artist (shaders/perf), 3D generalist (assets), part-time PM/producer, QA.
-
For Networked Apps: Add a backend/networking engineer early to avoid rework.
What Does A Realistic XR Budget Look Like For Common Projects?
For a focused pilot, expect $30k–$120k; for production apps, $120k–$500k+, with enterprise and multi-platform builds rising further.
These templates help translate rates into end-to-end budgets you can action.
Three Practical Budget Templates
Each template gives a ballpark that you can scale up or down by swapping tiers (entry/mid/senior) and adjusting platforms.
1) Marketing-Grade AR Try-On (Single Platform, 8–12 Weeks)
-
Team: 1 Mid-Level XR Engineer, 1 3D Artist, 0.25 PM, part-time QA
-
Budget: $45k–$110k
-
Scope Drivers: Model realism, occlusion quality, lighting/IBL, analytics, e-commerce hooks.
2) Training Simulation In VR (Single Platform, 12–16 Weeks)
-
Team: 1 Senior + 1 Mid-Level XR Engineer, Technical Artist (part-time), 3D Artist, QA
-
Budget: $90k–$220k
-
Scope Drivers: Interaction depth, scoring/assessments, narrative content, performance on mobile hardware.
3) Multi-User Spatial Collaboration (Two Platforms, 16–28 Weeks)
-
Team: 1 Senior XR Engineer, 1 Mid-Level XR Engineer, Backend/Netcode, Tech Artist, 3D Artist, PM, QA
-
Budget: $180k–$450k+
-
Scope Drivers: Voice/video, persistence, cross-device state sync, admin tools, analytics dashboards.
How To Reduce Costs Without Sacrificing Quality?
Focus on scope clarity, asset reuse, and early performance targets. A lean roadmap paired with decisive reviews avoids the most expensive trap—rebuilding late.
These tactics preserve quality while trimming burn.
Practical Cost-Savvy Tactics
-
Scope In “Slices,” Not Towers: Ship narrow, end-to-end user journeys first; iterate vs. boiling the ocean.
-
Performance Budgets Early: Lock draw calls, frame time, and texture budgets from the first sprint.
-
Reuse Assets: Leverage best-in-class paid packs and customize—a 70% fit you polish beats a 0% fit you build from scratch.
-
Automate Builds & Tests: CI, smoke tests, and device farms catch regressions that otherwise burn man-weeks.
-
Platform Abstraction: Use input/rendering layers that ease future ports (OpenXR where sensible).
Contracts, IP, And Compliance: What Costs Hide In The Fine Print?
Beyond rates, IP assignment, licensing, and compliance workflows can add $2k–$25k+ depending on your domain.
Budget a little legal foresight now to avoid a lot of legal hindsight later.
Essentials That Protect Your Budget
-
IP & Asset Rights: Ensure source code, shaders, and custom assets transfer to you; validate any third-party asset licenses.
-
Security & Privacy: If recording spatial data or biometrics (gaze/hand/voice), bake privacy standards into your SOW.
-
Maintenance Windows: Negotiate post-launch support (bug-fix allotments) rather than ad-hoc emergency premiums.
-
Source Control & Handover: Repos, build scripts, credentials, and documentation must be contractually deliverable.
Time-To-Hire And Availability: Why It Affects Price
Scarcity drives price: when you need a device-specific specialist on short notice, expect a premium or a wait.
The more lead time and flexibility you offer, the easier it is to secure top talent without rush rates.
Planning For Availability
-
Recruit Early: Line up experts for architecture reviews and key feature spikes.
-
Book Testing Windows: Hardware constraints mean QA calendars fill up fast; schedule device lab time ahead.
-
Set Decision Cadence: Weekly reviews unblock teams and retain contractors who value predictability.
Platform & Engine Choices: Do They Lock In Your Cost Curve?
Engine and platform shape your talent pool and long-term costs—choose with a clear view of content fidelity, platform reach, and performance envelopes.
Picking the right foundation avoids fighting the toolset.
Quick Guidance For Common Choices
-
Unity: Best availability, strong mobile/Quest; great for time-to-market.
-
Unreal: Higher visual ceiling, film/games expertise; pricier but priceless for realism.
-
WebXR: Frictionless distribution; ideal for marketing and lightweight interactions.
-
OpenXR: Helpful for device portability; ensure you still budget for platform-specific polish.
Team Composition: What’s The Most Cost-Effective Mix?
For sustained progress, 1 Senior + 1 Mid-Level + part-time Tech Artist hits a sweet spot.
Add a 3D generalist and QA as scope grows; pull a computer-vision or networking specialist for spikes rather than carrying them full-time.
A Phased Team Plan
-
Phase 1 (Prototype): 1 Mid-Level, part-time Senior consultation → keep costs low while validating fit.
-
Phase 2 (Build): Add Senior hands-on, Tech Artist part-time, 3D generalist → accelerate delivery.
-
Phase 3 (Polish & Port): Engage specialists (perf, shaders, CV) in short bursts → hit frame targets and QA gates.
Vendor Versus In-House: Which Path Protects Your Budget?
Use vendors for speed and breadth; build in-house for continuity and ownership.
Often the best path is staged: vendor for initial lift, then transition core ownership to your internal team.
A Practical Transition Plan
-
Co-Build: Insist on pair-programming, shared repos, and documentation.
-
Shadowing: Your future in-house owner shadows critical systems (rendering, networking).
-
Handover Sprint: Plan a 2–3 week period solely for knowledge transfer, bug triage, and build hardening.
Common Pricing Pitfalls And How To Avoid Them
Most overruns trace back to undefined scope, late performance fixes, or multi-platform ambitions added mid-stream.
Naming these pitfalls upfront is the cheapest way to avoid them.
Red Flags To Watch
-
“We’ll optimize later.” Later turns out to be expensive; set budgets early.
-
“Porting will be easy.” Device nuances multiply QA—budget for it.
-
“Design as we build.” Discovery is fine; just separate it from fixed-price delivery.
Sample Statements Of Work (SOW) Language That Saves Money
Clear SOW language aligns expectations and prevents debate under deadline.
Borrow these patterns to keep scope crisp.
Clauses That Protect Scope
-
Performance Targets: “Sustained 72–90 FPS on device X under scene Y with N dynamic lights.”
-
Asset Budgets: “Textures ≤ 512 MB at runtime; draw calls ≤ 2,000 per scene.”
-
Definition Of Done: “Device QA pass on Quest 3 and Vision Pro, with acceptance criteria in Appendix A.”
How Do Testing And QA Affect Costs?
Plan 10–25% of project budget for systematic QA across devices, room setups, and lighting conditions. Spatial computing multiplies test variables—motion, occlusion, reflectivity—so don’t undercut QA.
Smart QA Investments
-
Test Matrices: Device × Scene × Lighting × Interaction combos.
-
Automated Smoke Tests: Build verification on every merge, sanity checks for perf and input mappings.
-
Beta Programs: Early external users surface edge cases that in-house QA won’t encounter.
Are Milestones Or Retainers Better For Budget Control?
Milestones are great for fixed scope; retainers support ongoing product health and live ops.
Choose based on whether your XR app is a campaign or a platform.
Blended Approach That Works
-
Milestone 1: Prototype with acceptance criteria.
-
Milestone 2: Production feature pack.
-
Retainer: 20–40 hrs/month for maintenance, platform updates, and device support.
What Do Training And Documentation Add To Cost?
Allocate $1,500–$10,000 for internal training, dev handbooks, and recorded walkthroughs; it’s cheap insurance for long-term maintainability.
These artifacts prevent knowledge loss and reduce reliance on any single contributor.
High-Leverage Artifacts
-
Setup Guides: One-click environments, asset import rules, build profiles.
-
Runbooks: Performance troubleshooting, shader/material conventions, profiling steps.
-
Architecture Maps: Input abstraction, scene management, networking topology.
How Do You Compare Proposals Apples-To-Apples?
Normalize proposals on scope, deliverables, platforms, and performance targets before comparing hourly.
A low quote with vague deliverables is more expensive than a high quote with sharp acceptance criteria.
A Simple Comparison Checklist
-
Platforms, devices, and acceptance tests listed?
-
Asset creation included or client-provided?
-
Post-launch support window specified?
-
Source code/IP transfer explicit?
-
Performance budgets measurable?
How Do You Keep Budgets Predictable After Launch?
Post-launch, reserve a maintenance and feature envelope (5–15% of initial build per quarter) to keep pace with device updates and OS changes.
XR platforms evolve quickly; a small, steady budget beats emergency fixes later.
What’s In The Envelope
-
Platform Updates: SDK bumps, breaking changes, input mapping shifts.
-
Perf Regression Fixes: Asset churn over time needs re-optimization.
-
Small Features: Iterative UX improvements based on analytics.
FAQs About Cost of Hiring Extended Reality Developers
1. How Much Should I Pay An XR Developer Per Hour?
Entry-level rates often land $25–$60/hr, mid-level $60–$100/hr, senior $100–$175+/hr, with specialists occasionally higher for niche tasks.
2. What’s A Reasonable Budget For A Small AR Pilot?
A focused single-platform pilot typically ranges $30k–$90k, depending on asset realism, occlusion, and analytics.
3. Which Is Cheaper: Unity Or Unreal?
Unity developers are generally cheaper and more plentiful; Unreal developers often cost more but can deliver superior visual fidelity for certain use cases.
4. Do I Need A Technical Artist?
If you care about frame rate, visual quality, and battery life, a part-time technical artist is one of the highest-ROI roles you can add.
5. How Do I Reduce Costs Without Losing Quality?
Lock performance budgets early, reuse assets wisely, keep scope narrow for first release, and bring in specialists for the trickiest parts.
6. Should I Hire In-House Or Use A Studio?
If you’re building a platform or long-term product, seed an in-house team and supplement with specialists. For campaigns or one-offs, studios are faster to assemble.
7. Are WebXR Projects Cheaper?
Often yes—no app store friction and simpler distribution—but you’ll trade off some device-level capabilities and raw performance.
8. Why Do Vision Pro Or HoloLens Projects Cost More?
Spatial computing on these devices often involves specialized UX, precise performance targets, and occasional enterprise compliance, which raises effort.
Don’t forget devices, licenses, QA time, and post-launch updates. Reserve 10–25% for QA and 5–15% per quarter for maintenance.
10. Can I Combine Marketing And Training Use Cases In One App?
Yes, but expect scope creep. Plan separate modules and acceptance criteria so each use case gets the right performance and UX.