Back to Teaching

Teaching

Designing for Gradient Spaces

Designing physical-digital spaces that blend from real reality to virtual reality and anything in between — from design thinking to architectural and technological design, with a focus on mixed reality.

Overview

Course information

Course ID
CEE 342 (Spring 2026)
Instructor
Iro Armeni
Teaching Assistants
Jianhao Zheng, Martin Bucher
Lectures
Mondays 1:30–4:20 PM, Y2E2 292A
Credits
3 or credit/no credit
Office Hours
Iro Armeni — Wednesdays 2–3 PM, Y2E2 233
Jianhao Zheng — Thursdays 2:30–3:30 PM, Y2E2 278A
Martin Bucher — Thursdays 2:30–3:30 PM, Y2E2 278B
Online Material
Canvas
Course GitHub
github.com/cee342
Notes
We welcome undergraduate, MS, and PhD students.
For CEE MS SDC students: included in the Requirements, under Building, Infrastructure, and Urban System Development.
Changing in Spring 2027 to “Mixed Reality: Designing & Developing Spatial Computing Apps”.

Description

Course description

Summary

The course delves into designing for gradient spaces. What are gradient spaces?

Gradient spaces (read me!) are physical spaces that blend from the 100% physical (real reality) to the 100% digital (virtual reality) and anything in between. Through a series of lectures, discussions, and hands-on projects, the course explores what it means to design in such physical-digital spaces on three core levels — from design thinking to architectural design and technological design, with a focus on mixed reality. It considers these from the perspective of occupants of these spaces, who have different physical and digital needs and preferences.

The goal of the course is to create cross-disciplinary interactions that connect physical space design and digital application design, towards the creation of physical and digital experiences that are suitable for and centered on users. Students will be exposed to all three levels of design, but are expected to focus on only one for their final project.

Learning goals

By the end of the course, students will acquire design and implementation skills in developing components that blend physical and digital reality in different degrees, while supporting such a living experience. Specifically, they will:

  • Gain a fundamental understanding of what gradient spaces are and how to create their components.
  • Learn to approach the design of gradient spaces under the dual lens of physical and digital.
  • Develop skills to create and evaluate the components, and acquire hands-on experience through tutorials, studios, and the final project.
  • Interact with a range of domain backgrounds, through guest speakers from industry and academia or through fellow classmates.

Prerequisites / notice

The course is set up to include students from different departments. Although there are no dependencies on other courses, this is not an introductory course. To have a successful experience, students are required to have: (i) coding experience, if they would like to develop mixed reality or other applications for their final project; (ii) architectural design knowledge, if they would like to design a space; (iii) prototyping knowledge, if they would like to create a prototype; etc.

Performance evaluation

Grading combines 2 assignments, 6 readings, and a final project. Assignments require critical thinking, research into prior work, or hands-on interaction with a pre-existing system, and are designed to complement the final project. The final project asks students to creatively design and develop an application based on the material covered in the lectures; there is no final exam. Students may be evaluated with a letter grade or credit/no credit.

Grading weights: 30% assignments (15% each), 8% readings (1% each, except Reading 6, which is 3%), and 65% final project (10% proposal report, 12% midterm report, 40% final report).

Evaluation criteria for each assignment and project milestone are on Canvas under the relevant entry in “Assignments”. Course projects are assigned for review to a team member other than the assigned TA to reduce bias, with quick feedback from project supervisors and the assigned TA. The final project grade is decided by considering all feedback during a discussion with the teaching team. All members of a team receive the same grade unless there are obvious signs of unequal participation and work.

Late submission policy: students have a total of 3 late days across the course. Each day used reduces that deliverable's grade by 15%, compounding for consecutive days (e.g., two late days: grade × 0.85 × 0.85). In case of genuine emergencies, contact the teaching team — some proof may be requested. Late project reports incur the same penalty for all team members. No late submissions are accepted for project presentations.

Schedule

Lectures, tutorials & deadlines

Lectures

DateLecture
March 301. Introduction
April 62. Architecture: Building physical, digital, and gradient worlds
April 133. Interpreting the world around us: Visual Machine Perception & Scene Understanding
April 20 4. Design Thinking In-class project proposal presentations
April 275. Metrics and Evaluation
May 46. Rendering the Gradient World
May 11 7. Perception Engineering In-class midterm presentations
May 188. Mixed Reality Sensory Architecture
May 25No class: Memorial Day
June 19. Mixed Reality for Architecture, Engineering & Construction (AEC)
June 8Final Project Presentations & Demo

Tutorials

DateTutorial
March 301. Introduction
April 62. Hello World: Building and Deploying an MR Application
April 133. Exploring the SDK I: Hand Pose & Gesture Tracking, Interaction With Virtual Objects, User Interfaces
April 20Project Proposal Presentations
April 275. Exploring the SDK II: Scene Geometry, Spatial Audio
May 46. XREAL AR, Haptics, and Coding Agents
May 11Midterm Presentations
May 188. Leveraging & Integrating Pre-Trained Models for Your Apps
May 25No class
June 19. Collaborative Work Session
June 8Final Project Presentation

Deadlines

DeadlineDescription
April 6 Finish pre-tutorial setup before class Reading 1; form teams and choose project
April 13Reading 2
April 20 Project proposal report and slides Project proposal presentation, in class
April 27Reading 3; Assignment 1
May 4Reading 4
May 11 Midterm project report and slides; Assignment 2 Midterm project presentation, in class
May 18Reading 5
May 25Assignment 2
June 1Reading 6
June 8 Final project report and video Final project presentations and demo day, in class

All online submission deadlines are due by 1:30 PM on the specified date.

Projects

Student projects

Over the quarter, students work on a project related to Designing for Gradient Spaces in collaboration with a supervisor, in groups of 2–4. A list of project suggestions is provided, but students are free to propose their own project. Projects are assigned first come, first served.

Project proposal

A 1–2 page proposal describing what the project will do and how the team plans to achieve the envisioned results, developed in discussion with the assigned supervisor. A good place to start is to identify the physical and digital connection, as well as the algorithmic and technical challenges, addressing each individually and considering alternatives where an approach seems likely to fail. Teams present their proposal during a designated lecture and submit a presentation file along with the report.

Midterm progress check

A 2-page report describing progress with respect to the questions the project should answer — a checkpoint about halfway before the final presentation and report. Teams present in class to get feedback from the teaching team and fellow classmates, and are encouraged to raise open questions. A presentation file is submitted along with the report.

Final project delivery

A final presentation on the last day of class, along with an 8-page report (tables and figures included, references excluded) and the presentation file. Final demos are held right after the final presentations.

Templates are provided for all reports and presentations.

Equipment

Available devices

The following devices are available: Apple Vision Pro (×1), Meta Quest Pro (×1), Meta Quest 3 (×10), and XREAL Air 2 (×10). There are also haptic gloves (×5), suits (×5), and anklets (×5) compatible with Quest 3. Students can also use their own phones and webcams. For robotics applications, space to work can be arranged, but robotic devices may not be available. Supervisors will also provide devices for projects with special needs.

When picking a project, make sure you can fulfill the OS requirements for each device. If you want to work with a device that is best suited to another OS, consider setting up a virtual machine.

Device requirements

Meta Quest
Works on both Windows 10/11 and macOS together with Unity.
Quest Link requirements
Apple Vision Pro
The visionOS SDK requires Xcode and a Mac with an M1 chip or newer.
iPads
The iPadOS SDK also requires Xcode, but can be used on older, Intel-based Macs.
XREAL Air 2
The XREAL SDK requires Unity (2021.3+) with Android Build Support. It supports Intel Macs for basic use, but a Mac with an M1 chip or newer is recommended for the full Nebula development environment.
Nova 2 Haptic Gloves
Requires the SenseCom software to be running. Native development is Windows-focused; supports Unity 2019.4 LTS or newer.
TactSuit Pro Haptic Suit & Anklets
Windows 10/11 or macOS (Apple Silicon) with bHaptics Player; integrates with Unity 2019.4 or later.

Resources

Other resources