WEBVTT - Your Body as a Computer Interface 0:00:00.160 --> 0:00:07.200 Brought to you by Toyota. Let's go places. Welcome to 0:00:07.360 --> 0:00:15.520 Forward Thinking. Hey there, and welcome to Forward Thinking, the 0:00:15.640 --> 0:00:19.000 podcast that looks in the future and says, I sing 0:00:19.200 --> 0:00:23.360 the Body Electric. I'm Jonathan Strickland, I'm Lauren Voca, and 0:00:23.440 --> 0:00:29.040 I'm Joe McCormick. And guys, this just did di di 0:00:27.320 --> 0:00:30.680 di di di di did I'm sorry it's porky pick 0:00:31.800 --> 0:00:35.879 Laura similar no, no, no breaking news. We got a 0:00:35.920 --> 0:00:41.760 tweet on Twitter from one Chris Newcomb who said, in 0:00:41.800 --> 0:00:45.839 case your listeners didn't know concrete ships, and he provided 0:00:45.840 --> 0:00:48.960 a link and and said, hey, local kids swim around 0:00:48.960 --> 0:00:51.479 this thing for fun. And the link is to a 0:00:51.520 --> 0:00:54.840 wiki entry for the s S. Palo Alto, which is 0:00:54.880 --> 0:00:59.560 a concrete tanker ship from World War World War One. 0:01:00.080 --> 0:01:02.200 Why are we bringing this up? Is it because in 0:01:02.200 --> 0:01:06.080 a recent episode we made jokes about concrete ships. Yes, 0:01:06.160 --> 0:01:08.959 that's exactly what we did. In our Building Materials episode, 0:01:08.959 --> 0:01:10.880 which came out a couple of weeks ago or so, 0:01:11.360 --> 0:01:14.759 we all had a really good lull about how concrete 0:01:14.760 --> 0:01:18.320 ships are completely ludicrous idea that no one would ever 0:01:18.400 --> 0:01:21.880 possibly put into use. I think specifically what happened was 0:01:22.160 --> 0:01:24.880 we were talking about what you should make out of concrete, 0:01:24.880 --> 0:01:28.279 and I said, obviously boats. Yeah, I had no idea 0:01:28.360 --> 0:01:30.800 that this was a real thing, in my defense, because 0:01:30.800 --> 0:01:34.399 I was the person who immediately struck that down. This 0:01:34.480 --> 0:01:38.160 ship was retired like in nineteen nine and then it 0:01:38.280 --> 0:01:42.399 broke in half. So but there are totally ships that 0:01:42.520 --> 0:01:46.120 are made to this day with pharaoh cement, which is 0:01:46.160 --> 0:01:48.840 a type of concrete that's reinforced with like mession rebar 0:01:48.920 --> 0:01:52.640 and stuff like that. Uh so, so that happens, and 0:01:52.800 --> 0:01:55.400 I just wanted to wanted to update you guys important 0:01:55.440 --> 0:01:58.040 news updates. Well, thank you for the info, Chris. I 0:01:58.040 --> 0:02:00.600 I feel much more educated than I was before. And 0:02:00.640 --> 0:02:02.680 I also now feel like I have a magic power 0:02:02.720 --> 0:02:06.240 to make unlikely seeming things real by laughing at them. 0:02:06.600 --> 0:02:10.239 So what if there was a boat made out of uranium? 0:02:13.800 --> 0:02:16.000 You know what. As as funny as that is and 0:02:16.040 --> 0:02:17.640 as much as I would love to dwell on it, 0:02:17.720 --> 0:02:19.600 I I did. I did a little bit of research 0:02:19.840 --> 0:02:23.920 on a totally different topic. Uh yeah. Yeah. First of all, 0:02:24.160 --> 0:02:26.600 thanks again Chris for sending that message. And we we 0:02:26.639 --> 0:02:29.040 really love hearing from you guys, and it was awesome 0:02:29.120 --> 0:02:32.360 learning something that we thought was ridiculous. Up today, we're 0:02:32.400 --> 0:02:35.400 gonna talk about something else that at times comes across 0:02:35.400 --> 0:02:38.360 as a little ridiculous, which is the idea of what 0:02:38.520 --> 0:02:41.680 is the future of the kind of the interface that 0:02:41.720 --> 0:02:46.720 we use between us and our technology. Specifically, what happens 0:02:46.760 --> 0:02:52.240 when we turn ourselves into that interface. Yes, but in 0:02:52.360 --> 0:02:56.320 your face is what happens. I guess that kind of is. 0:02:56.360 --> 0:02:58.600 I wanted to do you guys have any like really 0:02:58.639 --> 0:03:03.880 good terror will interface stories? Well, I mean, just here, 0:03:04.120 --> 0:03:07.560 did you have a favorite terrible interface? To me, it's 0:03:07.680 --> 0:03:09.760 it's not so much a terrible interface as it was 0:03:09.800 --> 0:03:13.119 a frustrating process of learning how to use it. I'm 0:03:13.200 --> 0:03:17.119 left handed, and I'm old enough to remember personal computers 0:03:17.160 --> 0:03:20.040 before the mouse, and when the mouse came along, and 0:03:20.080 --> 0:03:24.280 then suddenly the mouse was absolutely required in order for 0:03:24.320 --> 0:03:28.040 you to be able to to navigate through software, it 0:03:28.160 --> 0:03:32.320 became very difficult for me. Like other folks were picking 0:03:32.360 --> 0:03:34.160 up on it very quickly, for me, it was more 0:03:34.200 --> 0:03:36.680 work because I didn't have that kind of fine tuned 0:03:36.760 --> 0:03:38.560 precision with my right hand the way I do with 0:03:38.640 --> 0:03:41.400 my left hand, and they didn't have left handed mice, 0:03:42.280 --> 0:03:44.240 and and by the time they did, I was so 0:03:44.360 --> 0:03:46.440 used to using my right hand. For that, I couldn't 0:03:46.800 --> 0:03:49.600 use a mouse left handed. I mean I it felt 0:03:49.640 --> 0:03:53.960 wrong and and nonintuitive because I had trained myself how 0:03:53.960 --> 0:03:56.280 to use it with my right hand. But for me, 0:03:56.720 --> 0:04:01.640 that interface initially at any rate, was not great. But 0:04:01.720 --> 0:04:06.320 that was again due to my own personal uh, left handedness, 0:04:06.360 --> 0:04:09.520 my sinister state of being. You know, I think you've 0:04:09.560 --> 0:04:14.320 probably had experiences with other maybe awkward interfaces. What about 0:04:14.320 --> 0:04:18.320 Google Glass? Yeah, Google Glass. Actually I was all right 0:04:18.320 --> 0:04:21.240 with Google Glass because I knew going into it what 0:04:21.440 --> 0:04:25.400 the interface was going to be like. But in general, 0:04:25.440 --> 0:04:28.280 actually Google is a great example. Just in general, Google, 0:04:28.600 --> 0:04:33.279 uh is a company that is clearly populated by engineers 0:04:33.560 --> 0:04:36.400 who have a very specific idea of how to solve 0:04:36.440 --> 0:04:39.320 a problem which may or may not translate to any 0:04:39.360 --> 0:04:43.200 other human beings experience. And so when you use a 0:04:43.200 --> 0:04:46.159 Google product, you have to kind of learn how to 0:04:46.240 --> 0:04:49.160 think in the way the engineers were thinking when they 0:04:49.200 --> 0:04:53.120 designed it, and then it works. But initially it can 0:04:53.160 --> 0:04:56.840 be very difficult to kind of suss out what you're 0:04:56.839 --> 0:04:58.800 supposed to do or how you're supposed to get your 0:04:58.800 --> 0:05:01.280 technology to do the thing you wanted to do. Yeah, 0:05:01.360 --> 0:05:03.080 we'll show I mean there's a learning curve to any 0:05:03.160 --> 0:05:06.240 kind of interface that you use to to to use technology. 0:05:06.320 --> 0:05:09.640 I'm still completely mystified by the N sixty four controller 0:05:11.320 --> 0:05:15.159 designed for someone with three hands. I just speak about it. 0:05:15.160 --> 0:05:17.760 It just makes me frustrated. It just makes me feel 0:05:17.760 --> 0:05:22.560 like I'm about to lose and get a turtle shell, right, 0:05:23.400 --> 0:05:27.440 Or the old or the very old Microsoft Xbox Duke controller, 0:05:27.520 --> 0:05:32.160 which was roughly the size of a Volkswagen Beetle like 0:05:32.440 --> 0:05:34.719 some of those, or you'll think about some of the 0:05:34.760 --> 0:05:39.120 really frustrating interfaces that were meant to be groundbreaking, like 0:05:39.320 --> 0:05:41.720 the power glove. I mean, I don't know if you 0:05:42.320 --> 0:05:45.720 guys might be too young to appreciate what a terrible, 0:05:46.720 --> 0:05:49.159 terrible product that was. I never I never owned one. 0:05:49.279 --> 0:05:51.760 I don't think I even knew anyone who had heard 0:05:51.839 --> 0:05:55.039 tales I played with one and it was you would 0:05:55.160 --> 0:05:58.120 rapidly go from this looks so cool on me too, 0:05:58.480 --> 0:06:01.560 this is completely are useless if I want to actually 0:06:01.560 --> 0:06:04.279 play a game. Um. Yeah, there are a lot of 0:06:04.320 --> 0:06:07.119 examples of interfaces out there that got in the way, 0:06:07.720 --> 0:06:10.120 and really what we're trying trying to talk about today 0:06:10.800 --> 0:06:14.520 is the attempt to get the interface out of the 0:06:14.560 --> 0:06:18.000 way to have a seamless interaction between us and the 0:06:18.000 --> 0:06:22.680 technology that we depend upon and want to use. Yeah, okay, 0:06:22.680 --> 0:06:25.120 so I guess we should do a quick bit of 0:06:25.440 --> 0:06:28.440 definition just in case you haven't been following us so 0:06:28.520 --> 0:06:30.880 much so far. You probably have, but just to be clear, 0:06:31.120 --> 0:06:33.760 what is an interface. It's a system that controls in 0:06:33.800 --> 0:06:37.800 putting output. It's the interaction between a human and a computer. 0:06:38.279 --> 0:06:40.920 And so this can be hardware or software. The hardware 0:06:40.920 --> 0:06:43.799 would be things like a screen where you see what's 0:06:43.800 --> 0:06:46.080 coming out of the computer. You can know what the 0:06:46.080 --> 0:06:49.320 computer is doing for you. And hardware input like a 0:06:49.360 --> 0:06:52.839 mouse or keyboard. Uh. And sometimes you can combine input 0:06:52.839 --> 0:06:55.560 and output into a single device, for example a touch screen. 0:06:56.040 --> 0:07:00.320 Classic example in putting output in the same object. But 0:07:00.400 --> 0:07:03.600 interfaces can also be software. So the classic example is 0:07:03.640 --> 0:07:06.440 the graphical user interface. Like when you go and use 0:07:06.520 --> 0:07:13.000 Microsoft Windows, you're interacting with memory in the computer through pictures. 0:07:13.400 --> 0:07:16.760 You know, you move files around into different folders. Really 0:07:16.800 --> 0:07:20.040 that's data coded to different locations in the memory, but 0:07:20.080 --> 0:07:23.280 there's a graphical representation of it for to make it 0:07:23.320 --> 0:07:27.520 easier for you. You're also executing programs that are represented 0:07:27.680 --> 0:07:31.280 as a some sort of graphic Uh. You know, of course, 0:07:31.320 --> 0:07:35.200 if you were using computers before goo ease became a 0:07:35.240 --> 0:07:38.440 big thing, then you were typing all those commands out 0:07:38.440 --> 0:07:40.720 and you had to remember what all the different commands 0:07:40.720 --> 0:07:42.840 were in order for you to do things like navigate 0:07:42.920 --> 0:07:46.200 to the right directory file directory to execute a file. 0:07:47.320 --> 0:07:50.920 But the the graphic user interface ends up simplifying that 0:07:51.000 --> 0:07:56.200 by creating this visually oriented approach to interfacing with the computer. Yeah, 0:07:56.200 --> 0:07:58.520 and so if you look at the history of computing, 0:07:58.560 --> 0:08:02.120 it's clear that interfaces are always changing, but not necessarily 0:08:02.160 --> 0:08:05.360 at a constant rate, not like at the rate that 0:08:05.520 --> 0:08:09.280 processing power seems to steadily multiply over time. Right. Yeah, 0:08:09.960 --> 0:08:12.640 this is another great example. We've talked about this when 0:08:12.680 --> 0:08:15.520 we mentioned Kurt's Wild and Kurt's Wild's look at things 0:08:15.520 --> 0:08:18.320 like Moore's law, and you start to try and uh 0:08:18.440 --> 0:08:21.280 and and draw conclusions about what the future is going 0:08:21.320 --> 0:08:23.440 to be like when by using Moore's law as your 0:08:23.480 --> 0:08:28.640 starting point. But that is really deceptive because, like you're saying, Joe, 0:08:29.080 --> 0:08:33.160 not everything and not everything progresses at that same speed, 0:08:34.000 --> 0:08:36.040 right well, and and that speed in particular is a 0:08:36.040 --> 0:08:40.120 little bit uh what's the word self? Oh, there's self fulfilling. Yeah, 0:08:40.120 --> 0:08:42.880 it's a self fulfilling prophecy, because no engineer wants to 0:08:42.920 --> 0:08:46.840 be in the generation that let Moore's Law die, you know, Like, no, 0:08:47.000 --> 0:08:49.400 we've got to figure out another way to double the 0:08:49.600 --> 0:08:53.480 processing power of this computer within the next eight to 0:08:53.559 --> 0:08:55.680 twenty four months. Yeah, but but no one has figured 0:08:55.679 --> 0:08:59.320 out how to double the mouse. Right, Hey, guys, I 0:08:59.360 --> 0:09:01.319 came up with it, a taped a mouse on top 0:09:01.360 --> 0:09:05.280 of another mouse. It's double mouse. Doesn't really work that way. 0:09:05.320 --> 0:09:09.360 So early computers didn't have a monitor or display, right, 0:09:09.720 --> 0:09:12.520 You would get your output in some other format, Like 0:09:12.559 --> 0:09:14.920 it could be punch cards. You could get a series 0:09:14.920 --> 0:09:17.360 of punch cards. You've run your your program through. Your 0:09:17.360 --> 0:09:19.960 input was punch cards, your output is a different set 0:09:19.960 --> 0:09:22.839 of punch cards, and that's your compiled program. That kind 0:09:22.880 --> 0:09:25.720 of stuff. Or you might get like a printer that 0:09:25.800 --> 0:09:30.400 prints along along uh strip of paper like it like 0:09:30.840 --> 0:09:34.240 tape essentially is what it ends up looking like. Actually, 0:09:34.320 --> 0:09:38.360 a friend of mine, Richard Garriott, he's known as he's 0:09:38.559 --> 0:09:41.360 a game designer. His first game that he ever designed 0:09:41.800 --> 0:09:45.080 printed on tape like that. So every move you made 0:09:45.080 --> 0:09:48.480 in his little dungeon based crawler, it would print out 0:09:48.960 --> 0:09:52.440 what that looked like. It was just a very simplified 0:09:53.120 --> 0:09:55.480 representation of a dungeon, and when you would make a move, 0:09:55.640 --> 0:09:58.720 it would have to print another sheet out to show 0:09:58.760 --> 0:10:00.560 you what had happened. The rich the whole idea of 0:10:00.600 --> 0:10:03.520 the interface of the universal touring machine was a strip 0:10:03.559 --> 0:10:06.960 of paper and which in which calculations would be done 0:10:06.960 --> 0:10:09.839 one at a time, printed on a long strip of paper. Yeah. 0:10:10.200 --> 0:10:14.400 So eventually we of all beyond that. We got monitors 0:10:14.440 --> 0:10:19.160 and displays. Uh, we got keyboards, which were much easier 0:10:19.200 --> 0:10:21.480 to use as an interface with a computer as opposed 0:10:21.520 --> 0:10:24.000 to just a collection of punch cards. Later on we 0:10:24.080 --> 0:10:29.400 got the mouse UM. Xerox ended up Xerox's Park department 0:10:29.520 --> 0:10:32.800 figured out the mouse and the graphics user interface, although 0:10:32.800 --> 0:10:35.079 of course it was Apple that took great advantage of 0:10:35.120 --> 0:10:39.679 that with the McIntosh UM, and so that became like 0:10:39.720 --> 0:10:42.640 the standard interface for computers and the mouse and keyboard 0:10:43.280 --> 0:10:48.840 for a really long time. Was that was the input? Yeah, 0:10:48.880 --> 0:10:51.720 I mean you would you had some other like fringe 0:10:51.840 --> 0:10:55.680 input systems, things like light pens and stuff. But yeah, 0:10:55.880 --> 0:10:59.000 but the enjoy besides the joystick, the general public really 0:10:59.040 --> 0:11:03.440 didn't interact dance Revolution pad Yeah, Now these days, we 0:11:03.440 --> 0:11:05.880 we've gotten to a point where we're seeing a real revolution, 0:11:06.000 --> 0:11:11.800 interfaces revolution, right, It's weird that we think of that 0:11:11.840 --> 0:11:15.679 we think of like keyboards and mice, mice, mouses, whichever 0:11:15.720 --> 0:11:18.959 it is. Um, this is standard, the standard way to 0:11:19.000 --> 0:11:23.199 control input right now. Screens are still pretty much paramount. 0:11:23.280 --> 0:11:25.920 But i'd say that, you know, I bet the majority 0:11:26.000 --> 0:11:29.800 of our web traffic comes from touch screen devices, not 0:11:30.480 --> 0:11:33.600 mouse and keyboard driven devices. That's absolutely correct, and you 0:11:33.640 --> 0:11:36.120 can see it by looking at the metrics. Um. Yeah, 0:11:36.160 --> 0:11:39.280 we're getting tons of traffic through mobile, and mobile in 0:11:39.320 --> 0:11:42.800 general is using touch screens. Now, you could also use 0:11:43.080 --> 0:11:45.320 voice commands for a lot of that mobile stuff if 0:11:45.320 --> 0:11:49.439 you were so inclined, just your commands to say, okay, Google, 0:11:49.960 --> 0:11:53.160 how stuff works? Dot Com. I apologize. If you're listening 0:11:53.200 --> 0:11:55.400 to this on an Android device and you have the 0:11:55.440 --> 0:11:59.160 speaker active, oh, you could do just your control through 0:11:59.160 --> 0:12:02.160 an Xbox Cannet Act or something like that, and they're 0:12:02.200 --> 0:12:05.040 the leap controller for PCs. There are a lot of 0:12:05.200 --> 0:12:07.160 the examples of that. We'll talk a little bit more 0:12:07.200 --> 0:12:10.040 about gest your controls in a bit, but but once 0:12:10.080 --> 0:12:13.080 you get into gest your control, you're entering a new 0:12:13.160 --> 0:12:19.000 kind of territory, aren't you, Because they're the issue is uh, well, 0:12:19.040 --> 0:12:22.160 think about it like this. You're you're using the body 0:12:22.280 --> 0:12:26.400 itself as part of an interface with a machine. So 0:12:26.559 --> 0:12:29.040 using the bodies an interface. It's an interesting and kind 0:12:29.040 --> 0:12:32.080 of counterintuitive idea, since an interface is supposed to be 0:12:32.120 --> 0:12:36.120 the bridge between the computer and the power of the 0:12:36.120 --> 0:12:39.000 computer and you, the user, what you're getting out of it. 0:12:39.040 --> 0:12:40.920 But if you think about it, we've been bridging this 0:12:40.960 --> 0:12:44.560 gap for so long with physical devices that are connected 0:12:44.679 --> 0:12:48.880 to the computer. Why not flip the script and build 0:12:48.920 --> 0:12:52.440 a bridge in a place that's physically connected to the user. 0:12:53.600 --> 0:12:57.560 And we've seen some some examples of that as well. 0:12:58.320 --> 0:13:02.800 You could argue that the ore headsets are are getting 0:13:02.800 --> 0:13:06.000 into that where you are are wearing the computer device 0:13:06.480 --> 0:13:10.960 and your physical motions are what allow you to experience 0:13:11.080 --> 0:13:14.439 that computer power in the way it was intended. Sure, 0:13:14.520 --> 0:13:18.200 or the aforementioned connect sensors, You're you're using your body 0:13:18.280 --> 0:13:23.240 to interact, Yeah, exactly. So, uh, you know, we're gonna 0:13:23.240 --> 0:13:26.319 talk a lot about that stuff in more detail a 0:13:26.320 --> 0:13:28.440 little bit later. We're also going to talk about not 0:13:28.600 --> 0:13:32.640 just ways where you are interacting, you know, in order 0:13:32.679 --> 0:13:36.719 to create input into a device, but also how you 0:13:36.760 --> 0:13:40.199 experience the output from that device. Right yeah, uh, so 0:13:40.440 --> 0:13:44.160 you know we should mention some basic ideas in what 0:13:44.160 --> 0:13:47.000 what what's on offer here in terms of the body 0:13:47.120 --> 0:13:49.839 is an interface, so the input is probably the more 0:13:49.880 --> 0:13:54.480 obvious one with input, Instead of pressing buttons on external device, 0:13:54.600 --> 0:13:57.960 moving a mouse or whatever, you might simply perform an 0:13:57.960 --> 0:14:01.200 independent action by and of your own body. So this 0:14:01.240 --> 0:14:05.760 could be gestures, movements, poking yourself, wiggling a part of 0:14:05.760 --> 0:14:10.640 your body, wiggling multiple parts of your body, parts of 0:14:10.720 --> 0:14:14.079 other people's bodies. No, see, then it wouldn't be it 0:14:14.120 --> 0:14:16.520 wouldn't That wouldn't quite meet the criteria. I think, well, 0:14:16.600 --> 0:14:18.360 it's still be a body interface, it just wouldn't be 0:14:18.360 --> 0:14:23.400 your body advocated. Have a dead body. I should have 0:14:23.560 --> 0:14:26.040 a Bernie device that reminds me of a movie that's 0:14:26.080 --> 0:14:29.000 coming out the go ahead. I think a complicated system 0:14:29.040 --> 0:14:32.160 of shrugs would be really good, right yeah, right, so 0:14:32.240 --> 0:14:34.400 you never have to lose your cool while you're controlling 0:14:34.400 --> 0:14:37.359 your phone. I meant to, I meant to do the 0:14:37.360 --> 0:14:40.120 the please tell me more shrug, but it turned out 0:14:40.160 --> 0:14:43.640 I just did the shrug or a combination of side 0:14:43.640 --> 0:14:47.520 eye and shrug. Anyway, the key ideas that you don't 0:14:47.560 --> 0:14:50.320 have to touch or manipulate anything except your own body. 0:14:50.360 --> 0:14:52.520 You've got it with you all the time. So there 0:14:52.560 --> 0:14:55.760 you go. And it's not this This idea isn't super 0:14:55.800 --> 0:14:58.160 weird to us because we're already familiar with stuff like 0:14:58.200 --> 0:15:01.000 the connect and gest your controls to some extent. Then 0:15:01.000 --> 0:15:04.280 if they're not super awesome yet, but then you've also 0:15:04.320 --> 0:15:07.200 got output. So instead of having to look at a 0:15:07.320 --> 0:15:11.200 screen that's attached to an external device, which would cover 0:15:11.320 --> 0:15:14.880 the vast majority of output today, I'm having trouble even 0:15:14.920 --> 0:15:17.440 thinking of a standard device that has a very different 0:15:17.480 --> 0:15:20.640 way of doing it than this. Well, I mean there's 0:15:20.680 --> 0:15:24.720 a growing list of devices that now are using audio, 0:15:25.400 --> 0:15:29.040 so things like Amazon's Echo, right that that would be Yeah, 0:15:29.080 --> 0:15:31.680 that's a good example. But but I get what you're saying. Yes, 0:15:31.720 --> 0:15:34.520 the vast majority, I would say, are are visually oriented. 0:15:34.960 --> 0:15:38.080 So yeah, instead of that, information about your computing task 0:15:38.280 --> 0:15:41.720 is made available directly to your body. The classic sci 0:15:41.720 --> 0:15:45.120 fi example of this would be this internal retina display. 0:15:45.200 --> 0:15:48.440 The screen is projected directly onto your retina. But I 0:15:48.480 --> 0:15:50.840 mean that's a little crazy. We probably won't have anything 0:15:50.920 --> 0:15:53.040 like that for a long time. If ever. Now we 0:15:53.120 --> 0:15:55.360 have some other examples that we'll talk about when we 0:15:55.400 --> 0:15:58.840 get to a haptics because that's one of the other 0:15:58.920 --> 0:16:02.280 methods of getting back from a computer that can be meaningful. 0:16:02.600 --> 0:16:05.800 It's just not visual. Yeah. So I would say the 0:16:05.880 --> 0:16:11.280 middle step between standard input and output devices, standard interfaces 0:16:11.360 --> 0:16:14.480 and this your own body as an interface would be 0:16:14.520 --> 0:16:18.720 wearables because that's it's getting close to your own body, 0:16:18.760 --> 0:16:21.040 but it's not quite your own body yet. Yeah, it 0:16:21.040 --> 0:16:24.400 could be something that is unobtrusive where you might not 0:16:24.520 --> 0:16:28.600 even think about it consciously after a while after wearing it. Yeah, sure, 0:16:28.600 --> 0:16:30.920 like a like a fitbit or the pieces of jewelry 0:16:30.920 --> 0:16:33.360 that they're coming out with something like that. Absolutely, that 0:16:33.440 --> 0:16:36.280 was a great example, and fitbit is in fact a 0:16:36.320 --> 0:16:39.800 fantastic example because so much of that interface is invisible 0:16:39.920 --> 0:16:43.480 to you. That again it's the idea of removing that barrier. 0:16:43.560 --> 0:16:45.920 So a fitbit is going to be tracking your steps. 0:16:45.960 --> 0:16:47.840 You might have other wearables that are doing things like 0:16:47.880 --> 0:16:51.440 tracking your heart rate, uh, that sort of stuff, where 0:16:51.720 --> 0:16:55.520 the data is going to some form of cloud based 0:16:55.560 --> 0:16:58.880 solution or or potentially just being beamed to a local 0:16:59.560 --> 0:17:04.240 UM advice. Like a smartphone or tablet, you're still usually 0:17:04.280 --> 0:17:07.720 dependent upon that other device in order to be able 0:17:07.760 --> 0:17:10.840 to consume the data in some way. It's presented to 0:17:10.880 --> 0:17:13.320 you in some way, so it's not like it's directly 0:17:13.440 --> 0:17:17.280 getting that data to you through the device itself. You're 0:17:17.119 --> 0:17:19.880 you might have a display on the device that gives 0:17:19.920 --> 0:17:22.800 you some of the basic information, but your body is 0:17:22.840 --> 0:17:27.199 not acting as the display, right, it's still the device. UM. 0:17:27.240 --> 0:17:30.200 It does allow us to have other means of interacting 0:17:30.200 --> 0:17:32.840 with our technology. Some wearables, you could argue, like the 0:17:32.920 --> 0:17:37.560 Nintendo Power Glove was a wearable, particularly good one, but 0:17:37.720 --> 0:17:41.960 it was a wearable. It was not not unobtrusive, not 0:17:42.200 --> 0:17:44.800 you know, it was definitely you knew someone was wearing one. 0:17:46.480 --> 0:17:49.280 But it allowed well that was part of the point, right, 0:17:49.320 --> 0:17:51.080 You wanted to show off that you were playing with 0:17:51.160 --> 0:17:55.520 power Yeah, exactly, and you had a glove to p 0:17:55.960 --> 0:17:57.760 and you looked a little bit like Michael Jackson in 0:17:57.760 --> 0:17:59.840 that air a little bit, yeah, which at the time 0:18:00.080 --> 0:18:03.280 is really importantly Yeah, because if we couldn't get the jacket, 0:18:03.280 --> 0:18:05.880 we could at least get the power glove. But the 0:18:05.840 --> 0:18:09.680 the all remember the nightmare on Elm Street movie where 0:18:09.760 --> 0:18:15.840 Freddie wears the power Glove. I remember seeing it, don't 0:18:15.880 --> 0:18:20.960 from my mind? I okay, definitely. Oh god, I was 0:18:21.000 --> 0:18:23.280 so worried about myself for a second there. Okay, Now 0:18:23.320 --> 0:18:26.360 everything's gonna be fine. You guys late at six though, 0:18:26.359 --> 0:18:28.760 I think that probably are on four. But at any rate, 0:18:28.800 --> 0:18:32.080 I get what you're saying. Um. Yeah, So so one 0:18:32.119 --> 0:18:33.679 of the things I wanted to talk about this is 0:18:33.720 --> 0:18:36.879 kind of a This is looking ahead at wearables. So 0:18:36.960 --> 0:18:39.960 you could have wearables that are are something that you 0:18:40.040 --> 0:18:42.959 don't interface with directly at all. It could be you know, 0:18:42.960 --> 0:18:45.480 we've we've talked about the possibility of things like r 0:18:45.560 --> 0:18:48.760 F I D chips that have a profile. This is 0:18:48.800 --> 0:18:50.240 sort of the sort of thing that Bill Gates was 0:18:50.280 --> 0:18:52.440 putting in his house where you would get a little 0:18:52.560 --> 0:18:55.879 r F I D D badge that would have a 0:18:55.960 --> 0:18:59.600 profile programmed into it that's personalized to you, and then 0:18:59.640 --> 0:19:02.080 you're experience as you walk through his house would be 0:19:02.320 --> 0:19:04.240 to see the kind of art that you like, to 0:19:04.320 --> 0:19:06.600 hear the kind of music you like. The lighting condition 0:19:06.600 --> 0:19:09.919 would be to your preference. Uh, it would be dependent 0:19:10.000 --> 0:19:12.800 upon that profile. We've since reached a point where we 0:19:12.840 --> 0:19:14.680 can get a little more advanced than that. You don't 0:19:14.720 --> 0:19:17.200 necessarily have to have a wearable anymore for that kind 0:19:17.200 --> 0:19:21.880 of stuff. But that was one implementation. Another however, is this, uh, 0:19:22.040 --> 0:19:27.560 this this haptics feedback solution that I had been talking about, 0:19:27.600 --> 0:19:31.879 so being having to do with your sense of touch exactly. 0:19:31.960 --> 0:19:36.160 So we already are familiar with technology that has haptic feedback. 0:19:36.280 --> 0:19:38.760 Here's one you're very likely to be familiar with. If 0:19:38.760 --> 0:19:41.280 you ever played a video game where the controller buzzes 0:19:41.280 --> 0:19:43.840 in your hand when you do something right. That's the 0:19:43.880 --> 0:19:46.720 old rumble pack, right. Those have been around for for 0:19:47.200 --> 0:19:50.399 a couple of generations of video game consoles and also 0:19:50.440 --> 0:19:54.160 for PC controllers, and generally speaking, you you want to 0:19:54.400 --> 0:19:59.600 have a controller that enhances the experience of playing a game, 0:19:59.680 --> 0:20:02.480 so it might be a great example would be a 0:20:02.480 --> 0:20:05.439 stealth based game where you're you're skulking around in the 0:20:05.480 --> 0:20:09.000 shadows and your controller might start to vibrate to indicate 0:20:09.040 --> 0:20:12.840 that perhaps you are visible or potentially visible to an enemy, 0:20:12.840 --> 0:20:15.400 so you need to get back into cover. Yeah, yeah, 0:20:15.440 --> 0:20:18.320 a vibration being being like your Spidey sense going on. Yeah, 0:20:18.880 --> 0:20:21.000 Or if you're if you're playing a horror game and 0:20:21.119 --> 0:20:23.320 your your life starts getting too low and you start 0:20:23.359 --> 0:20:26.960 feeling your heartbeat through the controller, and that lets you 0:20:27.000 --> 0:20:28.840 know that you need to drink a health potion or 0:20:29.040 --> 0:20:31.720 you know, just to spell whatever it is, right, or 0:20:31.760 --> 0:20:36.080 unplug the game and going to the corner. Yeah. Uh, 0:20:36.200 --> 0:20:38.199 if pyramid Head is coming around the corner, you just 0:20:38.240 --> 0:20:39.720 want to, like, I just I just need to go 0:20:39.760 --> 0:20:43.160 and read a happy book for a while. Uh. Or 0:20:43.200 --> 0:20:45.520 you know. Another one that everyone is probably familiar with 0:20:45.920 --> 0:20:50.880 are the vibrating motors in uh, in smartphones or cell phones. Yeah, yeah, right, 0:20:50.920 --> 0:20:54.520 And that's a very simple Yeah. Yeah. They maybe they 0:20:54.600 --> 0:20:56.960 vibrate when you're doing an input, or they vibrate to 0:20:57.000 --> 0:20:58.680 alert you that a call is coming in. But that's 0:20:58.760 --> 0:21:03.000 that's the happy feedback, very basic application of haptic feedback. 0:21:03.080 --> 0:21:05.480 I don't know if you've ever had the experience of 0:21:05.920 --> 0:21:08.639 getting so used to this that it's weird when it 0:21:08.680 --> 0:21:11.280 doesn't happen. I've had this experience with my phone where 0:21:11.320 --> 0:21:13.720 I don't even notice anymore that when I punch a 0:21:13.800 --> 0:21:16.880 key to like enter, you know, to enter a letter 0:21:16.960 --> 0:21:19.280 on a text message or something like that, the phone 0:21:19.400 --> 0:21:21.639 vibrates a little to register like, yeah, I got that, 0:21:21.760 --> 0:21:24.159 I got that. Letter uh. And if the it's on 0:21:24.280 --> 0:21:27.000 very low battery and you go into energy saver mode, 0:21:27.000 --> 0:21:29.919 it'll stop vibrating when you enter keys, and it feels 0:21:30.000 --> 0:21:32.560 very weird. You keep wondering like, wait, did that keep? 0:21:32.680 --> 0:21:35.080 Did that press? Did it take? In my old phone, 0:21:35.119 --> 0:21:39.760 I actually turned that off because the the it was 0:21:39.920 --> 0:21:41.840 reminding me of that episode of the I T. Crowd 0:21:41.840 --> 0:21:45.760 where they soup up Roy's vibrating motor in his cell phone. 0:21:45.840 --> 0:21:48.200 Because every time I would type in a letter, it 0:21:48.280 --> 0:21:50.440 made a really loud, like eat noise, to the point 0:21:50.440 --> 0:21:53.080 where if I wanted to check something out and my 0:21:53.119 --> 0:21:55.440 wife was napping, I would wake her up. So I 0:21:55.480 --> 0:21:59.159 finally turned it off. My current phone much more subtle, 0:21:59.240 --> 0:22:01.320 so I'm all right with it. I've never had a 0:22:01.359 --> 0:22:03.679 phone that did that. Although it did, it did scare 0:22:03.720 --> 0:22:06.280 me every time I was I used to I used 0:22:06.320 --> 0:22:08.600 to have a fitbit that I would wear constantly, and 0:22:08.640 --> 0:22:11.000 whenever I went over ten thousand steps in the day, 0:22:11.080 --> 0:22:13.480 it would it would do this like buzz buzz buzz. Yeah, 0:22:13.720 --> 0:22:16.119 party times and You're thinking, I'm having a heart attack. 0:22:18.600 --> 0:22:24.200 Make what's going on? Sometimes sometimes the acclamation period takes 0:22:24.240 --> 0:22:27.520 a little longer for certain types of technology than others. Well, 0:22:27.680 --> 0:22:29.280