WEBVTT 00:00:03.060 --> 00:00:08.209 There are five key factors in AR spatial  UI design that I'd like you to understand. 00:00:13.020 --> 00:00:17.446 The first one is designing for what I call *context intelligence*. 00:00:17.446 --> 00:00:21.414 That's the use and care for *space and place*. 00:00:21.414 --> 00:00:27.159 Look – the AR system is context-sensing;  it can tell the space around you; it's mapping it. 00:00:27.159 --> 00:00:32.845 So, holograms and objects must respond to or be context-aware. 00:00:32.845 --> 00:00:38.713 And it's important that you use space to organize your content and your story triggers. 00:00:38.713 --> 00:00:42.776 So, that's critical – *context intelligence*. 00:00:42.776 --> 00:00:47.891 The second one is *minimizing abstract  UIs*. So, *affordances first*. 00:00:47.891 --> 00:00:53.515 If it's grabbable, make it look grabbable. Don't make them discover and figure out 00:00:53.515 --> 00:00:57.420 if there's a trapdoor or secret UI. 00:00:57.420 --> 00:01:02.245 Remember that you have *time constraints* because you have more like bursts of attention with AR. 00:01:02.245 --> 00:01:08.734 Whereas with VR, maybe you can spend a lot of time, but these guidelines still apply to VR situations as well. 00:01:09.480 --> 00:01:14.848 *Direct manipulation* is the third one. So, natural interactions, simple hand gestures, 00:01:14.848 --> 00:01:21.404 gaze, minimizing how much they navigate, how much they flip through menus. 00:01:21.404 --> 00:01:27.138 Just minimizing that amount of playing around and closing things 00:01:27.138 --> 00:01:31.815 and getting distracted. Keep them *focused* on what they're doing on their goal with the UI, 00:01:31.815 --> 00:01:34.119 and let them directly manipulate. 00:01:34.119 --> 00:01:37.692 So, if there's data that they're looking at, if they're looking at a visualization of data, 00:01:37.692 --> 00:01:41.302 let them grab one of the variables and drag it down. 00:01:41.302 --> 00:01:47.245 Let them filter by pulling on a slider and controlling 00:01:47.245 --> 00:01:55.302 the back and forth of the data that they're seeing. So, let them literally get hands-on as they perform the task. 00:01:55.302 --> 00:02:01.334 The fourth one is to *respect interruption*. And what I mean by that is 00:02:01.334 --> 00:02:05.280 AR is highly interruptible, like mobile. 00:02:05.280 --> 00:02:09.583 Don't make it so you have to be uninterrupted – like, *design for interruption*. 00:02:09.583 --> 00:02:15.128 Like, if it's going to be interruptible, make sure that you have shallow entry and exit. 00:02:15.128 --> 00:02:19.963 If you want to make sure you're designing for interruption, take your headset off, 00:02:19.963 --> 00:02:25.842 put your phone down if it's a phone-based AR experience, and *interrupt yourself while you're designing*. 00:02:25.842 --> 00:02:31.415 And you'll be able to appreciate more of that. So, *learn from mobile distraction* – you know, 00:02:31.415 --> 00:02:37.997 The constant notifications that we get – this is another type of interruption that I think is bad Interruption. 00:02:37.997 --> 00:02:43.680 So, if you're constantly getting notifications  about what's going on while you're in, for example,  00:02:43.680 --> 00:02:48.986 a social VR, it might not be helpful to that person; it might just get them in this addictive, 00:02:48.986 --> 00:02:54.572 constantly checking loop that we've come to learn through mobile interruption. 00:02:54.572 --> 00:03:01.205 *Time pressures in AR should avoid dangerous contacts* like that... 00:03:01.205 --> 00:03:05.405 bus coming by or wandering around on a street. 00:03:05.405 --> 00:03:11.129 Look – if sensing a street, don't have people swat jewels as cars fly by. 00:03:11.129 --> 00:03:14.314 The fifth one is to *respect and enable users' spatial memory*. 00:03:14.314 --> 00:03:20.363 In other words, keep interactions and objects *shallow* – don't go down in that rabbit hole.