WEBVTT - Fw Thinking: Your Body as a Computer Interface 0:00:04.400 --> 0:00:07.800 Welcome to Tech Stuff, a production from I Heart Radio. 0:00:12.000 --> 0:00:14.720 Hey there, and Welcome to tech Stuff. I'm your host, 0:00:14.800 --> 0:00:17.800 Jonathan Strickland. I'm an executive producer with I Heart Radio. 0:00:17.920 --> 0:00:21.439 And how the teg are you? Yeah, I'm still sick. 0:00:21.800 --> 0:00:26.279 I'm working on it. It's a process, but I don't 0:00:26.280 --> 0:00:28.400 want to leave you without an episode, and I also 0:00:28.440 --> 0:00:30.800 don't want to subject you to having to listen to 0:00:30.800 --> 0:00:34.160 me sound like this for any real length of time. 0:00:34.640 --> 0:00:37.600 So I thought I would bring you an episode from 0:00:37.800 --> 0:00:40.880 the show Forward Thinking that we did several years ago. 0:00:41.560 --> 0:00:45.120 And by we uh, the podcast was was hosted by myself, 0:00:45.600 --> 0:00:49.479 Lauren Vogelbaum, whom you might know from Savor as well 0:00:49.520 --> 0:00:53.240 as lots of other stuff, and uh Joe McCormick, who 0:00:53.320 --> 0:00:55.520 you might know from Stuff to Blow your Mind and 0:00:55.600 --> 0:00:59.760 other stuff. So Lauren and Joe and I did episodes 0:01:00.360 --> 0:01:05.360 about futuristic stuff, not always technology, but often technology, and 0:01:05.400 --> 0:01:09.440 this particular episode is technology related. The title of the 0:01:09.480 --> 0:01:13.559 episode is your Body as a Computer Interface. I hope 0:01:13.600 --> 0:01:26.120 you enjoy Welcome to Forward Thinking. Hey there, and welcome 0:01:26.160 --> 0:01:29.520 to Forward Thinking, the podcast that looks at the future 0:01:29.600 --> 0:01:34.200 and says I sing the body electric. I'm Jonathan Strickland, 0:01:34.240 --> 0:01:37.880 I'm Lauren Vocal and I'm Joe McCormick, and uh, guys, 0:01:38.000 --> 0:01:41.120 this just didn't did did did? Did? Did? Did? Did? Did? 0:01:41.640 --> 0:01:45.080 I'm sorry, it's porky pick Lauren similar no, no, no 0:01:45.360 --> 0:01:50.640 breaking news. We got a tweet on Twitter from one 0:01:50.880 --> 0:01:55.080 Chris Newcomb who said, in case your listeners didn't know 0:01:55.640 --> 0:02:00.400 concrete ships, and he provided a link and and said, hey, kids, 0:02:00.440 --> 0:02:02.360 swing around this thing for fun. And the link is 0:02:02.440 --> 0:02:06.000 to a wiki entry for the S S. Palo Alto, 0:02:06.400 --> 0:02:10.160 which is a concrete tanker ship from World War World 0:02:10.280 --> 0:02:13.720 War One. Why are we bringing this up? Is it 0:02:13.800 --> 0:02:18.040 because in a recent episode we made jokes about concrete ships. Yes, 0:02:18.120 --> 0:02:20.920 that's exactly what we did. In our Building Materials episode, 0:02:20.960 --> 0:02:22.760 which came out a couple of weeks ago or so, 0:02:23.360 --> 0:02:26.720 we all had a really good lull about how concrete 0:02:26.760 --> 0:02:30.280 ships are completely ludicrous idea that no one would ever 0:02:30.400 --> 0:02:33.799 possibly put into use. I think specifically what happened was 0:02:34.160 --> 0:02:36.800 we were talking about what you should make out of concrete, 0:02:36.880 --> 0:02:40.239 and I said, obviously boats. Yeah, I had no idea 0:02:40.360 --> 0:02:42.760 that this was a real thing. In my defense, because 0:02:42.800 --> 0:02:46.359 I was the person who immediately struck that down. This 0:02:46.480 --> 0:02:50.120 ship was retired like in ninety nine and then it 0:02:50.280 --> 0:02:54.359 broke in half. So but there are totally ships that 0:02:54.480 --> 0:02:58.040 are made to this day with pharaoh cement, which is 0:02:58.160 --> 0:03:00.959 a type of concrete that's reinforced with mession rebar and 0:03:01.040 --> 0:03:04.840 stuff like that. Uh so, so that happens. And I 0:03:04.960 --> 0:03:08.240 just wanted to wanted to update you guys important news updates. Well, 0:03:08.320 --> 0:03:10.680 thank you for the info, Chris. I I feel much 0:03:10.760 --> 0:03:13.160 more educated than I was before. And I also now 0:03:13.200 --> 0:03:15.600 feel like I have a magic power to make unlikely 0:03:15.680 --> 0:03:19.920 seeming things real by laughing at them. So what if 0:03:20.000 --> 0:03:26.120 there was a boat made out of uranium? You know what. 0:03:26.760 --> 0:03:28.480 As as funny as that is, and as much as 0:03:28.480 --> 0:03:30.200 I would love to dwell on it, I I did. 0:03:30.360 --> 0:03:32.519 I did a little bit of research on a totally 0:03:32.600 --> 0:03:36.840 different topic. Uh yeah. Yeah. First of all, thanks again 0:03:36.960 --> 0:03:39.080 Chris for sending that message. And we we really love 0:03:39.120 --> 0:03:41.840 hearing from you guys, and it was awesome learning something 0:03:41.920 --> 0:03:44.720 that we thought was ridiculous. Uh. Today we're gonna talk 0:03:44.760 --> 0:03:47.560 about something else that at times comes across as a 0:03:47.600 --> 0:03:50.680 little ridiculous, which is the idea of one is the 0:03:50.840 --> 0:03:54.160 future of the kind of the interface that we use 0:03:54.360 --> 0:03:59.240 between us and our technology. Specifically, what happens when we 0:03:59.680 --> 0:04:05.120 turn ourselves into that interface? Yes, but in your face 0:04:05.720 --> 0:04:08.400 is what happens. I guess that kind of is I 0:04:08.800 --> 0:04:10.880 wanted to do you guys have any like really good 0:04:11.800 --> 0:04:16.320 terrible interface stories? Well, I mean, just here, did you 0:04:16.360 --> 0:04:20.040 have a favorite terrible interface? To me, it's not so 0:04:20.160 --> 0:04:23.040 much a terrible interface as it was a frustrating process 0:04:23.200 --> 0:04:26.560 of learning how to use it. I'm left handed, and 0:04:26.680 --> 0:04:29.960 I'm old enough to remember personal computers before the mouse, 0:04:30.680 --> 0:04:32.960 and when the mouse came along, and then suddenly the 0:04:33.040 --> 0:04:36.680 mouse was absolutely required in order for you to be 0:04:36.800 --> 0:04:41.960 able to to navigate through software, it became very difficult 0:04:42.040 --> 0:04:44.640 for me. Like other folks were picking up on it 0:04:44.839 --> 0:04:46.800 very quickly, for me, it was more work because I 0:04:46.880 --> 0:04:49.520 didn't have that kind of fine tuned precision with my 0:04:49.640 --> 0:04:51.200 right hand the way I do with my left hand, 0:04:51.360 --> 0:04:54.840 and they didn't have left handed mice, and and by 0:04:54.880 --> 0:04:56.839 the time they did, I was so used to using 0:04:56.880 --> 0:04:59.560 my right hand for that I couldn't use a mouse 0:04:59.640 --> 0:05:02.360 left hand it. I mean, I it felt wrong and 0:05:02.800 --> 0:05:06.200 and nonintuitive because I had trained myself how to use 0:05:06.279 --> 0:05:09.360 it with my right hand. But for me, that interface 0:05:09.480 --> 0:05:13.960 initially at any rate, was not great. But that was 0:05:14.040 --> 0:05:18.400 again due to my own personal uh, left handedness, my 0:05:18.600 --> 0:05:22.000 sinister state of being. You know, I think you've probably 0:05:22.120 --> 0:05:28.000 had experiences with other maybe awkward interfaces. What about Google Glass? Yeah, 0:05:28.320 --> 0:05:31.080 Google Glass. Actually I was all right with Google Glass 0:05:31.080 --> 0:05:34.280 because I knew going into it what the interface was 0:05:34.360 --> 0:05:38.200 going to be like. But in general, actually Google is 0:05:38.200 --> 0:05:41.400 a great example. Just in general, Google, uh is a 0:05:41.560 --> 0:05:45.960 company that is clearly populated by engineers who have a 0:05:46.200 --> 0:05:49.320 very specific idea of how to solve a problem, which 0:05:49.440 --> 0:05:52.920 may or may not translate to any other human beings experience. 0:05:53.440 --> 0:05:56.880 And so when you use a Google product, you have 0:05:57.000 --> 0:05:59.000 to kind of learn how to think in the way 0:05:59.760 --> 0:06:02.120 the engineers were thinking when they designed it, and then 0:06:02.200 --> 0:06:07.480 it works. But initially it can be very difficult to 0:06:07.640 --> 0:06:09.640 kind of suss out what you're supposed to do or 0:06:09.720 --> 0:06:11.720 how you're supposed to get your technology to do the 0:06:11.839 --> 0:06:13.960 thing you wanted to do. Yeah, we'll show. I mean, 0:06:13.960 --> 0:06:16.000 there's a learning curve to any kind of interface that 0:06:16.080 --> 0:06:19.640 you use to to to use technology. I'm still completely 0:06:19.680 --> 0:06:24.200 mystified by the N sixty four controller designed for someone 0:06:24.320 --> 0:06:27.360 with three hands. I just speak about it. It just 0:06:27.480 --> 0:06:30.000 makes me frustrated. It just makes me feel like I'm 0:06:30.000 --> 0:06:35.440 about to lose and get a turtle shell, right, or 0:06:35.480 --> 0:06:39.400 the old or the very old Microsoft Xbox Duke controller 0:06:39.520 --> 0:06:44.000 which was roughly the size of a Volkswagen Beetle like 0:06:44.440 --> 0:06:46.680 some of those, Or you'll think about some of the 0:06:46.760 --> 0:06:50.960 really frustrating interfaces that were meant to be groundbreaking, like 0:06:51.320 --> 0:06:53.720 the power glove. I mean, I don't know if you 0:06:54.320 --> 0:06:57.560 guys might be too young to appreciate what a terrible, 0:06:58.720 --> 0:07:01.120 terrible product that was. I never I never owned one. 0:07:01.200 --> 0:07:03.400 I don't think I even knew anyone who had. I 0:07:04.400 --> 0:07:07.760 played with one, and it was you would rapidly go 0:07:08.040 --> 0:07:10.920 from this looks so cool on me too, This is 0:07:11.160 --> 0:07:15.640 completely useless if I want to actually play a game. Um. Yeah, 0:07:15.720 --> 0:07:17.840 there are a lot of examples of interfaces out there 0:07:17.960 --> 0:07:20.960 that got in the way, and really what we're trying 0:07:21.040 --> 0:07:24.760 trying to talk about today is the attempt to get 0:07:24.840 --> 0:07:28.280 the interface out of the way to have a seamless 0:07:28.400 --> 0:07:32.240 interaction between us and the technology that we depend upon 0:07:32.600 --> 0:07:35.160 and want to use. Yeah, okay, so I guess we 0:07:35.200 --> 0:07:38.840 should do a quick bit of definition just in case 0:07:38.960 --> 0:07:41.120 you haven't been following us. So much so far you 0:07:41.240 --> 0:07:44.120 probably have. But just to be clear, what is an interface. 0:07:44.440 --> 0:07:46.960 It's a system that controls in putting output. It's the 0:07:47.080 --> 0:07:50.680 interaction between a human and a computer. And so this 0:07:50.760 --> 0:07:53.440 can be hardware or software. The hardware would be things 0:07:53.520 --> 0:07:56.320 like a screen where you see what's coming out of 0:07:56.360 --> 0:07:58.840 the computer you can know what the computer is doing 0:07:58.880 --> 0:08:02.880 for you. And hardware input like a mouse or keyboard. Uh. 0:08:02.960 --> 0:08:05.560 And sometimes you can combine input and output into a 0:08:05.640 --> 0:08:09.840 single device, for example a touchscreen. Classic example inputting output 0:08:09.920 --> 0:08:14.120 in the same object. But interfaces can also be software. 0:08:14.200 --> 0:08:17.320 So the classic example is the graphical user interface. Like 0:08:17.400 --> 0:08:21.640 when you go and use Microsoft Windows, you're interacting with 0:08:22.000 --> 0:08:26.040 memory in the computer through pictures. You know, you move 0:08:26.200 --> 0:08:30.040 files around into different folders. Really that's data coded to 0:08:30.120 --> 0:08:33.840 different locations in the memory, but there's a graphical representation 0:08:33.960 --> 0:08:36.360 of it for to make it easier for you. You're 0:08:36.360 --> 0:08:41.480 also executing programs that are represented as a some sort 0:08:41.520 --> 0:08:43.760 of graphic uh. You know. Of course, if you were 0:08:43.920 --> 0:08:48.640 using computers before goo ease became a big thing, then 0:08:48.840 --> 0:08:50.760 you were typing all those commands out and you had 0:08:50.840 --> 0:08:53.199 to remember what all the different commands were in order 0:08:53.240 --> 0:08:55.360 for you to do things like navigate to the right 0:08:55.960 --> 0:09:00.120 directory file directory to execute a file. But the the 0:09:00.280 --> 0:09:03.760 graphic user interface ends up simplifying that by creating this 0:09:04.200 --> 0:09:08.240 visually oriented approach to interfacing with the computer. Yeah, and 0:09:08.320 --> 0:09:10.679 so if you look at the history of computing, it's 0:09:10.720 --> 0:09:14.280 clear that interfaces are always changing, but not necessarily at 0:09:14.320 --> 0:09:18.079 a constant rate, not like at the rate that processing 0:09:18.160 --> 0:09:22.000 power seems to steadily multiply over time. Right. Yeah, this 0:09:22.200 --> 0:09:24.719 is another great example. We've talked about this when we 0:09:24.840 --> 0:09:27.559 mentioned Kurt's Wile and Kurt's Wild's look at things like 0:09:27.679 --> 0:09:30.480 Moore's law, and you start to try and uh and 0:09:30.720 --> 0:09:33.360 and draw conclusions about what the future is going to 0:09:33.400 --> 0:09:36.160 be like when by using Moore's law as your starting point. 0:09:36.440 --> 0:09:40.559 But that is really deceptive because, like you're saying, Joe, 0:09:41.080 --> 0:09:46.360 not everything and not everything progresses at that same speed, right, Well, 0:09:46.400 --> 0:09:48.600 and and that speed in particular is a little bit ut. 0:09:48.960 --> 0:09:52.280 What's the word self Oh, there's self fulfilling. Yeah, it's 0:09:52.280 --> 0:09:54.959 a self fulfilling prophecy, because no engineer wants to be 0:09:55.520 --> 0:09:58.800 in the generation that let Moore's law die, you know, Like, no, 0:09:59.000 --> 0:10:01.319 We've got to figure out another way to double the 0:10:01.600 --> 0:10:05.480 processing power of this computer within the next eight to 0:10:05.559 --> 0:10:07.680 twenty four months. Yeah, but but no one has figured 0:10:07.679 --> 0:10:11.280 out how to double the mouse. Right, Hey guys, I 0:10:11.360 --> 0:10:13.319 came up with it. I taped a mouse on top 0:10:13.360 --> 0:10:17.199 of another mouse. It's double mouse. Doesn't really work that way. 0:10:17.320 --> 0:10:21.320 So early computers didn't have a monitor or display. Right, 0:10:21.720 --> 0:10:24.480 You would get your output in some other format, Like 0:10:24.559 --> 0:10:26.920 it could be punch cards. You could get a series 0:10:26.920 --> 0:10:29.319 of punch cards. You've run your your program through. Your 0:10:29.360 --> 0:10:31.880 input was punch cards. Your output is a difference set 0:10:31.920 --> 0:10:34.839 of punch cards, and that's your compiled program. That kind 0:10:34.880 --> 0:10:37.640 of stuff. Or you might get like a printer that 0:10:37.800 --> 0:10:42.319 prints along along uh strip of paper like it like 0:10:42.840 --> 0:10:46.240 tape essentially is what it ends up looking like. Actually, 0:10:46.320 --> 0:10:50.360 a friend of mine, Richard Garriott, he's known as he's 0:10:50.559 --> 0:10:53.280 a game designer. His first game that he ever designed 0:10:53.800 --> 0:10:57.040 printed on tape like that. So every move you made 0:10:57.080 --> 0:11:00.440 in his little dungeon based crawler, it would print out 0:11:00.960 --> 0:11:04.400 what that looked like. It was just a very simplified 0:11:05.120 --> 0:11:07.439 representation of a dungeon, and when you would make a move, 0:11:07.640 --> 0:11:10.680 it would have to print another sheet out to show 0:11:10.760 --> 0:11:13.280 you what had happened. The original idea of the interface 0:11:13.360 --> 0:11:16.000 of the universal touring machine was a strip of paper 0:11:16.559 --> 0:11:19.240 and which in which calculations would be done one at 0:11:19.280 --> 0:11:21.760 a time, printed on a long strip of paper. Yeah. 0:11:22.200 --> 0:11:26.280 So eventually we of all beyond that. We got monitors 0:11:26.440 --> 0:11:31.120 and displays. Uh, we got keyboards, which were much easier 0:11:31.200 --> 0:11:33.480 to use as an interface with a computer as opposed 0:11:33.480 --> 0:11:35.959 to just a collection of punch cards. Later on we 0:11:36.080 --> 0:11:41.360 got the mouse. UM. Xerox ended up Xerox's Park department 0:11:41.520 --> 0:11:44.760 figured out the mouse and the graphics user interface, although 0:11:44.800 --> 0:11:47.079 of course it was Apple that took great advantage of 0:11:47.080 --> 0:11:51.599 that with the McIntosh UM, and so that became like 0:11:51.720 --> 0:11:54.600 the standard interface for computers and the mouse and keyboard 0:11:55.280 --> 0:12:00.840 for a really long time. Was that was input? Yeah, 0:12:00.880 --> 0:12:03.680 I mean you would you had some other like fringe 0:12:03.840 --> 0:12:07.520 input systems, things like light pens and stuff. But yeah, 0:12:07.880 --> 0:12:10.959 but the enjoy besides the joystick, the general public really 0:12:11.040 --> 0:12:15.240 didn't interact dance revolution pad. Yeah. Now these days, we 0:12:15.440 --> 0:12:17.160 we've gotten to a point where we're seeing a real 0:12:17.240 --> 0:12:22.480 revolution interfaces revolution a regular right. It's weird that we 0:12:22.720 --> 0:12:27.160 think of that. We think of like keyboards and mice, mice, mouses, 0:12:27.240 --> 0:12:30.840 whichever it is. UM this is standard, the standard way 0:12:30.920 --> 0:12:35.160 to control input right now. Screens are still pretty much paramount, 0:12:35.240 --> 0:12:37.880 but i'd say that, you know, I bet the majority 0:12:38.000 --> 0:12:41.760 of our web traffic comes from touch screen devices, not 0:12:42.480 --> 0:12:45.559 mouse and keyboard driven devices. That's absolutely correct, and you 0:12:45.640 --> 0:12:48.079 can see it by looking at the metrics. Um, yeah, 0:12:48.160 --> 0:12:51.240 we're getting tons of traffic through mobile, and mobile in 0:12:51.320 --> 0:12:54.760 general is using touch screens. Now, you could also use 0:12:55.080 --> 0:12:57.280 voice commands for a lot of that mobile stuff if 0:12:57.320 --> 0:13:01.400 you were so inclined, just your commands to say, okay, Google, 0:13:01.960 --> 0:13:05.160 how stuff works? Dot Com. I apologize. If you're listening 0:13:05.200 --> 0:13:07.400 to this on an Android device and you have the 0:13:07.440 --> 0:13:11.120 speaker active, oh, you could do GEST your control through 0:13:11.160 --> 0:13:14.240 an Xbox connect or something like that, and they're the 0:13:14.360 --> 0:13:17.240 leap controller for PCs. There are a lot of the 0:13:17.800 --> 0:13:19.400 examples of that. We'll talk a little bit more about 0:13:19.440 --> 0:13:22.120 gest your controls in a bit. But but once you 0:13:22.160 --> 0:13:25.319 get into gest your control, you're entering a new kind 0:13:25.360 --> 0:13:30.959 of territory, aren't you, Because they're the issue is uh, well, 0:13:31.040 --> 0:13:33.560 think about it like this. You're you're using the body 0:13:34.280 --> 0:13:38.319 itself as part of an interface with a machine. So 0:13:38.559 --> 0:13:41.079 using the bodies an interface, it's an interesting kind of 0:13:41.120 --> 0:13:44.160 counterintuitive idea, since an interface is supposed to be the 0:13:44.360 --> 0:13:48.560 bridge between the computer and the power of the computer 0:13:48.760 --> 0:13:50.800 and you the user, what you're getting out of it. 0:13:51.040 --> 0:13:52.800 But if you think about it, we've been bridging this 0:13:52.960 --> 0:13:56.480 gap for so long with physical devices that are connected 0:13:56.679 --> 0:14:00.880 to the computer. Why not flip the script and build 0:14:00.920 --> 0:14:05.000 a bridge in a place that's physically connected to the user. Right, 0:14:05.600 --> 0:14:09.520 And we've seen some some examples of that as well. 0:14:10.320 --> 0:14:15.000 You could argue that VR headsets are are getting into 0:14:15.080 --> 0:14:18.520 that where you are are wearing the computer device and 0:14:18.679 --> 0:14:23.120 your physical motions are what allow you to experience that 0:14:23.360 --> 0:14:26.560 computer power in the way it was intended. Sure, or 0:14:26.640 --> 0:14:32.160 the aforementioned connect sensors, you're you're using your body to interact, Yeah, exactly. 0:14:32.960 --> 0:14:35.560 We'll be back with more of an episode about your 0:14:35.560 --> 0:14:46.680 body as a computer interface after these messages. So we're 0:14:46.720 --> 0:14:50.960 gonna talk about not just ways where you are interacting 0:14:51.680 --> 0:14:55.480 in order to create input into a device, but also 0:14:55.800 --> 0:14:58.800 how you experience the output from that device, right, Yeah, 0:14:59.520 --> 0:15:03.360 So yeah, we should mention some basic ideas in what 0:15:03.640 --> 0:15:06.440 what what's on offer here in terms of the body 0:15:06.600 --> 0:15:09.320 is an interface, so the input is probably the more 0:15:09.360 --> 0:15:13.960 obvious one with input. Instead of pressing buttons on external device, 0:15:14.080 --> 0:15:17.360 moving a mouse or whatever, you might simply perform an 0:15:17.440 --> 0:15:20.640 independent action by and of your own body. So this 0:15:20.760 --> 0:15:25.160 could be gestures, movements, poking yourself, wiggling a part of 0:15:25.280 --> 0:15:32.120 your body, wiggling multiple parts of your body, other people's bodies. No, see, 0:15:32.160 --> 0:15:34.880 then it wouldn't be it wouldn't. That wouldn't quite meet 0:15:34.880 --> 0:15:37.200 the criteria. I think, well, it's still be a body interface, 0:15:37.240 --> 0:15:42.480 it just wouldn't be your body should have a dead body. 0:15:42.520 --> 0:15:44.880 I should have a Bernie device that reminds me of 0:15:44.960 --> 0:15:47.480 a movie that's coming out the go ahead. I think 0:15:47.480 --> 0:15:51.320 a complicated system of shrugs would be really good, right, yeah, right, 0:15:51.520 --> 0:15:53.400 so you never have to lose your cool while you're 0:15:53.400 --> 0:15:56.080 controlling your phone. I meant to. I meant to do 0:15:56.280 --> 0:15:59.440 the the please tell me more shrug, but it turned 0:15:59.440 --> 0:16:03.320 out just the shrug, or a combination of side eye 0:16:03.360 --> 0:16:07.080 and shrug. Anyway, the key ideas that you don't have 0:16:07.200 --> 0:16:10.000 to touch or manipulate anything except your own body. You've 0:16:10.040 --> 0:16:12.200 got it with you all the time. So there you go. 0:16:13.200 --> 0:16:15.600 And it's not this this idea isn't super weird to 0:16:15.720 --> 0:16:18.160 us because we're already familiar with stuff like the connect 0:16:18.200 --> 0:16:20.800 and gest your controls to some extent, then if they're 0:16:20.840 --> 0:16:24.480 not super awesome yet, but then you've also got output. 0:16:24.960 --> 0:16:28.080 So instead of having to look at a screen that's 0:16:28.080 --> 0:16:31.400 attached to an external device, which would cover the vast 0:16:31.560 --> 0:16:34.800 majority of output today, I'm having trouble even thinking of 0:16:34.840 --> 0:16:37.200 a standard device that has a very different way of 0:16:37.280 --> 0:16:40.640 doing it than this. Well, I mean there's a growing 0:16:40.760 --> 0:16:44.920 list of devices that now are using audio. Yeah, so 0:16:45.040 --> 0:16:48.120 things like Amazon's Echo, right, that that would be you're 0:16:48.160 --> 0:16:50.400 not Yeah, that's a good example, but but I get 0:16:50.440 --> 0:16:52.600 what you're saying. Yes, the vast majority, I would say, 0:16:52.640 --> 0:16:56.160 are are visually oriented. So yeah, instead of that, information 0:16:56.280 --> 0:16:59.960 about your computing task is made available directly to your body. 0:17:00.040 --> 0:17:02.640 The classic sci fi example of this would be this 0:17:03.120 --> 0:17:07.360 internal retina display. The screen is projected directly onto your retina. 0:17:07.480 --> 0:17:09.840 But I mean, that's a little crazy. We probably won't 0:17:09.880 --> 0:17:11.840 have anything like that for a long time. If ever. 0:17:12.200 --> 0:17:14.520 Now we have some other examples that we'll talk about 0:17:14.560 --> 0:17:17.440 when we get to a haptics because that's one of 0:17:17.520 --> 0:17:20.800 the other methods of getting feedback from a computer that 0:17:20.880 --> 0:17:24.639 can be meaningful. It's just not visual. Yeah, So I 0:17:24.680 --> 0:17:29.240 would say the middle step between standard inputting output devices, 0:17:29.280 --> 0:17:33.520 standard interfaces and this your own body as an interface 0:17:33.600 --> 0:17:37.399 would be wearables because that's, uh, it's getting close to 0:17:37.520 --> 0:17:40.400 your own body, but it's not quite your own body yet. Yeah, 0:17:40.440 --> 0:17:43.760 it could be something that is unobtrusive where you might 0:17:43.800 --> 0:17:47.040 not even think about it consciously after a while after 0:17:47.119 --> 0:17:49.080 wearing it. Yeah, share like a like a fitbed or 0:17:49.480 --> 0:17:51.520 the pieces of jewelry that they're coming out with something 0:17:51.600 --> 0:17:54.320 like that. Absolutely, that was a great example, and fitbed 0:17:54.480 --> 0:17:57.480 is in fact a fantastic example because so much of 0:17:57.520 --> 0:18:01.399 that interface is invisible to you. That again it's the 0:18:01.480 --> 0:18:04.119 idea of removing that barrier. So a fitbit is going 0:18:04.200 --> 0:18:06.560 to be tracking your steps. You might have other wearables 0:18:06.600 --> 0:18:09.359 that are doing things like tracking your heart rate, uh, 0:18:09.560 --> 0:18:12.720 that sort of stuff. Where the data is going to 0:18:13.240 --> 0:18:16.840 some form of cloud based solution or or potentially just 0:18:16.960 --> 0:18:21.119 being beamed to a local uh device like a smartphone 0:18:21.200 --> 0:18:26.000 or tablet. You're still usually dependent upon that other device 0:18:26.200 --> 0:18:28.920 in order to be able to consume the data in 0:18:29.080 --> 0:18:30.960 some way. It's presented to you in some way, so 0:18:31.040 --> 0:18:34.000 it's not like it's directly getting that data to you 0:18:34.640 --> 0:18:38.120 through the device itself. You're you might have a display 0:18:38.440 --> 0:18:40.680 on the device that gives you some of the basic information, 0:18:41.200 --> 0:18:44.080 but your body is not acting as the display, right, 0:18:44.119 --> 0:18:47.639 it's still the device. Um. It does allow us to 0:18:48.080 --> 0:18:51.359 have other means of interacting with our technology. Some wearables, 0:18:51.520 --> 0:18:54.360 you could argue, like the Nintendo Power Glove was a wearable, 0:18:55.040 --> 0:18:58.800 particularly good one. But it was a wearable. Uh. It 0:18:58.960 --> 0:19:02.600 was not not obtrusive, not you know, it was definitely 0:19:02.760 --> 0:19:07.160 you knew someone was wearing one. But it allowed well 0:19:07.600 --> 0:19:09.159 that was part of the point, right, You wanted to 0:19:09.240 --> 0:19:13.320 show off that you were playing with power Yeah, exactly, 0:19:13.920 --> 0:19:15.840 And you had a glove to yea, and you looked 0:19:15.840 --> 0:19:17.639 a little bit like Michael Jackson in that air a 0:19:17.720 --> 0:19:21.240 little bit, yeah, which at the time was really important. Yeah, 0:19:21.359 --> 0:19:23.080 because if we couldn't get the jacket, we could at 0:19:23.160 --> 0:19:26.600 least get the power glove. But the the you all 0:19:26.680 --> 0:19:29.960 remember the Nightmare on elm Street movie where Freddie wears 0:19:30.000 --> 0:19:36.040 a power glove. I remember seeing it, don't from my mind, 0:19:36.359 --> 0:19:40.840 I think it's okay, Oh god, I was so worried 0:19:40.880 --> 0:19:43.400 about myself for a second there. Okay, now everything's gonna 0:19:43.400 --> 0:19:45.879 be fine, you guys, it's late at six though I 0:19:46.040 --> 0:19:48.239 think that probably are on four. But at any rate, 0:19:48.280 --> 0:19:51.520 I get what you're saying. Um. Yeah, So, so one 0:19:51.600 --> 0:19:53.119 of the things I wanted to talk about this is 0:19:53.200 --> 0:19:56.280 kind of a this is looking ahead at wearables. So 0:19:56.440 --> 0:19:59.399 you could have wearables that are are something that you 0:19:59.520 --> 0:20:02.399 don't interface with directly at all. It could be you know, 0:20:02.480 --> 0:20:04.960 we've we've talked about the possibility of things like r 0:20:05.080 --> 0:20:08.200 F I D chips to have a profile. This is 0:20:08.280 --> 0:20:10.000 sort the sort of thing that Bill Gates was putting 0:20:10.040 --> 0:20:12.119 in his house where you would get a little r 0:20:12.240 --> 0:20:15.960 F I D D badge that would have a profile 0:20:16.040 --> 0:20:19.360 programmed into it that's personalized to you, and then your 0:20:19.480 --> 0:20:21.840 experience as you walk through his house would be to 0:20:22.000 --> 0:20:23.960 see the kind of art that you like, to hear, 0:20:24.000 --> 0:20:26.320 the kind of music you like. The lighting condition would 0:20:26.359 --> 0:20:29.680 be to your preference. Uh, it would be dependent upon 0:20:29.840 --> 0:20:32.399 that profile. We've since reached a point where we can 0:20:32.480 --> 0:20:34.720 get a little more advanced than that. You don't necessarily 0:20:34.960 --> 0:20:37.040 have to have a wearable anymore for that kind of stuff. 0:20:37.080 --> 0:20:41.280 But that was one implementation. Another, however, is this, uh, 0:20:41.520 --> 0:20:47.000 this this haptics feedback solution that I had been talking about, 0:20:47.080 --> 0:20:51.280 so being having to do with your sense of touch exactly. 0:20:51.440 --> 0:20:55.600 So we already are familiar with technology that has haptic feedback. 0:20:55.760 --> 0:20:58.239 Here's one you're very likely to be familiar with. If 0:20:58.240 --> 0:21:00.159 you ever played a video game or the control roll 0:21:00.200 --> 0:21:03.200 or buzzes in your hand you do something, right, that's 0:21:03.240 --> 0:21:05.560 the old rumble pack, right. Those have been around for 0:21:05.960 --> 0:21:09.520 for a couple of generations of video game consoles and 0:21:09.600 --> 0:21:13.320 also for PC controllers, And generally speaking, you you want 0:21:13.440 --> 0:21:18.560 to have a controller that enhances the experience of playing 0:21:18.640 --> 0:21:21.800 a game, so it might be a great example would 0:21:21.800 --> 0:21:24.680 be a stealth based game where you're you're skulking around 0:21:24.720 --> 0:21:27.800 in the shadows and your controller might start to vibrate 0:21:27.880 --> 0:21:31.760 to indicate that perhaps you are visible or potentially visible 0:21:31.800 --> 0:21:34.040 to an enemy, so you need to get back into cover. 0:21:34.480 --> 0:21:37.359 Yeah yeah, vibration being being like your spidy sense going on. 0:21:37.520 --> 0:21:39.879 Yeah um. Or if you're if you're playing a horror 0:21:40.000 --> 0:21:42.399 game and your your life starts getting too low and 0:21:42.480 --> 0:21:46.040 you start feeling your heartbeat through the controller and that 0:21:46.160 --> 0:21:47.800 lets you know that you need to drink a health 0:21:47.840 --> 0:21:50.720 potion or you know, to spell whatever it is right, 0:21:50.840 --> 0:21:55.560 or unplug the game and going to the corner. Yeah. Uh, 0:21:55.720 --> 0:21:57.639 if pyramid head is coming around the corner. You just 0:21:57.720 --> 0:21:59.159 want to like, I just I just need to go 0:21:59.240 --> 0:22:02.480 and read a happy book for a while. Uh. Or 0:22:02.680 --> 0:22:04.879 you know. Another one that everyone is probably familiar with 0:22:05.400 --> 0:22:08.960 are the vibrating motors in uh and and smartphones or 0:22:09.040 --> 0:22:12.800 cell phones, right, And that's a very simple Yeah. Yeah. 0:22:12.960 --> 0:22:15.760 They maybe they vibrate when you're doing an input, or 0:22:15.800 --> 0:22:17.720 they vibrate to alert you that a call is coming in. 0:22:17.840 --> 0:22:21.680 But that's that's the haptic feedback, very basic application of 0:22:21.720 --> 0:22:24.159 haptic feedback. I don't know if you've ever had the 0:22:24.240 --> 0:22:27.760 experience of getting so used to this that it's weird 0:22:27.840 --> 0:22:30.080 when it doesn't happen. I've had this experience with my 0:22:30.200 --> 0:22:32.800 phone where I don't even notice anymore that when I 0:22:32.880 --> 0:22:35.919 punch a key to like enter, you know, to enter 0:22:36.000 --> 0:22:38.000 a letter on a text message or something like that, 0:22:38.400 --> 0:22:40.680 the phone vibrates a little to register like, yeah, I 0:22:40.760 --> 0:22:43.159 got that, I got that letter. Uh. And if the 0:22:43.320 --> 0:22:45.680 it's on very low battery and you go into energy 0:22:45.800 --> 0:22:48.879 saver mode, it'll stop vibrating when you enter keys, and 0:22:48.960 --> 0:22:51.560 it feels very weird. You keep wondering like, wait, did 0:22:51.640 --> 0:22:54.040 that keep did that press? Did it take? In my 0:22:54.119 --> 0:22:58.440 old phone? I actually turned that off because the the 0:22:58.920 --> 0:23:00.920