# XR Midterm: Deep-Dive Study Guide

An introductory, exam-focused guide to the topics named in the Fall 2026 midterm study guide. It assumes no prior review. The course slides are the authority for course-specific terms and examples; the reading notes below paraphrase the assigned sections of *UX for XR*.

## How to use this guide

1. Start with the mental models and diagrams.
2. Read the explanations; say the bold terms back in your own words.
3. Close the guide and try the prompts at the end of each section.
4. Finish with the cram sheet, cards, and 35-question practice midterm on the companion website.

## 1. XR as a medium, a product, and a user experience

### What XR changes

**Extended reality (XR)** covers experiences that combine or replace physical and digital perception. **Augmented reality (AR)** adds digital content to a view of the physical world; **virtual reality (VR)** places the user in a primarily virtual environment; **mixed reality (MR)** makes digital content spatially situated and responsive to the real environment. In the Week 3 slides, all three device examples (Snap Specs, Meta Quest, Apple Vision Pro) can show AR content, but they achieve it differently.

XR is not just a screen with a new shape. It adds depth, scale, distance, body movement, gaze, hand gestures, sound direction, and the user's actual surroundings to the design problem. The same content therefore cannot always be copied unchanged from phone to headset.

```text
Physical world ── AR overlay ── MR interaction ── immersive VR
      visible       visible       visible + sensed     replaced
```

The first iPhone was revolutionary but evolutionary: phones already existed and people understood the basic device. XR lacks an equally universal mainstream predecessor. That helps explain why XR has long been framed as the “future present”: its potential is repeatedly anticipated, but adoption depends on usable products, familiar value, comfort, and compelling content. The course summary emphasizes this skepticism and the importance of integrating XR into real situations rather than assuming that novelty alone will sustain use.

### XR as a product needs a lifestyle

A device succeeds more easily when it fits into a repeatable **lifestyle or ecosystem**: existing habits, useful touchpoints, content, creators, and services. The Week 5 lecture examples are:

- Apple Watch became more useful through its relationship with iPhone.
- Snapchat AR lenses fit a camera-centered messaging habit.
- iPhone and untethered Meta Quest helped create new usage patterns.
- A technically capable product can struggle if it does not become a natural touchpoint (the lecture uses Alexa ordering as a cautionary example).

Think beyond “What can the device do?” Ask: “Who needs it, what activity does it improve, how does it fit into a day, and what makes people return?”

### User experience (UX) is larger than user interface (UI)

**UX** is the whole experience of using a product or service: expectations, setup, comfort, learning, task flow, feedback, social context, and what happens before and after the screen. **UI** is one mechanism through which UX is expressed. A good interface supports a coherent experience; it is not the experience by itself.

The Week 6 UX indicators are practical: the product “just makes sense,” supports a flow, offers options when needed, is easier than expected, and makes digital actions feel consistent with familiar real-world actions. The interface can become nearly invisible when the experience is intuitive.

**Internet of Things (IoT)** products show how connected technology can shift equipment from something a user must constantly master into something that senses context and personalizes itself. The lecture examples include smart cars and home appliances. XR designers can apply the same idea: technology should respond appropriately to the person and situation, rather than requiring the person to adapt to technical machinery.

## 2. Week 2: AR in products and the XR “future present”

The Week 2 examples show AR embedded in ordinary products, tasks, and places:

- **Measurement and planning:** phone-based measurement/AR planning tools place dimensions or layouts into a real scene.
- **Outdoor identification:** an AR mountain-identification app labels peaks in the camera view.
- **Astronomy:** Star Walk 2 overlays celestial information when pointed at the night sky.
- **Vehicle navigation and heads-up displays (HUDs):** guidance is aligned with the road or pilot's view, keeping relevant information in the visual context of the task.
- **Themed entertainment:** the Mario Kart ride at Universal Studios layers visual scope and gamification into a physical attraction.
- Earlier course examples include retail/product try-ons, IKEA furniture placement, LEGO product previews, AR service manuals, and warehouse logistics.

These examples work because the digital layer is related to a physical target or task. AR can make information contextual, spatial, and easier to interpret than a separate list or flat diagram. It is often a casual, solution-focused extension of a real activity rather than a fully immersive escape.

### Summary of XR as medium and product

The course's Week 2 summary makes three linked points:

1. XR has been imagined as a future mode of computing for a long time.
2. The consumer is still learning how to use it; unlike the phone, XR has no familiar mass-market predecessor.
3. Adoption therefore depends on translating technical possibility into clear, useful, socially acceptable experiences, not just announcing a futuristic device.

## 3. Week 3: devices, platforms, and AR as a language

### Device categories (the lecture's late-2020s framing)

| Category | Typical setting and role | Design implication |
|---|---|---|
| Lightweight glasses | On the go; all-day information companion | Keep interactions brief, glanceable, socially comfortable, and useful in context. |
| Medium-weight spatial glasses | On the go, home, or office; interactive “visual headphones” | Support richer interaction while preserving environmental awareness. |
| Heavy headset | Home or office; focused, shorter sessions | Make immersion worthwhile; prioritize comfort, onboarding, space, and safe use. |

The exact product landscape changes, but the design trade-off remains: mobility and social ease versus display capability, immersion, and compute.

### Product narratives and market roles

The slides compare organizations by the role they seek in people's lives: Meta's social network and business connections (including advertising/data); Google's Android/personal-device and connectivity position; and Apple's integrated computing ecosystem and high-end experience/entertainment position. The deck also discusses Snap's community-oriented Spectacles. Google + Samsung and Google + Xreal are examples of device/platform partnerships.

The lecture's timeline records Apple Vision Pro's reveal (June 2023) and store release (February 2024), Quest 3 and Ray-Ban Meta launches (October 2023), Snap's Specs developer release (September 2024), and Microsoft's exit from XR hardware (October 2024). Its later timeline labels SharePlay on Vision Pro, Meta Display, brand/device partnerships, and expanded developer camera access under 2025; it lists audio/mono-display glasses, Galaxy XR, and Snap Specs under 2026; and it presents Orion, Quest 4, and Puffin as 2027 possibilities. Learn these as dated lecture-slide claims/predictions; do not confuse the slide's forecast language with a timeless product fact.

### Two kinds of VR experiences (Week 3, p. 49)

- **360-degree video VR** can look quasi-photorealistic because it is captured video, but typically gives the user little or no ability to interact with the scene.
- **Realtime interactive VR apps/games** respond to user actions, but the device must render them live; the visual style is often more stylized and may look less photorealistic.

This is a trade-off between captured visual fidelity and real-time agency. Do not confuse “looks realistic” with “is interactive.”

### AR/MR and the physical-world ratio (Week 3, p. 52)

AR/MR foreground the physical setting: visuals overlay physical objects and respond to environmental changes. They are usually interactive and often combine interface-like controls with playful visual feedback. The lecture's rule of thumb is that about **80% of what the user sees should remain the physical world**. Sensors can let digital objects respond to physical objects and the user's actions; tools in the environment can become part of the interaction. This keeps the experience grounded rather than turning AR into a small, obstructive virtual world.

### Every AR experience has a structure

The Week 3 slides define a basic AR experience as:

1. a **physical-world target**,
2. **visuals that reference and augment** that target, and
3. a **sequence of events**.

For an interactive experience, add an interactable surface (physical or virtual), goals, and rewards. An alternate fine-arts approach may use a “theater mode” anchored to a surface. The course also frames AR as an unnamed capability people experience as “something my device can do,” not always as a technology label.

## 4. Week 4: core AR scene concepts

An AR scene is not merely a 3D object placed in a camera view. It combines a reference to the world, spatial layers, visual integration, sensing, interaction, sequencing, and an exit.

### Concept 1 — World reference / anchor

An **anchor** (sometimes called a **target**) gives the AR system a reference for where and when to place content. The content should appear in the right relation to the intended thing.

| Anchor/target | Example from the lecture |
|---|---|
| Surface | A floating or diorama-style scene placed on a table or floor. |
| Face | A selfie filter tracks a face. |
| Image/marker | A graphic novel recognizes a page image and launches that page's content. |
| 3D object | A Merge Cube or product configurator recognizes a 3D object and attaches content to it. |

The question to ask in design is: “What in the real world tells the system where this content belongs?”

### Concept 2 — World space and screen space

- **World space** is content positioned in the 3D environment; it remains related to a place or object as the camera/viewpoint moves.
- **Screen space** is the 2D interface attached to the device display, such as buttons or status controls.

Mobile AR creation must blend a 2D touchscreen/control surface with a 3D camera view. Separating these spaces makes the device function like a controller: screen controls can operate the world-anchored content. Headsets still have the distinction, but their interface is itself virtual and spatial. A good design makes clear which elements are “in my room” and which are “on my device.”

### Concept 3 — Occlusion and optical realism

**Occlusion** is the correct visual blocking/order of real and virtual objects. If a real table is in front of a virtual object, the table should hide the part behind it. If a virtual object is supposed to sit behind a real object but is always drawn on top, the illusion and interaction become confusing.

AR objects also need plausible optical cues: placement, scale, lighting, shadows, and depth. These cues help users understand whether an object is on a surface, attached to it, floating, or behind something. Occlusion is not decorative polish; it communicates spatial relationships.

### Concept 4 — Event-based interaction

AR behavior can be described as **trigger → event → response**:

```text
Something is sensed or done       The system recognizes it       Content changes
trigger (tap, gaze, image,         event (condition is met)       response (show,
proximity, gesture, tracking)                                    animate, play, etc.)
```

Behavior scripts connect triggers/events to responses. A trigger might be a tap or recognized image; a response could be an animation, sound, change in visibility, or next action. Computer vision and machine learning can help detect faces, hands, objects, or environmental conditions. Good feedback makes it apparent that the system noticed the user.

### Concept 5 — Scene and sequencing

A **scene** comprises its objects, anchoring, sensing and interaction methods, animation (including object-to-object animation), and exit. When launched, its objects load and scripts become ready. One experience can contain multiple scenes; code can sequence forward or allow a return loop. Plan the whole journey, not just the opening view.

### Under the hood

The Week 4 Apple example distinguishes:

- **ARKit**: reads/senses the environment and provides tracking/understanding capabilities.
- **RealityKit**: integrates 3D objects and their interactions with the real-world space.
- **API**: an application programming interface, a defined way for software components/frameworks to exchange data and capabilities.

Spatial content is expressed as 3D objects. Even a 2D image must be placed on a 3D surface (texture-mapped) to inhabit spatial design.

## 5. Week 4: advanced AR features (AR 3.0)

These capabilities help a brand or product move from a one-off overlay toward a persistent, location-aware, interactive relationship with a place or object.

### Persistence

**Persistence** lets an AR placement remain associated with a real-world location beyond one moment or one user's session. The slides use Niantic's **Visual Positioning System (VPS)** example: people can place an object at a real-world location, return to it later, or encounter the same object from different viewpoints. This supports shared, repeatable experiences rather than a disposable effect.

### Precise positioning: depth cameras, SLAM, and VPS

- **Depth cameras** estimate distances and scene geometry.
- **SLAM** means simultaneous localization and mapping: the system maps its surroundings while estimating its own position within that map.
- **VPS** uses visual/location information to position content accurately in the wider world.

Together, these capabilities improve reliable placement and alignment. Better positioning makes product scale, spatial storytelling, and persistent placement more convincing.

### Absolute scale

**Absolute scale** represents a product at its intended real-world size, rather than an arbitrary size that changes with the screen. The Week 4 example is a vehicle configurator: true size helps people judge whether the object fits, how large it is, and how it relates to the surrounding space. This is valuable when size is part of the purchase or use decision.

### Real-world colliders

A **collider** is a boundary used to detect contact/overlap. With real-world collision features, sensed physical objects can participate in AR interactions: the virtual object may stop at a wall, bounce from a surface, or otherwise respond to a real obstacle. The physical environment becomes an interactive part of the scene.

### Why these features matter to brands

They let a brand demonstrate a product in the user's own context, make its physical dimensions understandable, connect content to a place, and create repeat visits or shared discovery. That can make a product feel like it belongs in the user's physical world (a “phygital” experience). The features are only useful when they improve a real customer task or experience.

## 6. Week 5: Vision Pro content, developer ecosystems, and device comparisons

### Five Vision Pro content patterns

The study guide asks for at least three; learn the full set:

1. **Windowed apps** — spatial “laptop mode”: conventional app windows positioned around the user.
2. **Full Space apps/games** — an experience expands from mixed reality toward full VR immersion.
3. **Apple Immersive Video** — 360-degree, 3D video designed for full immersion; the user is not visible in the scene as themselves.
4. **Multi-app use in bounded volumes** — several apps/content areas coexist in spatially limited regions.
5. **Pop-in/pop-out transitions** — a 3D object or spatial video can begin inside a window, expand into a volume/immersive mode, and return.

Related terms: a **window** is a flat app panel; a **volume** is a bounded 3D region; a **portal** can connect the user’s view to another space. These compositions can be mixed in mixed-reality or full-immersion modes.

### The creator base and development tools

An XR platform needs a supply of creators and usable development paths. The slide titled “Securing Creator Bases” is followed by this VisionOS tool map:

- **Native**: Xcode and Reality Composer Pro.
- **Other realtime engines**: Unity with PolySpatial SDK; Godot SDK.
- **Device-agnostic/WebXR**: examples include A-Frame and three.js; experiences run in Safari on visionOS.

The strategic point is to lower creators' adoption cost by supporting established workflows, not forcing every developer to start from zero. A wider tool ecosystem can increase the amount and range of available content, which in turn makes the platform more useful. Tool choice still affects capability, performance, and portability.

### Innovation in developer tools

The deck connects tool innovation with capabilities such as:

- a virtual display that mirrors a laptop screen as a floating window,
- real-world object collision (compared with Niantic's collision feature),
- device intelligence that scales an experience to the space available, and
- voice and hand input.

These examples show how a spatial tool can use the room, device sensors, and familiar inputs—not only place a 3D object in front of a camera.

### Specs vs. Quest and Vision Pro

The lecture compares **Snap Specs** as on-the-go, optical AR glasses with **Meta Quest** and **Apple Vision Pro** as pass-through headsets (in the lecture's device examples). All can provide mixed-reality/AR visuals, but the view of the physical world differs:

| | Snap Specs (lecture example) | Meta Quest / Apple Vision Pro (lecture examples) |
|---|---|---|
| View | **Optical see-through** lenses: user looks directly through lenses at the real world. | **Video pass-through**: cameras show the real world on small displays inside the headset. |
| Main design narrative | On-the-go companion; expands immediate surroundings in playful and useful ways; strong community orientation. | Living-room/workplace spatial computing: larger virtual screens, immersive apps, games, collaboration. |
| Feel and context | Optical view can feel less like entering an artificial world; brightness adapts to surroundings. | More capable, enclosed visual experience; comfort, fit, safe space, and focused-use duration matter. |

Do not treat “optical” and “pass-through” as synonyms. With optical see-through, light from the real environment reaches the eye through the lens; with video pass-through, the user sees a camera-mediated image of the room.

## 7. Week 6: UX for XR

### UX influences: mobile and games

XR borrows from two large interaction traditions:

| Mobile conventions | Game conventions | XR combinations |
|---|---|---|
| Icons, flat buttons, menus, trays, highlights; tap, scroll, pinch, zoom, long-press; voice input. | Mouse/keyboard, WASD, D-pad, joysticks, inventories; physics and tactile interaction; two-hand or button combinations. | Gaze, hands, voice, gestures, body tracking, spatial UI, and ambient sensing. |

Mobile design emphasizes quick, familiar, efficient access to information. Games emphasize physicality, simulated physics, and tactile involvement. XR can blend the two: e.g., both hands pull/scale an object while a familiar finger gesture selects a spatial control.

### Active vs. ambient inputs

- **Active input** is an intentional command: gaze selection, pinch/tap, hand gesture, voice command, or typed text.
- **Passive/ambient input** is sensed context/activity that may influence the experience without a direct command—for example, AI glasses sensing environment or activity through machine learning.

Input must be legible and respectful: a person should know what the device is sensing and how to control it.

### Rich experiences: course definitions

The Week 6 slide visibly lists **five** terms, even though the midterm study-guide wording says “four attributes.” Learn all five to avoid omitting one the instructor expects:

| Attribute | Meaning |
|---|---|
| **Immersive** | Engages the senses enough to limit distractions and create a feeling of presence. |
| **Experiential** | Feels out of the ordinary; can create positive presence, reconnect users with their bodies, and increase environmental awareness. |
| **Engaging** | Interactive and capable of creating memories. |
| **Narrative** | Clearly demonstrates purpose and drives progression. |
| **Spatial** | Connects to the user's physical environment through context or movement/locomotion. |

Distinguish them in an example: a museum AR guide can be immersive through spatial audio and focused visuals, experiential by making a historical scene feel newly present, engaging through visitor choices, narrative through a clear progression, and spatial by aligning content to actual exhibits.

### Promising XR markets from the lecture

1. **Travel and recreation** — guidance, context, live translation, and enhanced adventure.
2. **Personalized sports** — tailored, contextual training or spectator experiences.
3. **Movies and games** — new immersive storytelling and AR “second-screen” extensions.
4. **Location-based entertainment** — theme parks, museums, walkable exhibits, and surround-screen venues.
5. **Physical health and intervention** — assessments, physical therapy, surgery, and therapy through embodied experiences.
6. **Remote work and collaboration** — spatial meetings, shared displays, and collaborative design.
7. **Experiential marketing** — pop-up stores and activations, such as a walkable fragrance experience.

The design task is to identify the audience and meaningful outcome, then deliberately include the experiential qualities above—not simply add XR because a market sounds promising.

## 8. Week 7: experience arc, rewards, and avatars

### Six stages of a curated experience

```text
Anticipation → Onboarding → Doing → Transition → Completing → Reflection
                    ↑           └─ core loop ─┘
```

1. **Anticipation** — set expectations and give a reason to begin.
2. **Onboarding** — teach the affordances and help the user feel capable and safe.
3. **Doing** — the main activity; the user explores, acts, learns, or plays.
4. **Transition** — bridge between activities/scenes or shift the user's attention/state.
5. **Completing** — signal that the task or experience has reached a satisfying end.
6. **Reflection** — allow the user to interpret, remember, share, or consider what happened.

The **core loop** is the repeatable action/reward cycle within the Doing phase (for example: explore → act → receive feedback/reward → choose the next action). It supports engagement, but it is not the same as the six-stage overall arc.

Spatial experiences can be harder to understand than mobile apps, so onboarding may be sequential and continue during use. Reminders or practice can build competence while the user is already having fun. For example, a VR game that teaches aiming by asking the user to shoot menu targets turns instruction into skill practice.

### Four reward types

Designers should ask what the audience values and where the genuine reward lies, then sequence discovery, learning, and rewards accordingly.

- **Autonomy** — having meaningful choice, control, and agency.
- **Competence** — mastering a skill, understanding a system, or seeing progress.
- **Relatedness** — belonging, connection, or shared activity with other people.
- **Reciprocity** — mutual exchange, contribution, or returning value to others/a community.

Example: a collaborative AR city hunt might offer autonomy (choose routes), competence (solve increasingly difficult clues), relatedness (team play), and reciprocity (leave clues or discoveries for the next group).

### Two avatar purposes

- **Expressive/game/social avatars** are stylized or gamified representations. They can support identity play, expressive movement, facial-expression tracking (the Meta Quest Pro example uses face-facing sensors), social presence, and entertainment.
- **Realistic Personas** are intended for situations where people need to show up as themselves—work meetings, calls with family, and shared activities. The Vision Pro example records facial expressions on first setup and creates a 3D representation; the slides discuss Gaussian splatting in realistic-avatar development. Supported apps can use a Persona in FaceTime, meetings, collaborative design, or other multi-user sessions.

The avatar that is desirable depends on purpose: play and self-expression often benefit from flexible stylization; trust and face-to-face communication often benefit from recognizable likeness and expression. “More realistic” is not universally better.

## 9. Vision Pro setup and navigation

### Personalizing eyes and hands

The device learns the user's eye/gaze and hand interaction so that selection and spatial response are personalized. The setup flow asks the user to look at individual dots and tap the index finger and thumb together to confirm each one. If setup fails or must be repeated, the course handout says to ask Siri to redo eye setup. This calibration makes gaze targeting and pinch confirmation work for that person.

### Gaze + pinch: select and open

1. Look at an app icon to target it.
2. Tap/pinch the index finger and thumb to confirm/open it.
3. Repeat gaze-to-target plus pinch for app controls.

This separates **pointing/targeting** (eyes) from **confirmation** (hands), avoiding the need to point a controller at every object.

### Hand gestures that expose menus

- Look at the right palm; a circle/menu affordance appears. Move the hand and the circle follows. Tap/pinch it to open the app view, then choose another app.
- Turn the right hand over to reveal an information/control affordance; select it to open Control Center.
- Double-click the crown to re-center the Home Screen if it is off to the side or out of view.
- Grab the line at the bottom of a window to move it; look at a corner and drag the curved handle to scale; select the X to close.

### Guest setup

The handout also describes using the crown to align the display and accepting Guest Mode with a double-click. The exact first-use prompt may vary; the exam-relevant interaction principle is personalized eye/hand setup plus gaze-and-pinch navigation.

## 10. Assigned *UX for XR* reading: key insights in your own words

### Sections 1.1–1.3 — spatial computing, UX, XR

- Spatial computing changes the design surface from a framed rectangle into an interaction that may use space, speech, gestures, gaze, the body, and multiple senses.
- UX is holistic: it includes the user's interaction with the product, services, hardware, and surrounding context. UI is important but narrower.
- XR designers need to understand what the technology can and cannot do, and how technical dependencies affect design; they do not all need to be programmers.
- XR work often grows out of 3D/game-engine pipelines. Game design already handles mechanics, flows, and story, but its established audience and genre conventions may not answer the needs of a new enterprise, health, or education audience.
- UX research fills that gap by learning users' goals and context, developing personas/scenarios, prototyping, and testing. UX and game teams benefit from sharing vocabulary and methods.

### Sections 2.2.2–2.2.6 — AR history and XR design elements

- AR adoption developed along a relatively accessible path: early displays and specialist uses, then mobile cameras, markers, playful social overlays, and mass-market apps. Pokémon Go was a major adoption milestone; strong familiar IP and location tracking helped its reach.
- In 2010–2020, mobile computing, ARKit/ARCore, VR headsets, and HoloLens/Magic Leap moved XR from experiments toward more polished consumer products.
- **Industry 4.0** refers to connected, data-driven, decentralized production using technologies such as AI, IoT, cloud systems, and XR. Spatial computing can extend similar ideas into homes, cities, and services.
- UX helps turn varied XR technologies and inputs into something users can learn, trust, and adopt. Important principles can be shared across device categories even when the hardware differs.
- Seven design areas recur: comfort/safety; interaction (affordances, signifiers, feedback); environment/spatial components; sensory input; engagement/storytelling/gamification; constraints; and inclusion/diversity/accessibility.
- Comfort and safety are not optional: anticipate movement, play space, disorientation, and device limitations. Constraints can guide attention and prevent unsafe or confusing actions.
- Sensory cues (visual, audio, haptic) can direct attention, explain state, and help users navigate. Story and rewards help answer “what should I do next?” Accessibility includes different bodies, abilities, cultures, and situations.

### Sections 2.4–2.4.5 — AR categories and UX

- **Marker-based AR** recognizes a designed pattern/image (or QR-like marker); it works well for books, manuals, education, and contextual product information.
- **Markerless AR** uses mapping/tracking such as SLAM to place content on surfaces, as in furniture placement.
- **Location-based AR** uses location/orientation sensors and ties digital content to places, as in navigation or location games.
- These types can run on handheld devices or headsets, but their interaction conventions differ: handheld AR is screen/touch-centered; headsets use spatial interaction, gaze, gestures, or controllers. Projection AR is a separate installation-based category.
- The reading traces early AR from Ivan Sutherland's 1968 concept, through Thomas Caudell's 1990 use of the term “augmented reality,” to specialist wearable systems such as BARS in 1999 and later consumer handheld AR.
- LiDAR/depth sensing can improve environmental understanding and occlusion, but capability varies by device. Designers should avoid assuming every phone senses the world equally well.
- AR's real environment is part of the design context. Spatial objects have 3D position even if their surface is visually flat. Placement, guidance, off-screen cues, scale, and testing matter.
- Privacy and social acceptability are UX issues. Google Glass illustrates how camera concerns and public reaction can undermine an otherwise capable device. Explain sensing and data use; consider whether gestures or device use feel safe and appropriate in public.

### Sections 4.2.2–4.2.3 — user funnel and 3D design

- XR has a **friction funnel**: the effort and time between deciding to use an experience and reaching its valuable part. Hardware contributes, but designers can improve the initial flow.
- The first 30–60 seconds are especially important. Slow loading, stutter, a blank space, or disorientation can make the experience feel broken. Use empathy to anticipate the user's worries.
- An empathy map captures **Says, Thinks, Does, Feels** to surface goals, behavior, and emotion. Strong onboarding introduces actions in small steps, uses familiar elements, previews the world, and offers something positive early.
- XR content lives in 3D, even if it looks like a flat panel. Consider perspective, viewing angle, distance, lighting, shadows, anchoring, and what happens when the user approaches or activates an object.
- Make state visible with feedback—glow, movement, scale change, sound, or another cue. Familiar game techniques (e.g., a camera-facing billboard or menu that follows the user) can solve spatial readability problems. The reading also uses MRTK (Mixed Reality Toolkit) as an example of a framework that prioritizes hand interaction and can inform both AR and VR.

### Sections 4.3.6–4.3.7 — spatial objects and social AR

- In VR, 3D objects build the environment. In handheld/social AR, a single object often carries the whole interaction: the “AR object is the app.” It can feel personal because it appears in the user's own space and reacts to their actions/environment.
- Good social AR objects need attractive modeling, texture, animation, clear triggers, and platform-aware design. Verify what the authoring platform supports before designing interactions.
- Convincing placement uses environmental lighting/shading and surface shadows. **Physically Based Rendering (PBR)** uses material maps such as albedo/color, normal, roughness, metalness, and ambient occlusion to control appearance under light.
- Animation communicates state and meaning: an idle loop can invite activation; a triggered one-shot can reveal information or a call to action. The goal is legibility and visual fit, not realism for its own sake.
- Platform support and asset formats constrain production. The reading names **glTF** and **USDZ** as modern AR object formats that can carry PBR materials and animation; authoring/viewing platform capabilities should be checked before detailed design.

### Section 5.2.5 — handheld AR UX

- The phone camera and physical environment are central. Tell users what kind of space is needed; guide them safely and account for movement.
- Holding a phone at a particular height/angle becomes tiring. Vary the interaction and let some content continue outside the camera view.
- Use off-screen arrows for content outside the frame. Favor familiar direct gestures, visible 3D hints, and simple feedback; reduce text, and use audio or vibration when it helps.
- Shadows, lighting, and reflections communicate where an object sits, how far it is from a surface, and whether it is attached or floating.
- Content may need to adapt between handheld (often below shoulder level) and glasses (at eye level); viewing distance, field of view, and stereoscopic depth change the design.

## 11. High-value distinctions to remember

| Don't conflate | Correct distinction |
|---|---|
| UX and UI | UI is one part of a broader end-to-end experience. |
| Anchor and trigger | An anchor positions/references content; a trigger starts a behavior. |
| World space and screen space | One is 3D/environment-relative; the other is fixed to the display/interface. |
| Markerless and location-based AR | Markerless maps/tracks surfaces/space; location-based ties content to geographic position. |
| Optical and pass-through | Optical shows the real world directly through lenses; pass-through shows camera video on displays. |
| 360 video and interactive VR | Captured video can look realistic but is less interactive; realtime apps respond to user input but often use stylized graphics. |
| Immersion and engagement | Immersion concerns sensory presence; engagement concerns meaningful interaction and continued participation. |
| Core loop and experience arc | The loop repeats inside the Doing stage; the six-stage arc structures the whole experience. |
| Avatar styles | Expressive/game avatars and realistic personas serve different social purposes. |

## 12. Closed-book recall prompts

Try these aloud or in writing before opening the companion quiz:

1. Give three examples of AR embedded in a product, piece of equipment, or activity. What physical context makes each useful?
2. Define anchor, world space, screen space, occlusion, event-based interaction, scene, and sequence.
3. Explain persistence, SLAM/VPS positioning, absolute scale, and real-world colliders; give a brand/product reason for each.
4. Name the five Vision Pro content patterns and describe three.
5. Compare optical Specs with pass-through Quest/Vision Pro in view, use context, and interaction design.
6. Explain how mobile conventions and game conventions each influence XR interaction.
7. Define all five rich-experience terms on Week 6 p. 20. Why is it safest to learn five even though the study guide says four?
8. Name the six experience stages in order and distinguish the core loop.
9. Describe the four reward types and give an example of each.
10. Contrast an expressive avatar with a realistic Persona.
11. Explain why a first-run eye/hand calibration is needed and how gaze and pinch work together.
12. Summarize one key insight from each assigned *UX for XR* reading block.

## Source coverage

- `20263.538_MidtermExam_StudyGuide (1).pdf`: exam scope and format.
- `iDSN538_Wk2_Slides_(T).pdf`: pp. 49–58.
- `iDSN538_Wk3_Slides_(T).pdf`: pp. 13–20, 34, 49, 52.
- `iDSN538_Wk4_Slides.pdf`: AR concepts and advanced AR features.
- `iDSN538_Wk5_Slides (T).pdf`: Vision Pro content types, creator ecosystem, Specs comparison, developer tools.
- `iDSN538_Wk6_Slides (T).pdf`: UX, IoT, design influences, rich experiences, markets.
- `20263.538_Week7(T).pdf`: experience stages, reward types, avatars.
- `Setting up and navigating AVP.pdf`: hands/eyes setup, gaze/pinch navigation, menus, and window manipulation.
- `UX for XR.pdf`: 1.1–1.3; 2.2.2–2.2.6; 2.4–2.4.5; 4.2.2–4.2.3; 4.3.6–4.3.7; 5.2.5.