# Spatial Computing App Onboarding: Teach AR Gently

> By Lawrence Arya, Founder & CEO of VP0. Published 2026-05-31, updated 2026-06-02. 4 min read.
> Source: https://vp0.com/blogs/spatial-computing-ios-app-onboarding-ui

Spatial computing breaks the flat-screen rules users know: onboard them gently, one new concept at a time, with comfort first.

**TL;DR.** Spatial and AR onboarding has to teach an unfamiliar paradigm: new gestures (look, pinch, drag in space), permissions (camera, space), and comfort. Build it from a free VP0 design that introduces one concept at a time, uses a coaching overlay for AR tracking, sets clear expectations, and respects physical comfort and the room. Keep sessions short, give a 2D fallback, and never overwhelm. Teach gently, and the magic lands.

Spatial and AR features break the flat-screen rules users have known for years, so onboarding has to teach a new paradigm gently. The short answer: build it from a free VP0 design that introduces one concept at a time, gestures, permissions, comfort, uses a coaching overlay for AR tracking, sets clear expectations, and respects the user's physical comfort and space. Keep it short and never overwhelm. The space is expanding fast, the AR and VR market is projected past [$50](https://www.statista.com/) billion, but adoption depends on onboarding that does not lose people.

## Teach one new thing at a time

Spatial computing asks users to learn unfamiliar interactions, looking to target, pinching to select, dragging objects in space, and to grant new permissions (camera, and an understanding of their room). Throwing all of that at them at once overwhelms. So introduce one concept at a time, let them try it, and confirm success before moving on. For AR on the phone, use the system coaching overlay to guide tracking ("move your phone to scan the area"), and set expectations about lighting and space. Above all, respect comfort, do not force long sessions, sudden motion, or actions that require an impractical amount of physical space. Apple's [Human Interface Guidelines for visionOS](https://developer.apple.com/design/human-interface-guidelines/designing-for-visionos) and its [augmented reality guidance](https://developer.apple.com/augmented-reality/) stress gentle, comfort-first onboarding.

## Build it from a free design

VP0 is a free iOS design library for AI builders. Pick onboarding and instructional designs, copy their links, and have Cursor or Claude Code rebuild them in SwiftUI, then sequence the spatial concepts. Introduce each gesture with a short, clear prompt and a chance to practice. Request permissions in context with plain reasons. Use the coaching overlay for AR tracking, and design a graceful state for when tracking fails or the space is too small, including a 2D fallback so no one is stuck. Keep early sessions short and comfortable. For the AR build foundations, see [visionOS mobile companion app template](/blogs/visionos-mobile-companion-app-template/), and for onboarding fundamentals, see [iOS onboarding screen design that actually converts](/blogs/ios-onboarding-screen-design-that-actually-converts/).

## Spatial onboarding building blocks

Introduce each gently, in order.

| Step | Teach | Comfort rule |
|---|---|---|
| Gestures | Look, pinch, drag in space | One at a time, let them try |
| Permissions | Camera, space understanding | In context, plain reasons |
| Tracking | Scan the area | Coaching overlay, clear prompts |
| Expectations | Lighting, space needed | Set up front, honestly |
| Fallback | When AR cannot run | A working 2D experience |

## Common mistakes

The first mistake is dumping every new gesture and concept on the user at once. The second is no coaching overlay, so AR tracking just looks broken. The third is ignoring comfort, long sessions, sudden motion, or needing a huge space. The fourth is no 2D fallback when AR cannot run, stranding users. The fifth is not setting expectations about lighting and space, leading to frustration. Teach one thing at a time, comfortably, with a fallback.

## A worked example

Say you add AR features to your app. Your VP0-built onboarding introduces the first gesture with a short prompt and a practice step, then requests camera permission in context. A coaching overlay guides the user to scan their space, with clear expectations about lighting. If tracking fails or the room is too small, a friendly message offers a 2D version so they are never stuck. Sessions stay short and comfortable, and each new concept arrives only after the last one clicks. For the iPad adaptive-layout cousin that closes this set, see [iPadOS Stage Manager UI layout template](/blogs/ipados-stage-manager-ui-layout-template/), and for the AI build loop, see [how to build an iOS app with AI](/blogs/how-to-build-an-ios-app-with-ai/).

## Key takeaways

- Spatial and AR onboarding must teach an unfamiliar paradigm gently.
- Build it from a free VP0 design and introduce one concept at a time.
- Use the system coaching overlay for AR tracking and set clear expectations.
- Respect comfort: short sessions, no sudden motion, reasonable space needs.
- Always provide a 2D fallback so users are never stranded when AR cannot run.

## Frequently asked questions

How do I onboard users to spatial or AR features? Build onboarding from a free VP0 design that teaches one new gesture or concept at a time with practice, requests permissions in context, uses a coaching overlay for tracking, and sets clear expectations.

Why introduce spatial concepts one at a time? Because the interactions (look, pinch, drag in space) and permissions are unfamiliar. Teaching them gradually, with a chance to practice each, prevents overwhelming the user.

What if AR tracking fails or the space is too small? Design a graceful fallback: a friendly message and a working 2D version of the experience, so users are never stuck when conditions do not allow AR.

How do I respect comfort in spatial onboarding? Keep early sessions short, avoid sudden motion, do not require an impractical amount of physical space, and set expectations about lighting and room up front.

## Frequently asked questions

### How do I onboard users to spatial or AR features?

Build onboarding from a free VP0 design that teaches one new gesture or concept at a time with practice, requests permissions in context, uses a coaching overlay for tracking, and sets clear expectations.

### Why introduce spatial concepts one at a time?

Because the interactions (look, pinch, drag in space) and permissions are unfamiliar. Teaching them gradually, with a chance to practice each, prevents overwhelming the user.

### What if AR tracking fails or the space is too small?

Design a graceful fallback: a friendly message and a working 2D version of the experience, so users are never stuck when conditions do not allow AR.

### How do I respect comfort in spatial onboarding?

Keep early sessions short, avoid sudden motion, do not require an impractical amount of physical space, and set expectations about lighting and room up front.

---
*Published on the [VP0 Journal](https://vp0.com/blogs). Free to read, index and cite with attribution.*