Skip to main content

AR in Everyday UX: Practical Applications Beyond Demos

Augmented reality has moved past the novelty phase. The impressive demos are no longer the point — what matters now is where AR genuinely improves a workflow compared to a standard screen-based interface. This guide focuses on practical AR applications, the UX patterns that make them work, and how to evaluate whether AR is the right choice for your product.

Last updated: 16 March 2026

When AR is the right choice (and when it isn't)​

AR adds a layer of digital information to the physical world. That's only useful when the physical context matters. Ask these questions before committing to an AR feature:

Is spatial context essential? If the user needs to understand how something fits in a physical space (furniture placement, wiring routes, navigation overlays), AR adds genuine value.

Is the task hands-busy? AR with voice or gaze input can keep workers' hands free for physical tasks (maintenance, surgery, assembly).

Would 2D be simpler? If the information can be presented effectively in a flat list, map, or diagram, a screen is faster and cheaper to build. Don't use AR for tasks that are fundamentally tabular.

Everyday AR use cases that work​

  • Measurement and layout. Verifying physical dimensions, spacing, and alignment — similar to what Linear does on screen, but mapped to physical objects.
  • Wayfinding. Indoor navigation overlays in airports, hospitals, and warehouses.
  • Remote assistance. A technician sees annotations overlaid on the equipment they're servicing, placed by a remote expert.
  • Contextual documentation. Point at a machine or component to see its manual, maintenance history, or specs.
  • Try-before-you-buy. Previewing furniture, paint colours, or accessories in situ.

Designing AR overlays that don't overwhelm​

The most common failure in AR UX is information overload. The physical world is already visually complex — adding too many labels, icons, and panels creates chaos.

Depth-based filtering​

Show more detail for nearby objects, less for distant ones. If a user is standing near a circuit breaker panel, show detailed labels. The panel across the room gets a simple icon.

Progressive disclosure in 3D​

Start with minimal overlays — status indicators, directional cues. Let users tap, gaze-dwell, or say "more info" to expand. This is the 3D equivalent of the progressive disclosure patterns used in onboarding flows.

Spatial anchoring​

Overlays must stay anchored to physical objects as the user moves. Drifting labels destroy trust and usefulness. Budget development time for robust tracking and always test in varied lighting.

The 3-second rule

If a user can't understand the purpose of an AR overlay within three seconds of seeing it, the overlay is either too complex or poorly placed. Simplify the default state and let users pull in detail on demand.

Input patterns for AR​

AR input depends heavily on hardware. Design for the capabilities your target device supports:

Mobile AR (phone/tablet)​

Input is mostly touch (on the screen) plus device position/orientation. Use tap-to-place, drag-to-move, and pinch-to-scale gestures. Ensure touch targets are large enough — see the accessibility checklist for minimum sizing.

Head-mounted AR (glasses, headsets)​

Input modes include gaze, hand gesture, voice, and external controllers. Gaze-dwell (look at something for 1–2 seconds to select it) is the most universal but slowest. Combine gaze-to-aim with voice-to-act for faster interactions. This connects to the multimodal patterns described throughout our UX guides.

Projection-based AR​

No wearable device — visuals are projected onto surfaces. Input typically uses physical gestures captured by cameras. Provide generous tolerances and clear visual feedback.

Typography and readability in AR​

Text in AR has to contend with unpredictable backgrounds. Standard web typography assumptions don't apply:

  • High-contrast containers. Always place text on a semi-opaque panel, never directly on the camera feed. A dark or frosted panel with white text is the safest default.
  • Minimum text size. 16sp equivalent at reading distance. Smaller text becomes illegible against busy backgrounds.
  • Limited text length. If you need more than two lines, consider audio narration or linking to a full-screen detail view.
  • Avoid thin fonts. Medium or bold weights survive better against varied backgrounds.

These considerations align with general CSS sizing and spacing principles — the goal is legibility at any scale.

Performance and battery​

AR features are computationally expensive. Camera processing, object detection, and 3D rendering drain batteries and generate heat. Performance directly affects UX because:

  • Frame rate drops below 30 fps cause nausea in head-mounted AR.
  • Excessive battery drain makes users disable the feature.
  • Thermal throttling degrades tracking quality over time.

Apply the same performance-conscious design thinking from the performance for designers guide: reduce unnecessary rendering, lazy-load overlays, and give users a way to exit AR cleanly.

Testing AR experiences​

You can't fully test AR at a desk. Plan for on-site testing in realistic environments:

  1. Varied lighting. Test in bright daylight, fluorescent indoor light, and dim conditions. Tracking quality varies dramatically.
  2. Different surfaces. Featureless walls, reflective floors, and cluttered spaces all challenge AR.
  3. Movement. Test while walking, turning, and bending. Static testing misses most tracking failures.
  4. Extended sessions. Ask participants to use the AR feature for 15+ minutes to uncover fatigue and thermal issues.

Use your standard usability testing framework but add spatial observation: where does the participant physically move? Do they bump into things? Do they lose the overlay?

Common mistakes​

Using AR for information that's better as a list. Inventory counts, status tables, and form data don't belong in AR. Use screens.

Assuming perfect tracking. Real-world tracking breaks in sunlight, on featureless surfaces, and at extreme angles. Design for degraded tracking, not just perfect conditions.

Ignoring physical safety. Users looking through a screen or headset aren't fully aware of their surroundings. Add warnings, reduce walking-while-viewing, and keep sessions short.

Over-decorating overlays. Shadows, glows, and animated borders look great in screenshots but clutter the view in practice. Keep overlays minimal.

Not providing a non-AR fallback. Some environments simply won't work with AR. Always offer a 2D alternative.

Checklist​

Related Resources