WEBVTT - The Google Glass Story

0:00:04.160 --> 0:00:07.160
<v Speaker 1>Get in touch with technology with tech Stuff from how

0:00:07.240 --> 0:00:14.280
<v Speaker 1>stuff works dot com. Hey there, and welcome to tech Stuff.

0:00:14.320 --> 0:00:17.920
<v Speaker 1>I am your host, Jonathan Strickland. I am a senior

0:00:18.040 --> 0:00:22.360
<v Speaker 1>writer with the website how stuff works dot com. And

0:00:22.560 --> 0:00:26.280
<v Speaker 1>as always, I like to talk about technology, especially on

0:00:26.320 --> 0:00:30.520
<v Speaker 1>this show. That's why it's called tech Stuff, and I'm

0:00:30.520 --> 0:00:32.920
<v Speaker 1>going to talk about subject that I've touched on in

0:00:33.000 --> 0:00:35.520
<v Speaker 1>past episodes. In fact, we did a full episode about

0:00:35.520 --> 0:00:38.960
<v Speaker 1>this subject. I'm talking about Google Glass. And while we

0:00:39.000 --> 0:00:42.839
<v Speaker 1>did do an older episode about this, I felt like

0:00:43.280 --> 0:00:46.720
<v Speaker 1>we could really use a chance to revisit this and

0:00:46.720 --> 0:00:49.640
<v Speaker 1>and kind of talk about in the more modern style

0:00:49.720 --> 0:00:52.320
<v Speaker 1>of this show. You might remember, the old version of

0:00:52.400 --> 0:00:55.120
<v Speaker 1>tech Stuff was more conversational and this one's less, so

0:00:55.160 --> 0:00:59.560
<v Speaker 1>it's more narrative. Well, Google Glass was a big augmented

0:00:59.600 --> 0:01:02.480
<v Speaker 1>reality the project or an a our project out of

0:01:02.520 --> 0:01:05.480
<v Speaker 1>Google's R and D labs, the Google x labs, that's

0:01:05.520 --> 0:01:09.479
<v Speaker 1>the super secret research and development branch of Google. And

0:01:09.600 --> 0:01:11.880
<v Speaker 1>it probably was a little bit ahead of its time.

0:01:11.920 --> 0:01:15.000
<v Speaker 1>In fact, it really was ahead of its time, and

0:01:15.040 --> 0:01:17.679
<v Speaker 1>it was purposefully ahead of its time. That was part

0:01:17.720 --> 0:01:21.000
<v Speaker 1>of the problem. But I'm getting ahead of myself. It

0:01:21.280 --> 0:01:24.680
<v Speaker 1>might have suffered from some poor design and implementation, or

0:01:24.680 --> 0:01:28.760
<v Speaker 1>at least some choices that perhaps puzzled people. I wouldn't

0:01:28.800 --> 0:01:30.800
<v Speaker 1>go so far as to call them poor myself. I

0:01:30.800 --> 0:01:34.119
<v Speaker 1>actually really liked Google Glass. Maybe it was just too

0:01:34.160 --> 0:01:38.480
<v Speaker 1>darned expensive. It's pretty pretty costly. But whatever the reason,

0:01:38.560 --> 0:01:41.880
<v Speaker 1>and we'll explore all of them. It's no longer a

0:01:41.880 --> 0:01:45.560
<v Speaker 1>consumer product that you can buy from Google. So today

0:01:45.560 --> 0:01:48.560
<v Speaker 1>we're gonna talk about Project Glass, how it got started,

0:01:48.600 --> 0:01:51.720
<v Speaker 1>the technology behind it, and the failed experiment to turn

0:01:51.800 --> 0:01:54.480
<v Speaker 1>it into a consumer product, and where is it now.

0:01:55.480 --> 0:01:58.200
<v Speaker 1>The reason I decided to cover this is because the

0:01:58.200 --> 0:02:01.600
<v Speaker 1>week I'm recording this episode, The Telegraph ran an article

0:02:01.640 --> 0:02:04.800
<v Speaker 1>about some of the biggest flops in technology, and some

0:02:04.880 --> 0:02:07.240
<v Speaker 1>of the usual suspects were in there, like the Nintendo

0:02:07.400 --> 0:02:12.000
<v Speaker 1>Virtual Boy was one of the major flops listed. There

0:02:12.000 --> 0:02:15.640
<v Speaker 1>are also some heartbreaking intreats in there. The Sega Dreamcast,

0:02:15.680 --> 0:02:19.639
<v Speaker 1>for example. I know that's another video game component there,

0:02:19.680 --> 0:02:23.200
<v Speaker 1>a console. In this case, it was legitimately a really

0:02:23.240 --> 0:02:25.720
<v Speaker 1>good video game console. It just didn't do very well

0:02:25.720 --> 0:02:28.720
<v Speaker 1>in the market, but I still have one and it

0:02:28.800 --> 0:02:32.800
<v Speaker 1>was really really good. Then there was Google Glass that

0:02:32.880 --> 0:02:35.040
<v Speaker 1>was also one of the ones that the Telegraph listed

0:02:35.520 --> 0:02:39.320
<v Speaker 1>another heartbreaker. So what's the story behind it? Well, I

0:02:39.360 --> 0:02:44.200
<v Speaker 1>can't talk about Google Glass without first talking about augmented reality,

0:02:44.560 --> 0:02:47.560
<v Speaker 1>can I? You know me? You know I can't. I

0:02:47.600 --> 0:02:51.160
<v Speaker 1>am physically incapable of doing that. I'm sure many of

0:02:51.160 --> 0:02:53.959
<v Speaker 1>you are familiar with the concept of augmented reality or

0:02:54.000 --> 0:02:56.280
<v Speaker 1>a R. But just in case, I'm going to give

0:02:56.320 --> 0:03:00.600
<v Speaker 1>you a quick refresher. So Thomas Couddle gets the credit

0:03:00.680 --> 0:03:04.080
<v Speaker 1>for coining the phrase augmented reality in nineteen nine. He

0:03:04.160 --> 0:03:06.880
<v Speaker 1>was specifically talking about the system that would allow you

0:03:06.919 --> 0:03:10.720
<v Speaker 1>to see where wires needed to be laid out and say,

0:03:10.919 --> 0:03:14.640
<v Speaker 1>the fuselage of an airplane. So if you've ever been

0:03:14.680 --> 0:03:17.480
<v Speaker 1>able to walk into an airplane where it's been stripped

0:03:17.480 --> 0:03:20.080
<v Speaker 1>down so you can see the guts of it. Uh.

0:03:20.440 --> 0:03:23.040
<v Speaker 1>I was recently at an airplane museum where I got

0:03:23.040 --> 0:03:25.400
<v Speaker 1>to do this. I walked through what had been a

0:03:25.440 --> 0:03:29.720
<v Speaker 1>former seven forty seven and now included a section where

0:03:29.760 --> 0:03:33.240
<v Speaker 1>everything got stripped away so you could see essentially the

0:03:33.240 --> 0:03:36.320
<v Speaker 1>bones the skeleton of the seven forty seven, and part

0:03:36.320 --> 0:03:40.440
<v Speaker 1>of that included conduits through which wires would run. Well,

0:03:40.480 --> 0:03:42.640
<v Speaker 1>when you're building one of these airplanes, you need to

0:03:42.680 --> 0:03:45.880
<v Speaker 1>know where those wire conduits have to be so that

0:03:45.920 --> 0:03:48.440
<v Speaker 1>you can make sure they fit into the overall design.

0:03:49.520 --> 0:03:53.240
<v Speaker 1>Caudal worked on systems that would give a digital overlay

0:03:53.360 --> 0:03:57.280
<v Speaker 1>as engineers would look at this airplane design so that

0:03:57.320 --> 0:03:59.720
<v Speaker 1>they could lay the cables the proper way, make sure

0:03:59.720 --> 0:04:02.360
<v Speaker 1>that they were aligned so that they weren't going to

0:04:02.920 --> 0:04:07.480
<v Speaker 1>end up messing up the design some other way. And really,

0:04:07.520 --> 0:04:12.120
<v Speaker 1>augmented reality is just the integration of digital information into

0:04:12.200 --> 0:04:14.800
<v Speaker 1>the real world around us. And you can do this

0:04:14.840 --> 0:04:18.680
<v Speaker 1>in lots of different ways, but typically we talk about

0:04:18.760 --> 0:04:22.360
<v Speaker 1>augmented reality in terms of overlaying some sort of visual

0:04:22.760 --> 0:04:26.720
<v Speaker 1>digital information, like a digital display through which you can

0:04:26.800 --> 0:04:29.800
<v Speaker 1>see a view of the real world, and thus you

0:04:29.839 --> 0:04:33.359
<v Speaker 1>can have some augmented information on top of that view

0:04:33.720 --> 0:04:36.960
<v Speaker 1>of reality. So a good example of this might be

0:04:37.040 --> 0:04:40.040
<v Speaker 1>a fighter pilot who has a helmet that includes a

0:04:40.160 --> 0:04:43.400
<v Speaker 1>digital heads up display or h u D on the

0:04:43.520 --> 0:04:46.120
<v Speaker 1>visor of the helmet itself, so you might be able

0:04:46.160 --> 0:04:51.040
<v Speaker 1>to visualize things like uh Allied aircraft and you'd be

0:04:51.080 --> 0:04:54.200
<v Speaker 1>able to see it and it would be identified within

0:04:54.279 --> 0:04:57.800
<v Speaker 1>your visor so that you get information about that. That's

0:04:58.000 --> 0:05:01.520
<v Speaker 1>a simple example, simple in the sense that you can

0:05:01.520 --> 0:05:04.120
<v Speaker 1>easily imagine it. It's actually quite complicated when you build

0:05:04.160 --> 0:05:08.200
<v Speaker 1>the technology. A few high end cars have similar features

0:05:08.240 --> 0:05:12.080
<v Speaker 1>that give digitally enhanced information that is projected or otherwise

0:05:12.080 --> 0:05:15.719
<v Speaker 1>displayed on the windshield itself, which gives the driver the

0:05:15.720 --> 0:05:18.640
<v Speaker 1>ability to see certain special views. You might be able

0:05:18.640 --> 0:05:21.440
<v Speaker 1>to see, like a infrared view of what is outside

0:05:21.440 --> 0:05:25.240
<v Speaker 1>the car, or a projection of things like the outside temperature,

0:05:25.440 --> 0:05:26.919
<v Speaker 1>that sort of stuff. But it tends to be in

0:05:26.960 --> 0:05:29.520
<v Speaker 1>those luxury cars. You don't see it in a lot

0:05:29.560 --> 0:05:34.880
<v Speaker 1>of the lower production cars, even even the nicer ones.

0:05:35.000 --> 0:05:41.239
<v Speaker 1>It's pretty rare. You just you also have I'm guessing

0:05:41.400 --> 0:05:46.080
<v Speaker 1>an augmented reality device on you. More likely than not

0:05:46.240 --> 0:05:48.839
<v Speaker 1>most of you, I'm sure have smartphones. So if you

0:05:48.880 --> 0:05:51.640
<v Speaker 1>have a smartphone, you have a device that is probably

0:05:51.680 --> 0:05:55.000
<v Speaker 1>capable of running augmented reality apps. There are tons of

0:05:55.040 --> 0:05:57.760
<v Speaker 1>different apps in the a R space for all of

0:05:57.800 --> 0:06:01.800
<v Speaker 1>the major smartphone platforms, iOS and Android being the two

0:06:01.839 --> 0:06:04.159
<v Speaker 1>big ones, but there are ones for other ones as well,

0:06:04.839 --> 0:06:07.160
<v Speaker 1>And typically the way these work is that you hold

0:06:07.160 --> 0:06:11.359
<v Speaker 1>your phone up. Your phones back facing camera pulls in

0:06:11.440 --> 0:06:14.279
<v Speaker 1>a view of the world around you, so it's like

0:06:14.320 --> 0:06:16.880
<v Speaker 1>you're getting a live view It's like your your phone

0:06:16.960 --> 0:06:19.359
<v Speaker 1>is a monitor for you to look at a live

0:06:19.520 --> 0:06:22.039
<v Speaker 1>camera feed of the world around you, but then the

0:06:22.080 --> 0:06:25.200
<v Speaker 1>app allows other digital information to be overlaid on top

0:06:25.240 --> 0:06:27.400
<v Speaker 1>of that view. So it might be something as simple

0:06:27.480 --> 0:06:31.000
<v Speaker 1>as directions of where to go. Let's say you've programmed

0:06:31.000 --> 0:06:33.919
<v Speaker 1>your phone saying I wanna get to this one particular

0:06:33.960 --> 0:06:37.440
<v Speaker 1>coffee shop and it's about six blocks away, and you

0:06:37.480 --> 0:06:39.800
<v Speaker 1>hold your phone up and it tells you, all right,

0:06:39.800 --> 0:06:41.960
<v Speaker 1>you need to go three blocks straight ahead, then you're

0:06:41.960 --> 0:06:46.440
<v Speaker 1>gonna take a right. That's a pretty simple again concept

0:06:46.680 --> 0:06:50.480
<v Speaker 1>for augmented reality, but it could do other stuff too,

0:06:50.520 --> 0:06:51.880
<v Speaker 1>Like you might be able to hold it up to

0:06:51.960 --> 0:06:54.039
<v Speaker 1>a sign that's written in a language you can't read,

0:06:55.000 --> 0:06:56.719
<v Speaker 1>and it might be able to read it and translate

0:06:56.760 --> 0:06:59.360
<v Speaker 1>it for you. We're seeing a lot of translate apps

0:06:59.400 --> 0:07:02.240
<v Speaker 1>that in Core break this kind of augmented reality, and

0:07:02.360 --> 0:07:05.560
<v Speaker 1>it's pretty awesome, at least in my my opinion, is

0:07:05.560 --> 0:07:08.480
<v Speaker 1>pretty awesome. But there are tons of different ways to

0:07:08.520 --> 0:07:12.800
<v Speaker 1>implement augmented reality and just as many different use cases

0:07:12.920 --> 0:07:17.400
<v Speaker 1>for a R. And it ranges from just entertainment to

0:07:17.480 --> 0:07:23.840
<v Speaker 1>productivity to industrial use and beyond medicine. Lots of different

0:07:24.000 --> 0:07:28.720
<v Speaker 1>potential uses for a r now. Google Glass started as

0:07:28.760 --> 0:07:32.160
<v Speaker 1>a head mounted computer device that would incorporate augmented reality

0:07:32.200 --> 0:07:35.200
<v Speaker 1>features into a display that you could look through and

0:07:35.280 --> 0:07:38.200
<v Speaker 1>still see the world beyond. And while the project was

0:07:38.240 --> 0:07:41.520
<v Speaker 1>first teased in a video in two thousand twelve, the

0:07:41.600 --> 0:07:45.560
<v Speaker 1>origins for this project go back much further than that.

0:07:46.280 --> 0:07:49.560
<v Speaker 1>And first, before there was even a Google, there was

0:07:49.600 --> 0:07:53.240
<v Speaker 1>a guy named Thad Starner. I've actually had the good

0:07:53.280 --> 0:07:56.760
<v Speaker 1>fortune to meet Mr Starner because he works at Georgia

0:07:56.800 --> 0:08:00.160
<v Speaker 1>Tech as a professor there, and I visited Georgia Tech.

0:08:00.240 --> 0:08:05.480
<v Speaker 1>I've visited the wearable computing labs, and I've chatted with him.

0:08:05.520 --> 0:08:08.960
<v Speaker 1>He's an interesting dude. And Georgia techt just down the

0:08:09.000 --> 0:08:11.520
<v Speaker 1>street from how stuff works, so it's not hard for

0:08:11.600 --> 0:08:14.080
<v Speaker 1>us to get over there. Well, he also served as

0:08:14.080 --> 0:08:16.600
<v Speaker 1>a technical lead for Google Glass. In fact, I believe

0:08:16.680 --> 0:08:20.080
<v Speaker 1>he served as technical lead longer than anyone else in

0:08:20.080 --> 0:08:23.520
<v Speaker 1>that position for that particular project. And it was Startner's

0:08:23.560 --> 0:08:26.640
<v Speaker 1>work in wearable technology and augmented reality that you could

0:08:26.680 --> 0:08:31.760
<v Speaker 1>say got the ball rolling. So you remember I mentioned

0:08:31.760 --> 0:08:34.720
<v Speaker 1>a guy named Caddle got the credit for coining the

0:08:34.720 --> 0:08:40.080
<v Speaker 1>phrase augmented reality. Well, Starner says that he really coined

0:08:40.080 --> 0:08:44.640
<v Speaker 1>that phrase independently of Caudle also in through a fellowship

0:08:44.640 --> 0:08:47.160
<v Speaker 1>proposal he wrote, and he thinks that that might be

0:08:47.240 --> 0:08:51.360
<v Speaker 1>the first appearance of augmented reality. He wanted to use

0:08:51.400 --> 0:08:55.840
<v Speaker 1>the phrase artificial reality when he was originally talking about

0:08:55.840 --> 0:09:00.000
<v Speaker 1>this concept. However, someone else was already using that term.

0:09:00.160 --> 0:09:02.800
<v Speaker 1>That someone was Timothy Leary, and if you don't know

0:09:02.800 --> 0:09:05.800
<v Speaker 1>who Timothy Learry is, you should look that up. Leary

0:09:05.920 --> 0:09:09.000
<v Speaker 1>was specifically talking about the kind of reality you experience

0:09:09.080 --> 0:09:12.960
<v Speaker 1>when you have partaken in mind altering substances. So it

0:09:13.040 --> 0:09:18.840
<v Speaker 1>wasn't exactly the context that Starner wanted to imply when

0:09:18.840 --> 0:09:21.920
<v Speaker 1>he was talking about his technology, so he didn't adopt

0:09:21.960 --> 0:09:26.120
<v Speaker 1>artificial reality, and he went with augmented reality instead. In

0:09:27.559 --> 0:09:33.040
<v Speaker 1>which was years before Google ever even existed. Starner created

0:09:33.080 --> 0:09:37.520
<v Speaker 1>a wearable display, so it was a display that attached

0:09:37.559 --> 0:09:40.400
<v Speaker 1>to his glasses, and really he worked with other people

0:09:40.440 --> 0:09:43.400
<v Speaker 1>to design this. He didn't build it by himself with

0:09:43.480 --> 0:09:46.240
<v Speaker 1>his own two hands, but he worked with designers to

0:09:46.280 --> 0:09:49.880
<v Speaker 1>create a computer system that incorporated a display that could

0:09:49.880 --> 0:09:53.120
<v Speaker 1>clip onto his glasses. And it was pretty big and bulky,

0:09:53.160 --> 0:09:56.520
<v Speaker 1>and it was not transparent. It was like having a

0:09:56.559 --> 0:10:00.920
<v Speaker 1>small computer monitor mounted on your glass is uh. And

0:10:00.960 --> 0:10:04.640
<v Speaker 1>he started to wear this all the time wherever he went.

0:10:05.840 --> 0:10:10.160
<v Speaker 1>It was kind of an experiment in finding out how

0:10:10.280 --> 0:10:14.200
<v Speaker 1>you might use wearable computers, what elements are important, which

0:10:14.200 --> 0:10:17.840
<v Speaker 1>ones are not important, how do you incorporated into your

0:10:17.920 --> 0:10:21.720
<v Speaker 1>daily life. So he would wear this all the time,

0:10:21.800 --> 0:10:25.000
<v Speaker 1>and it very often would prompt people to ask questions

0:10:25.040 --> 0:10:27.720
<v Speaker 1>about this weird thing that he had on him on

0:10:27.800 --> 0:10:33.120
<v Speaker 1>his face mainly. Eventually there was a build of this

0:10:33.240 --> 0:10:36.720
<v Speaker 1>that started going by a name called the Lizzie. It

0:10:36.800 --> 0:10:40.360
<v Speaker 1>was a wearable computer, complete with input devices and with

0:10:40.480 --> 0:10:46.679
<v Speaker 1>that head malond display that again was kind of unsightly originally. Anyway,

0:10:48.120 --> 0:10:53.520
<v Speaker 1>this display was able to show a resolution of seven pixels,

0:10:53.600 --> 0:10:57.439
<v Speaker 1>so tiny resolution compared to what you would find today,

0:10:57.480 --> 0:11:01.720
<v Speaker 1>the very low resolution compared to today's screens. It was

0:11:01.720 --> 0:11:06.760
<v Speaker 1>also monochromatic, so only one color. And connected to that

0:11:07.280 --> 0:11:11.040
<v Speaker 1>was a one handed keyboard called a twiddler, which I

0:11:11.080 --> 0:11:14.160
<v Speaker 1>wish were a joke, but it is not. So it

0:11:14.200 --> 0:11:16.480
<v Speaker 1>was a little one handed twiddler keyboard. It kind of

0:11:16.720 --> 0:11:21.400
<v Speaker 1>reminds me of the keypads on old cell phones where

0:11:21.440 --> 0:11:23.480
<v Speaker 1>if you wanted to send a text message and you

0:11:23.559 --> 0:11:26.200
<v Speaker 1>had to hit the letter E. You had to press

0:11:26.280 --> 0:11:28.640
<v Speaker 1>the D E F key twice in a row in

0:11:28.720 --> 0:11:30.960
<v Speaker 1>order for you to select E before you moved onto

0:11:30.960 --> 0:11:34.400
<v Speaker 1>your next letter. According to Starner, he could hit type

0:11:34.440 --> 0:11:36.880
<v Speaker 1>up to a hundred thirty words per minute using this

0:11:36.960 --> 0:11:42.560
<v Speaker 1>one handed keyboard method, which is crazy fast. It's crazy

0:11:42.600 --> 0:11:46.200
<v Speaker 1>fast even if you're using two hands on a regular keyboard.

0:11:46.200 --> 0:11:50.160
<v Speaker 1>So I was really impressed to hear about that. Uh,

0:11:50.480 --> 0:11:53.559
<v Speaker 1>very large and heavy batteries would give the computer more

0:11:53.559 --> 0:11:55.920
<v Speaker 1>than ten hours of juice before you need to recharge.

0:11:55.960 --> 0:12:00.280
<v Speaker 1>But I mean these batteries weighed several pounds at Lee East,

0:12:00.880 --> 0:12:06.800
<v Speaker 1>so they weren't little unobtrusive things attached to the computer.

0:12:06.920 --> 0:12:12.600
<v Speaker 1>It was it was like wearing a hefty backpack. Um,

0:12:12.600 --> 0:12:15.080
<v Speaker 1>so it wasn't exactly comfortable to wear all the time.

0:12:16.480 --> 0:12:18.720
<v Speaker 1>And the computer was really serving as a platform, a

0:12:18.800 --> 0:12:22.240
<v Speaker 1>development platform. It was the basis for programmers to design

0:12:22.360 --> 0:12:26.559
<v Speaker 1>wearable computing applications. So it's not like it magically gave

0:12:26.600 --> 0:12:29.560
<v Speaker 1>Starner some sort of crazy computing ability. It was rather

0:12:29.600 --> 0:12:32.120
<v Speaker 1>an early wearable device to help explore the applications and

0:12:32.160 --> 0:12:38.000
<v Speaker 1>implementations of wearables without having to worry about creating a

0:12:38.040 --> 0:12:42.840
<v Speaker 1>specific product. So this was really exploratory, and when you

0:12:42.880 --> 0:12:45.280
<v Speaker 1>think about it, it was meant to say, we think

0:12:45.320 --> 0:12:48.840
<v Speaker 1>there's something here, but we don't exactly know what it

0:12:49.000 --> 0:12:50.960
<v Speaker 1>is yet. We don't know what the final form is

0:12:51.000 --> 0:12:53.319
<v Speaker 1>going to be, So I don't have an idea for

0:12:53.679 --> 0:12:55.960
<v Speaker 1>something that's going to be in a package on a

0:12:56.040 --> 0:12:59.080
<v Speaker 1>store shelf that other people can go out and buy. Rather,

0:12:59.240 --> 0:13:04.600
<v Speaker 1>I think computing has the capability of transforming our daily

0:13:04.679 --> 0:13:08.040
<v Speaker 1>lives in yet another way. Now keep in mind, this

0:13:08.080 --> 0:13:12.360
<v Speaker 1>isn't nineteen the early nineties. This is before smartphones, so

0:13:12.480 --> 0:13:15.440
<v Speaker 1>smartphones would go on to show us that, yes, indeed,

0:13:15.720 --> 0:13:18.320
<v Speaker 1>having a computer device that you can carry around with

0:13:18.400 --> 0:13:23.280
<v Speaker 1>you changes things. There's no question of that. The Internet

0:13:23.320 --> 0:13:26.440
<v Speaker 1>itself is a reflection of how much that has changed.

0:13:26.720 --> 0:13:31.319
<v Speaker 1>Internet advertising has changed dramatically because of mobile devices and

0:13:31.480 --> 0:13:35.000
<v Speaker 1>the popularity of them. So wearable computer has definitely had

0:13:35.040 --> 0:13:38.600
<v Speaker 1>the potential to make an enormous impact. But we had

0:13:38.640 --> 0:13:43.120
<v Speaker 1>to figure out what sort of implementation made sense and

0:13:43.200 --> 0:13:45.880
<v Speaker 1>what kind of applications would you use it for. Because

0:13:45.960 --> 0:13:49.200
<v Speaker 1>just to have something, just to have it that doesn't

0:13:49.240 --> 0:13:51.960
<v Speaker 1>remain compelling for very long, that would be part of

0:13:51.960 --> 0:13:57.199
<v Speaker 1>the problem of Google Glass later spoiler alert. Now, one

0:13:57.200 --> 0:14:01.240
<v Speaker 1>of those applications that Starner created or e on, was

0:14:02.160 --> 0:14:04.880
<v Speaker 1>a program that would keep track of everything he said,

0:14:05.679 --> 0:14:07.880
<v Speaker 1>whether or not it was straight voice to text, I

0:14:07.880 --> 0:14:11.120
<v Speaker 1>am not entirely certain. I'm sure by some point it

0:14:11.160 --> 0:14:14.079
<v Speaker 1>really was. But he would also be able to type

0:14:14.120 --> 0:14:18.160
<v Speaker 1>things in using the twiddler, which I remind you it's

0:14:18.240 --> 0:14:21.480
<v Speaker 1>not a joke. So it was kind of like a

0:14:21.480 --> 0:14:24.320
<v Speaker 1>perpetual notes system. He could keep track of things he

0:14:24.400 --> 0:14:26.880
<v Speaker 1>was thinking about and talking about, and then he could

0:14:26.960 --> 0:14:29.480
<v Speaker 1>run a search back against that and see if he

0:14:29.480 --> 0:14:32.240
<v Speaker 1>could find anything interesting later on. And he said that

0:14:32.360 --> 0:14:35.560
<v Speaker 1>about cent of the time what he got back was garbage,

0:14:35.960 --> 0:14:39.720
<v Speaker 1>wasn't particularly interesting, insightful, or helpful. But about five percent

0:14:39.720 --> 0:14:43.000
<v Speaker 1>at the time it was totally the opposite. It was

0:14:43.400 --> 0:14:47.840
<v Speaker 1>something really worth knowing and remembering. So he thought of

0:14:47.840 --> 0:14:50.600
<v Speaker 1>it as something like a memory booster. It wasn't. It

0:14:50.680 --> 0:14:55.040
<v Speaker 1>wasn't replacing his memory, but augmenting it. Now, according to

0:14:55.040 --> 0:14:59.040
<v Speaker 1>popular accounts, Starner attended a conference in the late nineties

0:14:59.760 --> 0:15:02.800
<v Speaker 1>and and he met to post graduate students from Stanford,

0:15:02.840 --> 0:15:07.080
<v Speaker 1>so this would be about those two post graduate students

0:15:07.160 --> 0:15:10.880
<v Speaker 1>were named Saragi Brenn and Larry Page, And if you're

0:15:10.920 --> 0:15:13.080
<v Speaker 1>familiar with those two, you know those are the co

0:15:13.240 --> 0:15:16.520
<v Speaker 1>founders for Google. In fact, they would found the company

0:15:16.520 --> 0:15:20.360
<v Speaker 1>Google just a few short months after this conference. Now,

0:15:20.400 --> 0:15:24.840
<v Speaker 1>Brin and Page thought that Starner's wearable computers were fascinating,

0:15:25.240 --> 0:15:27.720
<v Speaker 1>and he gave them a full demonstration of what the

0:15:27.760 --> 0:15:30.920
<v Speaker 1>computer was capable of doing. However, at the time, they

0:15:30.920 --> 0:15:35.280
<v Speaker 1>were already focusing on a way to improve search engines

0:15:35.440 --> 0:15:39.240
<v Speaker 1>on the web, so they couldn't really dedicate any attention

0:15:39.280 --> 0:15:42.040
<v Speaker 1>to wearable computers they were they were too busy perfecting

0:15:42.120 --> 0:15:46.480
<v Speaker 1>their search engine approach. And this was important because back

0:15:46.480 --> 0:15:50.200
<v Speaker 1>in the day before things like Google, the algorithm that

0:15:50.280 --> 0:15:53.040
<v Speaker 1>got so sophisticated that it was able to ignore a

0:15:53.040 --> 0:15:54.920
<v Speaker 1>lot of the tricks people were using to try and

0:15:55.000 --> 0:15:59.640
<v Speaker 1>direct traffic to their sites. Web search engines were just okay.

0:15:59.680 --> 0:16:03.640
<v Speaker 1>Most of them were looking for instances of keywords appearing

0:16:03.800 --> 0:16:06.280
<v Speaker 1>on a page, which meant that people would try and

0:16:06.360 --> 0:16:10.600
<v Speaker 1>full search engines by inserting as many different key search

0:16:10.760 --> 0:16:13.480
<v Speaker 1>terms as possible at the bottom of a page, even

0:16:13.520 --> 0:16:17.920
<v Speaker 1>if the page had nothing to do with that particular concept.

0:16:18.080 --> 0:16:21.120
<v Speaker 1>And why would they do this? Because web advertising is

0:16:21.160 --> 0:16:24.240
<v Speaker 1>based off of how many views you get on a page.

0:16:24.600 --> 0:16:27.960
<v Speaker 1>Page views are king at least most. Web advertising is

0:16:27.960 --> 0:16:29.400
<v Speaker 1>not all of it, but a lot of it is.

0:16:30.560 --> 0:16:32.360
<v Speaker 1>So if you were able to direct a lot of

0:16:32.360 --> 0:16:35.280
<v Speaker 1>traffic to your web page, that was another page view.

0:16:35.520 --> 0:16:38.280
<v Speaker 1>It didn't matter if what that people founded that by

0:16:38.320 --> 0:16:40.120
<v Speaker 1>the time they got there, if it wasn't what they

0:16:40.160 --> 0:16:42.360
<v Speaker 1>were looking for, and if they bounced, you got the

0:16:42.360 --> 0:16:45.640
<v Speaker 1>page view. You don't care where they go afterward. Well,

0:16:45.680 --> 0:16:48.760
<v Speaker 1>Google one of its big missions was to create a

0:16:48.800 --> 0:16:51.960
<v Speaker 1>better search engine that would ignore all of the gamification

0:16:52.400 --> 0:16:56.400
<v Speaker 1>of S e O and to try and look for

0:16:56.920 --> 0:16:59.760
<v Speaker 1>the links that are the best representation of whatever it

0:16:59.840 --> 0:17:02.920
<v Speaker 1>is you're searching for. So that's what they're they're real

0:17:02.960 --> 0:17:07.040
<v Speaker 1>focus was on. However, this whole, this meeting between Starner

0:17:07.080 --> 0:17:12.040
<v Speaker 1>and Brennan Page may have been the first seed for

0:17:12.160 --> 0:17:16.000
<v Speaker 1>Google Glass, and it happened in before Google was an

0:17:16.040 --> 0:17:20.720
<v Speaker 1>official company. Now flash forward a decade. It's two thousand eight.

0:17:21.240 --> 0:17:25.879
<v Speaker 1>Google by this time is a huge company, incredibly successful,

0:17:26.400 --> 0:17:30.280
<v Speaker 1>and it had just launched its own smartphone operating system

0:17:30.440 --> 0:17:37.640
<v Speaker 1>called Android. Starner immediately thought that Android had promise as

0:17:37.720 --> 0:17:40.560
<v Speaker 1>more than just an operating system for a smartphone. It

0:17:40.600 --> 0:17:43.840
<v Speaker 1>could be ported over to all sorts of different devices

0:17:43.920 --> 0:17:47.840
<v Speaker 1>and used for lots of different stuff, particularly things that

0:17:48.000 --> 0:17:52.000
<v Speaker 1>were small and nimble, stuff that wasn't like your traditional

0:17:52.080 --> 0:17:58.080
<v Speaker 1>laptop or desktop computer that includes wearables. So he tried

0:17:58.119 --> 0:18:01.560
<v Speaker 1>to get in touch with Brennan Paige. However, the phone

0:18:01.600 --> 0:18:05.440
<v Speaker 1>number he had from ten years previous was no longer

0:18:06.040 --> 0:18:09.879
<v Speaker 1>going to either of them. Big surprise, right, and he

0:18:10.000 --> 0:18:12.920
<v Speaker 1>kind of let lie for another couple of years. In

0:18:12.960 --> 0:18:15.720
<v Speaker 1>two ten he would write an email to Sarah ge

0:18:15.720 --> 0:18:20.399
<v Speaker 1>brend and he said, you should probably come out to

0:18:20.480 --> 0:18:22.600
<v Speaker 1>my lab at Georgia Tech and take a look at

0:18:22.600 --> 0:18:24.840
<v Speaker 1>the wearables and see where we've gone in the last

0:18:24.840 --> 0:18:27.240
<v Speaker 1>ten years. I think you'd be really interested. And Brandon said,

0:18:27.240 --> 0:18:30.040
<v Speaker 1>you know, we're thinking about wearables. We think it's about time.

0:18:30.720 --> 0:18:33.080
<v Speaker 1>And rather than us go there, how about we fly

0:18:33.160 --> 0:18:34.919
<v Speaker 1>you and your team out here so you can give

0:18:35.000 --> 0:18:38.400
<v Speaker 1>us a full day of demonstrations. And Starner said yes,

0:18:38.400 --> 0:18:41.160
<v Speaker 1>and next thing he knew, he became a technical lead

0:18:41.400 --> 0:18:48.280
<v Speaker 1>for Project Glass over at Google's X division. By shortly

0:18:48.320 --> 0:18:51.520
<v Speaker 1>thereafter after Starner joined the team, uh Starner Brennan Page

0:18:51.520 --> 0:18:54.000
<v Speaker 1>were able to bring over another leader in wearable tech.

0:18:54.080 --> 0:18:57.160
<v Speaker 1>Someone that Starner had worked with in the past, Greg

0:18:57.280 --> 0:19:00.840
<v Speaker 1>Priest Dorman, who had pioneered work with bio feedback systems

0:19:00.840 --> 0:19:02.880
<v Speaker 1>in the seventies and into the eighties and then moved

0:19:02.920 --> 0:19:07.840
<v Speaker 1>into wearable computing. He's another huge name in wearables, so

0:19:07.880 --> 0:19:13.480
<v Speaker 1>he also joined the Google Glass development team. On August

0:19:14.040 --> 0:19:17.040
<v Speaker 1>two thousand eleven, four Google employees filed a patent for

0:19:17.080 --> 0:19:22.080
<v Speaker 1>what was called a wearable device with input and output structures.

0:19:22.960 --> 0:19:26.160
<v Speaker 1>It's the title of a patent, and like most patent titles,

0:19:26.440 --> 0:19:29.760
<v Speaker 1>it's a little dry and it seems pretty nondescript. The

0:19:29.800 --> 0:19:34.040
<v Speaker 1>illustrations accompanying the patent include one that closely resembles what

0:19:34.200 --> 0:19:36.520
<v Speaker 1>the final form of Google Glass turned out to be.

0:19:37.440 --> 0:19:39.600
<v Speaker 1>Some of the other illustrations look more like a more

0:19:39.680 --> 0:19:42.080
<v Speaker 1>or less normal pair of glasses. Some of them looked

0:19:42.080 --> 0:19:45.639
<v Speaker 1>a little strange or odd. The patent described the general

0:19:45.680 --> 0:19:50.240
<v Speaker 1>components for the invention, which you know patents are supposed

0:19:50.280 --> 0:19:52.440
<v Speaker 1>to do. In order for you to get a patent

0:19:52.480 --> 0:19:54.600
<v Speaker 1>on something, you have to actually explain how the thing

0:19:54.640 --> 0:19:56.920
<v Speaker 1>works in the parts that it that are that it's

0:19:56.960 --> 0:20:00.840
<v Speaker 1>made out of. Otherwise you can't. You're not supposed to

0:20:00.840 --> 0:20:04.840
<v Speaker 1>get a patent on it. So what did this cover? Well,

0:20:04.960 --> 0:20:07.879
<v Speaker 1>I suppose I can quote directly from the patent itself

0:20:08.680 --> 0:20:12.359
<v Speaker 1>under the claims section. The first and most important of

0:20:12.400 --> 0:20:19.720
<v Speaker 1>the claims reads thus late an electronic device comprising a

0:20:19.840 --> 0:20:22.439
<v Speaker 1>frame configured to be worn on the head of a user,

0:20:22.720 --> 0:20:25.760
<v Speaker 1>the frame including a bridge configured to be supported on

0:20:25.840 --> 0:20:29.320
<v Speaker 1>the nose of the user, a brow portion coupled to

0:20:29.600 --> 0:20:33.119
<v Speaker 1>and extending away from the bridge to a first end

0:20:33.240 --> 0:20:37.080
<v Speaker 1>remote there from, and configured to be positioned over a

0:20:37.200 --> 0:20:40.119
<v Speaker 1>first side of a brow of the user, and the

0:20:40.280 --> 0:20:43.439
<v Speaker 1>first arm having a first end coupled to the first

0:20:43.600 --> 0:20:46.920
<v Speaker 1>end of the brow portion and extending to a free end,

0:20:47.240 --> 0:20:49.960
<v Speaker 1>the first arm being configured to be positioned over a

0:20:50.040 --> 0:20:53.520
<v Speaker 1>first temple of the user, with the free end disposed

0:20:53.560 --> 0:20:57.320
<v Speaker 1>near a first ear of the user, wherein the bridge

0:20:57.359 --> 0:21:00.920
<v Speaker 1>is adjustable for selective positioning of the brow portion relative

0:21:01.000 --> 0:21:04.680
<v Speaker 1>to an eye of the user. A generally transparent display

0:21:05.119 --> 0:21:07.960
<v Speaker 1>means for affixing the display to the frame such that

0:21:08.160 --> 0:21:10.920
<v Speaker 1>the display is movable with respect to the frame through

0:21:11.040 --> 0:21:14.399
<v Speaker 1>rotation about a first axis that extends parallel to the

0:21:14.400 --> 0:21:18.119
<v Speaker 1>first brow portion, and an input device affixed to the

0:21:18.200 --> 0:21:21.440
<v Speaker 1>frame and configured for receiving from the user and input

0:21:21.480 --> 0:21:25.199
<v Speaker 1>associated with a function, wherein information related to the function

0:21:25.359 --> 0:21:30.520
<v Speaker 1>is presentable on the display. What the what? Well, I'm

0:21:30.520 --> 0:21:34.440
<v Speaker 1>gonna explain what that means, but first let's take a

0:21:34.520 --> 0:21:44.000
<v Speaker 1>quick break to thank our sponsor. All right, So what

0:21:44.040 --> 0:21:48.600
<v Speaker 1>did that patent speak actually mean? Because it gots so

0:21:49.640 --> 0:21:53.080
<v Speaker 1>weird and dry, and that's typical for patents, by the way.

0:21:53.119 --> 0:21:58.840
<v Speaker 1>That's it's a very formulaic approach because you know, patent

0:21:58.920 --> 0:22:02.200
<v Speaker 1>system is is a bureocracy, and you have to conform

0:22:02.400 --> 0:22:05.480
<v Speaker 1>to the methodology of the bureaucracy in order to get

0:22:06.000 --> 0:22:10.840
<v Speaker 1>your idea through. Otherwise, if it doesn't conform, you're not

0:22:10.960 --> 0:22:14.760
<v Speaker 1>likely to get a patent award. So what it actually

0:22:14.840 --> 0:22:17.080
<v Speaker 1>means is the invention would fit on your face like

0:22:17.119 --> 0:22:20.920
<v Speaker 1>a pair of glasses that one arm or stem if

0:22:20.920 --> 0:22:25.200
<v Speaker 1>you prefer, of these glasses would curve around the brow

0:22:25.520 --> 0:22:28.880
<v Speaker 1>above one eye to rest against the side of your head,

0:22:28.960 --> 0:22:32.480
<v Speaker 1>so over one eye, and in early Google glass it

0:22:32.560 --> 0:22:36.360
<v Speaker 1>was always the right eye. There'd be a little protrusion.

0:22:37.280 --> 0:22:39.920
<v Speaker 1>That's where at the end of that protrusion, that's where

0:22:39.920 --> 0:22:44.159
<v Speaker 1>the screen would be, the clear, transparent sclip screen. I

0:22:44.200 --> 0:22:46.040
<v Speaker 1>guess I can say clear and transparent like I can

0:22:46.040 --> 0:22:50.240
<v Speaker 1>say a t M machine. Uh. Then the the other

0:22:50.359 --> 0:22:53.080
<v Speaker 1>part of it would wrap around back behind your ear,

0:22:53.920 --> 0:22:57.359
<v Speaker 1>with a part of it resting just behind your ear.

0:22:57.920 --> 0:23:00.560
<v Speaker 1>More on that in just a second, But that would

0:23:00.560 --> 0:23:03.320
<v Speaker 1>be the main part of Google Glass. The other section

0:23:03.359 --> 0:23:07.440
<v Speaker 1>would just be a dumb frame that exists really just

0:23:07.480 --> 0:23:09.840
<v Speaker 1>to provide stability. So you would have a part that

0:23:09.880 --> 0:23:11.600
<v Speaker 1>would rest on the bridge of your nose that would

0:23:11.600 --> 0:23:17.080
<v Speaker 1>help support the the stem I was talking about. And

0:23:17.160 --> 0:23:20.159
<v Speaker 1>on the other side your second ear, because you remember

0:23:20.160 --> 0:23:24.920
<v Speaker 1>the patent said first ear and first etcetera, etcetera. First brow.

0:23:25.960 --> 0:23:27.800
<v Speaker 1>The other one would be the second one. This is

0:23:27.840 --> 0:23:31.680
<v Speaker 1>not important to the invention because nothing of any technical

0:23:31.800 --> 0:23:34.760
<v Speaker 1>technical import is going on on that side. It's literally

0:23:34.840 --> 0:23:38.080
<v Speaker 1>just a frame to hold the rest of the technology

0:23:38.080 --> 0:23:41.080
<v Speaker 1>in place. So over your right ear you have the

0:23:41.119 --> 0:23:44.240
<v Speaker 1>stem of the Google Glass, and in that section you've

0:23:44.280 --> 0:23:47.560
<v Speaker 1>got a control area. You've got your battery, you've got

0:23:47.600 --> 0:23:50.960
<v Speaker 1>your speaker, you've got your projector for the screen, you've

0:23:50.960 --> 0:23:54.920
<v Speaker 1>got inside, you've got the processor, you've got the receiver

0:23:55.040 --> 0:23:58.840
<v Speaker 1>for Bluetooth, etcetera. On the other side, over your left ear,

0:23:59.119 --> 0:24:01.960
<v Speaker 1>it's just a regular or little stem that fits over

0:24:02.040 --> 0:24:04.040
<v Speaker 1>your ear, kind of like a regular pair of glasses.

0:24:04.080 --> 0:24:08.880
<v Speaker 1>There's nothing there, no technical elements inside that side of it.

0:24:08.880 --> 0:24:17.040
<v Speaker 1>It's just dumb plastic. So the part that's right behind

0:24:17.040 --> 0:24:20.399
<v Speaker 1>your ear, that's where the speaker was, that's where the

0:24:20.440 --> 0:24:23.080
<v Speaker 1>audio would come from. Obviously, if you're watching a video

0:24:23.320 --> 0:24:25.320
<v Speaker 1>or you're taking a call, you would need to be

0:24:25.359 --> 0:24:29.280
<v Speaker 1>able to hear things through the glasses. Uh, it's cool

0:24:29.400 --> 0:24:32.840
<v Speaker 1>because this particular speaker wasn't just playing audio blasting it

0:24:32.840 --> 0:24:35.879
<v Speaker 1>out into the real world. It was using bone conduction

0:24:36.200 --> 0:24:40.520
<v Speaker 1>to transmit audio so that you could hear it. Now,

0:24:40.560 --> 0:24:42.520
<v Speaker 1>if you stood close to someone who was wearing google

0:24:42.560 --> 0:24:44.760
<v Speaker 1>glass and they were playing audio, you would hear stuff.

0:24:44.840 --> 0:24:47.919
<v Speaker 1>Because when you get down to it, sound is vibration.

0:24:48.840 --> 0:24:52.400
<v Speaker 1>The sound that you are hearing right now is transmitted

0:24:52.560 --> 0:24:56.720
<v Speaker 1>through molecules vibrating at the frequency that I'm talking at,

0:24:56.840 --> 0:25:02.119
<v Speaker 1>and the amplification as well. The amplitude. So when you

0:25:02.160 --> 0:25:04.320
<v Speaker 1>get down to the fact that sound is just vibration,

0:25:04.600 --> 0:25:08.040
<v Speaker 1>bone conduction makes sense. It is what it sounds like.

0:25:08.280 --> 0:25:13.240
<v Speaker 1>Sound is transmitting through bone. Your bone conducts sound bones,

0:25:13.520 --> 0:25:15.760
<v Speaker 1>I should say, although in this particular case, we're talking

0:25:15.760 --> 0:25:20.040
<v Speaker 1>about the skull, otherwise known in medical circles as the headbone.

0:25:21.240 --> 0:25:24.840
<v Speaker 1>So the headbone would transmit the sound from the speaker.

0:25:25.359 --> 0:25:28.160
<v Speaker 1>So what's happening is that? Well, I guess it helps

0:25:28.200 --> 0:25:31.120
<v Speaker 1>if we talk about just the regular sense of hearing first, Right,

0:25:31.880 --> 0:25:36.200
<v Speaker 1>These vibrating air molecules enter your ear canal. They cause

0:25:36.280 --> 0:25:39.760
<v Speaker 1>your ear drum or your tympanic membrane if you prefer

0:25:40.240 --> 0:25:45.080
<v Speaker 1>to vibrate. Now, that vibration gets transmitted to a tiny

0:25:45.119 --> 0:25:48.280
<v Speaker 1>set of bones in your inner ear, which act as

0:25:48.359 --> 0:25:52.560
<v Speaker 1>kind of like an amplifier, and they ultimately terminate on

0:25:52.640 --> 0:25:56.240
<v Speaker 1>an organ called the cochlea, which is sort of in

0:25:56.359 --> 0:25:59.320
<v Speaker 1>a spiral shell shape. It's got some fluid in it,

0:25:59.359 --> 0:26:03.040
<v Speaker 1>and it's got some fingerlike nerve endings in it that

0:26:03.119 --> 0:26:06.840
<v Speaker 1>are in this fluid. And when the cochlea is vibrated,

0:26:06.880 --> 0:26:10.520
<v Speaker 1>then this fluid moves around and that stimulates the nerve

0:26:10.640 --> 0:26:13.720
<v Speaker 1>endings inside of it, which then send signals to the brain,

0:26:14.000 --> 0:26:17.640
<v Speaker 1>which then interpret that to be sound. It's pretty cool

0:26:17.880 --> 0:26:20.320
<v Speaker 1>when you really developed thought about it. Well, the neat

0:26:20.320 --> 0:26:22.960
<v Speaker 1>thing about bone conduction is you can bypass the ear

0:26:23.000 --> 0:26:27.240
<v Speaker 1>drum entirely. You can send vibrations through bone, which then

0:26:27.240 --> 0:26:31.560
<v Speaker 1>will reach the inner ear on their own bypassing that

0:26:31.640 --> 0:26:36.000
<v Speaker 1>pathway that all other sound tends to take and vibrating

0:26:36.000 --> 0:26:40.480
<v Speaker 1>the cochlea directly. So there are a lot of sports

0:26:41.359 --> 0:26:44.919
<v Speaker 1>earbuds or or headbands or whatever that have these kind

0:26:44.960 --> 0:26:49.159
<v Speaker 1>of bone conduction speakers some people call bone phones. I

0:26:49.240 --> 0:26:54.120
<v Speaker 1>do not, but some people do. And the Google Glass

0:26:54.280 --> 0:26:57.960
<v Speaker 1>had one of these types of speakers to again transmit

0:26:58.040 --> 0:27:02.080
<v Speaker 1>sound without it blasting out into the general world. Uh.

0:27:02.200 --> 0:27:04.600
<v Speaker 1>Pretty interesting stuff. And this meant that you could watch

0:27:04.680 --> 0:27:07.120
<v Speaker 1>things like videos, or listen to a voicemail or make

0:27:07.119 --> 0:27:11.360
<v Speaker 1>a call using Google Glass, and you could hear through

0:27:11.400 --> 0:27:13.280
<v Speaker 1>Google Glass. You didn't have to hold a phone up

0:27:13.280 --> 0:27:19.199
<v Speaker 1>to your other ear. Now, the invention also incorporated a

0:27:19.240 --> 0:27:22.120
<v Speaker 1>screen that was transparent, so, in other words, you had

0:27:22.160 --> 0:27:25.159
<v Speaker 1>to be able to see through the screen and be

0:27:25.240 --> 0:27:28.719
<v Speaker 1>able to view the outside world through it. It couldn't

0:27:28.800 --> 0:27:31.800
<v Speaker 1>have an opaque backing, so you couldn't silver the back

0:27:31.840 --> 0:27:35.359
<v Speaker 1>of the screen, which presents some challenges. So how do

0:27:35.400 --> 0:27:39.120
<v Speaker 1>you project images so that you can see a display

0:27:39.359 --> 0:27:42.840
<v Speaker 1>and read the digital information? Because again, that's what augmented

0:27:42.840 --> 0:27:45.879
<v Speaker 1>reality is all about, right, It's overlaying that digital information

0:27:46.000 --> 0:27:48.520
<v Speaker 1>on top of a view of the actual world around you.

0:27:48.960 --> 0:27:50.600
<v Speaker 1>So if you can see through the screen, how do

0:27:50.680 --> 0:27:56.320
<v Speaker 1>you display images on that said screen? Well, Claim nine

0:27:57.240 --> 0:27:59.840
<v Speaker 1>on that same patent gives some information on that matter.

0:27:59.880 --> 0:28:03.800
<v Speaker 1>It says the electronic device of Claim one, wherein the

0:28:03.920 --> 0:28:07.960
<v Speaker 1>generally transparent display is a prism of a transparent material

0:28:08.040 --> 0:28:11.320
<v Speaker 1>configured to make an image projected into a side of

0:28:11.359 --> 0:28:14.439
<v Speaker 1>the prism visible at a surface of the prism that

0:28:14.600 --> 0:28:17.239
<v Speaker 1>is at a non zero angle to the side of

0:28:17.280 --> 0:28:22.600
<v Speaker 1>the prism. Now what that means is that on casual glance,

0:28:23.160 --> 0:28:28.119
<v Speaker 1>the prism looks like an elongated cube of clear plastic,

0:28:28.920 --> 0:28:31.360
<v Speaker 1>and it looks like that's all it is. But if

0:28:31.400 --> 0:28:33.600
<v Speaker 1>you were to take a look at it from the top,

0:28:34.320 --> 0:28:36.680
<v Speaker 1>like the top of a pair of Google glass, and

0:28:36.720 --> 0:28:39.240
<v Speaker 1>you were looking down, you would see that there's a

0:28:39.280 --> 0:28:45.960
<v Speaker 1>fine line bisecting from one uh corner of this prism

0:28:46.160 --> 0:28:50.920
<v Speaker 1>down into about the middle of the prism. And you know,

0:28:50.960 --> 0:28:55.320
<v Speaker 1>at this weird little diagonal. This is an angled layer

0:28:55.680 --> 0:28:58.080
<v Speaker 1>inside the prism, and the way it works is it

0:28:58.120 --> 0:29:01.920
<v Speaker 1>allows light to pass through straight from ahead of you.

0:29:02.000 --> 0:29:03.760
<v Speaker 1>So if you're wearing the pair of Google glass and

0:29:03.760 --> 0:29:06.840
<v Speaker 1>you're looking at something, light can pass straight through the prism,

0:29:07.080 --> 0:29:09.520
<v Speaker 1>no problem. But if light were to come from a

0:29:09.720 --> 0:29:13.760
<v Speaker 1>right angle to the right, as in a place where

0:29:13.760 --> 0:29:18.000
<v Speaker 1>a little projector in the Google Glass could project out images,

0:29:19.040 --> 0:29:23.000
<v Speaker 1>it would then redirect that light ninety degrees so that

0:29:23.080 --> 0:29:26.120
<v Speaker 1>it goes into your eyes. In other words, you can

0:29:26.120 --> 0:29:28.600
<v Speaker 1>still see the world in front of you because that

0:29:28.720 --> 0:29:32.640
<v Speaker 1>light can pass through unimpeded. Light coming from the right side,

0:29:32.840 --> 0:29:36.520
<v Speaker 1>which is where the the digital little digital projector is,

0:29:37.480 --> 0:29:39.680
<v Speaker 1>that gets reflected into your eyes, so then you can

0:29:39.680 --> 0:29:42.880
<v Speaker 1>see the digital information overlaid on top of the world

0:29:42.920 --> 0:29:45.360
<v Speaker 1>around you. So the think of it is kind of

0:29:45.360 --> 0:29:49.240
<v Speaker 1>like a mirror, but the mirror only works if light

0:29:49.320 --> 0:29:53.080
<v Speaker 1>is coming at it from a very specific angle. It's,

0:29:53.240 --> 0:29:54.920
<v Speaker 1>you know, in a way like a a one of

0:29:54.960 --> 0:29:57.000
<v Speaker 1>those two way mirrors where you can see through one

0:29:57.000 --> 0:29:59.040
<v Speaker 1>way but not in the other. It's kind of similar

0:29:59.040 --> 0:30:04.240
<v Speaker 1>to that. So I thought that was super neat um.

0:30:04.680 --> 0:30:07.320
<v Speaker 1>It was actually the most fascinating part of Google Glass

0:30:07.320 --> 0:30:09.600
<v Speaker 1>when I was first learning about it way back in

0:30:11.200 --> 0:30:13.680
<v Speaker 1>when I was trying to learn how it worked so

0:30:13.720 --> 0:30:15.520
<v Speaker 1>I could write an article about it, and in fact

0:30:15.560 --> 0:30:18.760
<v Speaker 1>I did right at least a version of how Google

0:30:18.800 --> 0:30:21.080
<v Speaker 1>Glass works. I haven't looked on the website to see

0:30:21.080 --> 0:30:24.040
<v Speaker 1>if that's still my version, because we update these these

0:30:24.360 --> 0:30:28.280
<v Speaker 1>articles on occasion and sometimes that changes the authorship as well.

0:30:29.160 --> 0:30:30.920
<v Speaker 1>But yeah, way back in the day, I wrote an

0:30:31.000 --> 0:30:33.200
<v Speaker 1>article about how Google Glass works, and part of it

0:30:33.240 --> 0:30:35.000
<v Speaker 1>was just learning about this prism and I thought it

0:30:35.040 --> 0:30:43.560
<v Speaker 1>was fascinating. In addition, the UH, the design of this

0:30:43.640 --> 0:30:46.680
<v Speaker 1>prism meant that it was slightly above your normal line

0:30:46.680 --> 0:30:49.120
<v Speaker 1>of sight. So this is that part of the patent

0:30:49.160 --> 0:30:53.040
<v Speaker 1>that talked about it being offset from your eye. It's

0:30:53.760 --> 0:30:57.400
<v Speaker 1>it's mounted a bit above where your natural line of

0:30:57.440 --> 0:30:59.760
<v Speaker 1>sight would be, so you would always have it in

0:30:59.840 --> 0:31:02.200
<v Speaker 1>your field of view, but it wouldn't necessarily be in

0:31:02.240 --> 0:31:05.240
<v Speaker 1>focus unless you were to glance upward so that your

0:31:05.360 --> 0:31:09.720
<v Speaker 1>right eye would be looking at the prism directly. This

0:31:09.880 --> 0:31:14.120
<v Speaker 1>was a specific design implemented by Google in order to

0:31:14.200 --> 0:31:17.840
<v Speaker 1>avoid things like people getting distracted by digital images when

0:31:17.840 --> 0:31:20.280
<v Speaker 1>they should be paying into to the world around them,

0:31:20.320 --> 0:31:23.960
<v Speaker 1>and to make Google Glass something that you reference rather

0:31:24.000 --> 0:31:27.160
<v Speaker 1>than something that replaces your view of the world around you.

0:31:27.920 --> 0:31:29.960
<v Speaker 1>Very important if you're doing something like I don't know,

0:31:30.280 --> 0:31:34.440
<v Speaker 1>walking or driving or riding a bicycle, anything where you're

0:31:34.480 --> 0:31:37.040
<v Speaker 1>you're moving through a space, you want to be able

0:31:37.080 --> 0:31:40.440
<v Speaker 1>to make sure that you're not having your attention divided

0:31:40.680 --> 0:31:43.400
<v Speaker 1>so that you end up doing something stupid, like walking

0:31:43.480 --> 0:31:48.200
<v Speaker 1>into an open man hole or into a a telephone pole.

0:31:48.480 --> 0:31:51.480
<v Speaker 1>I have done that before, for real zes, but that

0:31:51.520 --> 0:31:53.280
<v Speaker 1>was because I was looking at a phone. I've been

0:31:53.280 --> 0:31:55.600
<v Speaker 1>that guy. I don't look at my phone when I'm

0:31:55.600 --> 0:31:58.400
<v Speaker 1>crossing streets, but I look at it when I'm walking

0:31:58.400 --> 0:32:01.560
<v Speaker 1>down sidewalks, and I have aid that price on multiple occasions.

0:32:01.600 --> 0:32:03.600
<v Speaker 1>You think I've learned by now, and I guess I have.

0:32:03.800 --> 0:32:09.840
<v Speaker 1>I've learned how to replicate that experience almost perfectly. The

0:32:09.880 --> 0:32:13.680
<v Speaker 1>patent also included an important component in Google Glasses control system,

0:32:13.760 --> 0:32:18.080
<v Speaker 1>which was a capacitive touch bar along that one stem,

0:32:18.320 --> 0:32:21.760
<v Speaker 1>the active stem of Google Glass. And I've talked about

0:32:21.800 --> 0:32:24.960
<v Speaker 1>capacitive touch before, but let's quickly go over that so

0:32:25.000 --> 0:32:27.760
<v Speaker 1>that we understand what I'm talking about. So with a

0:32:27.800 --> 0:32:31.880
<v Speaker 1>capacitive touch surface, you have the makings of a circuit, right.

0:32:32.280 --> 0:32:34.400
<v Speaker 1>All that remains is you have to have something to

0:32:34.520 --> 0:32:37.200
<v Speaker 1>close the circuit. You have to have something conductive make

0:32:37.400 --> 0:32:41.479
<v Speaker 1>contact with a capacitive surface, so that a complete circuit

0:32:41.560 --> 0:32:44.880
<v Speaker 1>can form, and when a complete circuit does form, there's

0:32:44.880 --> 0:32:48.680
<v Speaker 1>a voltage drop at the location of the touch. So

0:32:48.720 --> 0:32:50.640
<v Speaker 1>if I have a giant touch screen in front of me,

0:32:50.640 --> 0:32:53.840
<v Speaker 1>and it's a capacitive touch screen, and I reached down

0:32:53.920 --> 0:32:57.120
<v Speaker 1>with one finger and make contact with that screen, I

0:32:57.160 --> 0:32:59.720
<v Speaker 1>complete a circuit, and there's a voltage drop at the

0:32:59.720 --> 0:33:02.960
<v Speaker 1>point where I touched it. Software on the device is

0:33:03.000 --> 0:33:06.920
<v Speaker 1>able to interpret that as being a an actual command

0:33:06.960 --> 0:33:10.520
<v Speaker 1>of some sort, and it might be selecting a program.

0:33:10.520 --> 0:33:13.280
<v Speaker 1>It might mean turning volume up or down. It might

0:33:13.360 --> 0:33:16.800
<v Speaker 1>mean swiping right because that dude you're looking at on

0:33:16.880 --> 0:33:19.400
<v Speaker 1>tender is pretty hot and you kind of want to

0:33:19.440 --> 0:33:22.840
<v Speaker 1>know what what's his deal man, so you want to

0:33:22.840 --> 0:33:27.320
<v Speaker 1>swipe right on that. Lots of different applications. They are

0:33:27.360 --> 0:33:31.240
<v Speaker 1>also resistive touch screens that work on a slightly different principle.

0:33:31.320 --> 0:33:33.280
<v Speaker 1>Those are the ones that you have to actually use

0:33:33.360 --> 0:33:37.840
<v Speaker 1>pressure when you're making contact, because it's not enough to

0:33:37.840 --> 0:33:39.960
<v Speaker 1>touch it. You actually have to press so that you're

0:33:40.280 --> 0:33:43.920
<v Speaker 1>you're slightly deforming the layers in order to create a

0:33:44.040 --> 0:33:47.760
<v Speaker 1>circuit within the display itself. But that's a totally different

0:33:47.760 --> 0:33:52.719
<v Speaker 1>type of touch screen. Now, in the case of Google Glass,

0:33:52.760 --> 0:33:55.960
<v Speaker 1>the capacity panel is a means to cycle through the

0:33:56.040 --> 0:34:00.120
<v Speaker 1>various features that are on the glasses. It's all so

0:34:00.200 --> 0:34:03.120
<v Speaker 1>a way to execute other basic commands. So Google would

0:34:03.120 --> 0:34:06.200
<v Speaker 1>go a step further than this. You wouldn't have just

0:34:06.480 --> 0:34:09.160
<v Speaker 1>touch commands. That was just one way you could interact

0:34:09.200 --> 0:34:13.200
<v Speaker 1>with Google Glass. They also incorporated some motion controls and

0:34:13.360 --> 0:34:15.879
<v Speaker 1>voice commands. So, for example, if you want to turn

0:34:15.880 --> 0:34:18.200
<v Speaker 1>your screen on and you want to wake up Google

0:34:18.239 --> 0:34:21.480
<v Speaker 1>Glass from its power saving mode, you could choose an

0:34:21.520 --> 0:34:26.120
<v Speaker 1>option where by tilting your head backward at a fairly

0:34:26.200 --> 0:34:29.560
<v Speaker 1>good rate, it would wake up Google. It's kind of

0:34:29.600 --> 0:34:33.719
<v Speaker 1>like saying sup to someone. Uh. If you want to

0:34:33.719 --> 0:34:37.040
<v Speaker 1>take a photo, you could start with the phrase okay Google,

0:34:37.239 --> 0:34:39.680
<v Speaker 1>which probably sounds familiar to you if you have an

0:34:39.719 --> 0:34:42.440
<v Speaker 1>Android device or a Google Home and if I just

0:34:42.560 --> 0:34:47.399
<v Speaker 1>activated it, I am sorry. You could then follow up

0:34:47.440 --> 0:34:50.280
<v Speaker 1>with take a picture, so you could give a voice

0:34:50.280 --> 0:34:52.879
<v Speaker 1>command to your Google Glass to take photos. I can

0:34:52.880 --> 0:34:55.200
<v Speaker 1>speak from experience that people thought that this was the

0:34:55.239 --> 0:34:58.279
<v Speaker 1>coolest thing ever. When Google Glass was brand new and

0:34:58.320 --> 0:35:00.799
<v Speaker 1>only a few pairs were out in the wild. In

0:35:01.080 --> 0:35:05.480
<v Speaker 1>uh September of after I had a pair of Google Glass,

0:35:05.480 --> 0:35:08.200
<v Speaker 1>and yes I did have a pair of them. Technically,

0:35:08.239 --> 0:35:11.120
<v Speaker 1>the company purchased them. I was just the representative who

0:35:11.120 --> 0:35:13.840
<v Speaker 1>got to be the one to use them. When I

0:35:13.920 --> 0:35:17.239
<v Speaker 1>had them, I took them to dragon Con, which is

0:35:17.280 --> 0:35:20.279
<v Speaker 1>a big science fiction and fantasy convention here in Atlanta,

0:35:20.440 --> 0:35:22.600
<v Speaker 1>and I would ask people, may I take your picture?

0:35:22.880 --> 0:35:24.520
<v Speaker 1>You know, because there are a lot of people in costume,

0:35:24.560 --> 0:35:27.680
<v Speaker 1>a lot of great causeplay at dragon Con, and most

0:35:27.680 --> 0:35:29.640
<v Speaker 1>of the time people say yes absolutely. That's why I

0:35:29.680 --> 0:35:32.480
<v Speaker 1>got dressed up. And then I would say, okay, Google,

0:35:33.040 --> 0:35:36.319
<v Speaker 1>take a picture, and they would look at me confused

0:35:36.520 --> 0:35:39.560
<v Speaker 1>because they had never seen Google glass do that before.

0:35:39.600 --> 0:35:42.280
<v Speaker 1>And then the little light would flash on the Google

0:35:42.360 --> 0:35:45.200
<v Speaker 1>glass because that would indicate that a photo had been taken.

0:35:45.280 --> 0:35:48.640
<v Speaker 1>Google wanted to have a physical indicator to let people

0:35:48.640 --> 0:35:51.520
<v Speaker 1>know when a camera was active, and then immediately they

0:35:51.520 --> 0:35:54.680
<v Speaker 1>would freak out about the fact that I was wearing

0:35:54.680 --> 0:35:58.400
<v Speaker 1>the future on my faith, and I would invariably have

0:35:58.440 --> 0:36:00.880
<v Speaker 1>to take another photo because the first would mostly be

0:36:01.040 --> 0:36:03.560
<v Speaker 1>if you've ever seen a dog, look confused. That's what

0:36:03.680 --> 0:36:05.920
<v Speaker 1>almost all of the first photos looked like from that

0:36:06.000 --> 0:36:09.040
<v Speaker 1>Dragon Con, because I was talking to a pair of

0:36:09.080 --> 0:36:10.960
<v Speaker 1>glasses and they thought I was talking to them and

0:36:10.960 --> 0:36:14.000
<v Speaker 1>they were wondering, why am I saying this? These days

0:36:14.040 --> 0:36:17.520
<v Speaker 1>everyone would totally understand what was going on at the time,

0:36:17.520 --> 0:36:21.040
<v Speaker 1>it was pretty new. Now, to avoid making the headset

0:36:21.080 --> 0:36:24.280
<v Speaker 1>too heavy or too hot, the designers decided that Google

0:36:24.320 --> 0:36:27.840
<v Speaker 1>Glass would have to be a peripheral piece of technology. So,

0:36:27.880 --> 0:36:31.080
<v Speaker 1>in other words, they didn't want it to be loaded

0:36:31.120 --> 0:36:38.400
<v Speaker 1>down with processors and with various connectivity chips like cellular connectivity, WiFi,

0:36:38.560 --> 0:36:41.600
<v Speaker 1>all of that kind of stuff. Um, So you would

0:36:41.640 --> 0:36:45.320
<v Speaker 1>pair it to another device, like a smartphone, for example,

0:36:45.560 --> 0:36:50.320
<v Speaker 1>and the smartphone would act as your link between the

0:36:50.360 --> 0:36:54.000
<v Speaker 1>glasses and the outside world. For the most part. You

0:36:54.040 --> 0:36:57.480
<v Speaker 1>can also do WiFi, I think, but obviously WiFi is

0:36:57.520 --> 0:37:00.160
<v Speaker 1>not pervasive, so if you're anywhere where there's not why Fi,

0:37:00.320 --> 0:37:03.120
<v Speaker 1>you would need to have almost like a modem, and

0:37:03.200 --> 0:37:05.680
<v Speaker 1>your smartphone would act as your modem with a Bluetooth

0:37:05.680 --> 0:37:10.879
<v Speaker 1>connection allowing for the communication between your glasses and the phone. Now,

0:37:10.920 --> 0:37:12.960
<v Speaker 1>that simplified the components that needed to go into the

0:37:12.960 --> 0:37:15.880
<v Speaker 1>glasses themselves, and that allowed the designers to make it

0:37:15.960 --> 0:37:18.839
<v Speaker 1>a little bit lighter and not worry about so much

0:37:18.880 --> 0:37:21.120
<v Speaker 1>heat generation. It also meant that there was less of

0:37:21.120 --> 0:37:25.440
<v Speaker 1>a drain on the battery, Which was perhaps the biggest

0:37:25.520 --> 0:37:28.799
<v Speaker 1>challenge for the team was designing a battery that would

0:37:28.840 --> 0:37:32.120
<v Speaker 1>be light enough and yet powerful enough to do what

0:37:32.160 --> 0:37:35.600
<v Speaker 1>they wanted it to do. They needed it to not

0:37:36.120 --> 0:37:39.680
<v Speaker 1>make the glasses uncomfortable to wear or really unwearable for

0:37:39.719 --> 0:37:41.640
<v Speaker 1>any length of time, but they also wanted to make

0:37:41.640 --> 0:37:43.440
<v Speaker 1>sure they had enough juice to get a decent amount

0:37:43.480 --> 0:37:45.480
<v Speaker 1>of use out of it before you had to re

0:37:45.480 --> 0:37:49.800
<v Speaker 1>recharge it. They also got around this by having Google

0:37:49.840 --> 0:37:53.600
<v Speaker 1>Glass go into sleep mode pretty quickly, so that anytime

0:37:53.640 --> 0:37:56.280
<v Speaker 1>you were not actively using it, it could conserve power,

0:37:56.640 --> 0:37:59.920
<v Speaker 1>and that way you could get maybe another hour out

0:38:00.000 --> 0:38:03.279
<v Speaker 1>of it. It drained pretty fast back when I got one.

0:38:04.760 --> 0:38:08.839
<v Speaker 1>Earlier wearable computers would require those massive batteries I talked

0:38:08.840 --> 0:38:11.600
<v Speaker 1>about before, the ones that weighed four or five pounds. Now,

0:38:11.600 --> 0:38:14.520
<v Speaker 1>you don't want something like that on your glasses. It

0:38:14.560 --> 0:38:20.120
<v Speaker 1>would just be uh excruciating. So this was a huge

0:38:20.200 --> 0:38:23.279
<v Speaker 1>challenge and remains a huge challenge in wearables to this day,

0:38:23.360 --> 0:38:27.480
<v Speaker 1>is figuring out the balance between the features you want

0:38:27.520 --> 0:38:30.840
<v Speaker 1>to include and how much can a battery provide before

0:38:30.880 --> 0:38:33.240
<v Speaker 1>you're going to have to start recharging it every few minutes.

0:38:34.680 --> 0:38:36.920
<v Speaker 1>While the paperwork was being drawn up with the patents,

0:38:37.080 --> 0:38:40.440
<v Speaker 1>Starner and others were in Google's labs building this actual

0:38:40.520 --> 0:38:44.520
<v Speaker 1>hardware and testing it constantly. Whenever they were in the lab,

0:38:44.800 --> 0:38:47.320
<v Speaker 1>they were wearing these devices. Whenever they were doing the

0:38:47.400 --> 0:38:49.640
<v Speaker 1>regular jobs, they were wearing these They were testing them.

0:38:49.680 --> 0:38:51.960
<v Speaker 1>They were trying them out, they were adding new features,

0:38:52.000 --> 0:38:55.239
<v Speaker 1>taking old ones out when they didn't work, building apps

0:38:55.280 --> 0:38:58.920
<v Speaker 1>just for their own use, to kind of really test

0:38:58.960 --> 0:39:01.719
<v Speaker 1>the limits of what this technology could do. And then

0:39:01.760 --> 0:39:03.239
<v Speaker 1>at the end of the day they would put them

0:39:03.320 --> 0:39:06.640
<v Speaker 1>up and go home because they weren't ready for the

0:39:06.680 --> 0:39:10.360
<v Speaker 1>world to see Google Glass yet. They didn't want to

0:39:10.400 --> 0:39:13.480
<v Speaker 1>go out and start using it outside where people might

0:39:13.520 --> 0:39:15.439
<v Speaker 1>wonder what the heck is going on, and then next

0:39:15.440 --> 0:39:19.279
<v Speaker 1>thing you know, everyone's talking about it. So in two

0:39:19.320 --> 0:39:23.080
<v Speaker 1>thousand eleven, Google employees submitted the patent for the head

0:39:23.120 --> 0:39:27.040
<v Speaker 1>mounted display. The Patent Office would eventually grant that patent

0:39:27.280 --> 0:39:31.440
<v Speaker 1>in on February two thirteen, which actually is not that

0:39:31.560 --> 0:39:35.239
<v Speaker 1>long at all. That's pretty fast in many cases for

0:39:35.600 --> 0:39:39.000
<v Speaker 1>between a patent application and when it's actually granted, Um,

0:39:39.040 --> 0:39:41.960
<v Speaker 1>a couple of years is nothing. But then Google let

0:39:41.960 --> 0:39:44.360
<v Speaker 1>the cat out of the bag. In between those two dates,

0:39:45.880 --> 0:39:50.480
<v Speaker 1>in April two twelve, Google released a concept video, and

0:39:50.520 --> 0:39:52.840
<v Speaker 1>this was a video that was shown from a first

0:39:52.880 --> 0:39:55.520
<v Speaker 1>person view, so you were in the shoes of a

0:39:55.560 --> 0:39:59.840
<v Speaker 1>guy wearing some sort of device that had something to

0:39:59.880 --> 0:40:02.600
<v Speaker 1>do with Google. And the reason why I'm vague is

0:40:02.600 --> 0:40:04.799
<v Speaker 1>because the video was pretty vague. It was just giving

0:40:04.800 --> 0:40:07.160
<v Speaker 1>you an idea of what this experience might one day

0:40:07.200 --> 0:40:09.920
<v Speaker 1>be like. Clearly, it was a head melted display of

0:40:10.000 --> 0:40:13.440
<v Speaker 1>some sort with a heads up display element to it,

0:40:14.000 --> 0:40:16.799
<v Speaker 1>and it allowed this guy to send messages, to make

0:40:16.920 --> 0:40:20.400
<v Speaker 1>phone calls, to take images, to share live video with

0:40:20.480 --> 0:40:23.719
<v Speaker 1>someone else. So, in other words, the camera on this

0:40:23.800 --> 0:40:27.719
<v Speaker 1>device could feed video directly to somebody somewhere else in

0:40:27.719 --> 0:40:34.040
<v Speaker 1>the world. Ah, and you could even alert the person

0:40:34.160 --> 0:40:36.040
<v Speaker 1>of what was going on in the world around them.

0:40:36.080 --> 0:40:38.640
<v Speaker 1>So at one point, he's on his way to an

0:40:38.680 --> 0:40:41.439
<v Speaker 1>appointment and he wants to take the subway, and as

0:40:41.440 --> 0:40:43.920
<v Speaker 1>he gets close to the subway, a little alert points

0:40:44.000 --> 0:40:47.200
<v Speaker 1>up and it says their delays at the subway station,

0:40:47.200 --> 0:40:49.759
<v Speaker 1>and he's like, ah, shucks, and so he decides to

0:40:49.760 --> 0:40:54.120
<v Speaker 1>walk instead. So some of the stuff would get worked

0:40:54.160 --> 0:40:57.360
<v Speaker 1>into Google Glass, some of it wouldn't be directly worked

0:40:57.360 --> 0:41:00.600
<v Speaker 1>into Google Glass, but they could fudge it through other means.

0:41:00.880 --> 0:41:04.000
<v Speaker 1>Um But it was an interesting video and it got

0:41:04.040 --> 0:41:08.560
<v Speaker 1>a lot of people talking. It generated a lot of buzz. Now,

0:41:09.360 --> 0:41:12.839
<v Speaker 1>you might think, like with the subway example, was that

0:41:13.640 --> 0:41:19.040
<v Speaker 1>a case of machine vision understanding that the subway the

0:41:19.080 --> 0:41:22.279
<v Speaker 1>guy is walking to is a particular one in a

0:41:22.320 --> 0:41:25.520
<v Speaker 1>particular system, and that that one is one that's being

0:41:25.520 --> 0:41:29.360
<v Speaker 1>affected by delays. Uh That was not worked into Google

0:41:29.360 --> 0:41:33.080
<v Speaker 1>Glass because the camera cannot be perpetually on. If it were,

0:41:33.200 --> 0:41:37.600
<v Speaker 1>the battery would drain very very quickly. Instead, what you

0:41:37.640 --> 0:41:42.680
<v Speaker 1>could do is you could incorporate UH GPS from a

0:41:42.680 --> 0:41:47.320
<v Speaker 1>smartphone as well as a person's calendar if they've added

0:41:47.440 --> 0:41:51.640
<v Speaker 1>an appointment to their calendar, and if the phone makes

0:41:51.680 --> 0:41:54.160
<v Speaker 1>a quote unquote guess that you are on your way

0:41:54.200 --> 0:41:57.120
<v Speaker 1>to set appointment, and it notices you're getting closer to

0:41:57.360 --> 0:42:00.480
<v Speaker 1>a subway station because of your GPS coordinates, it could

0:42:00.480 --> 0:42:02.799
<v Speaker 1>then send you an alert saying, oh, we've got this

0:42:03.239 --> 0:42:07.040
<v Speaker 1>message saying that that particular subway station is experiencing delays. Now,

0:42:07.040 --> 0:42:10.960
<v Speaker 1>from your perspective, it's almost like Google Glass looked at

0:42:10.960 --> 0:42:15.040
<v Speaker 1>the subway and then said, hey, buddy, let's let's walk.

0:42:15.120 --> 0:42:16.879
<v Speaker 1>You're never gonna get there if you try and get

0:42:16.880 --> 0:42:20.080
<v Speaker 1>on the train, But in reality, it could be stuff

0:42:20.120 --> 0:42:22.200
<v Speaker 1>that's happening on the background. The nice thing is it

0:42:22.239 --> 0:42:26.399
<v Speaker 1>doesn't really matter how it happens. What matters is the experience.

0:42:26.920 --> 0:42:30.400
<v Speaker 1>Does the experience make sense? Is it compelling? Because if

0:42:30.400 --> 0:42:32.719
<v Speaker 1>it is, it doesn't matter if it was because of

0:42:32.960 --> 0:42:35.960
<v Speaker 1>machine vision or if it was because of a combination

0:42:36.320 --> 0:42:42.280
<v Speaker 1>of GPS and calendar apps and other information. The result

0:42:42.440 --> 0:42:45.120
<v Speaker 1>is the same either way. Other than the fact that

0:42:45.719 --> 0:42:48.480
<v Speaker 1>in the way I just described, it's not draining your

0:42:48.480 --> 0:42:51.000
<v Speaker 1>Google Glass batteries super fast by having the camera on

0:42:51.040 --> 0:42:55.200
<v Speaker 1>all the time. The video got a lot of attention.

0:42:55.280 --> 0:42:57.680
<v Speaker 1>People were excited about it. People wanted to know more,

0:42:58.360 --> 0:43:01.719
<v Speaker 1>but Google did not show off Google Glass at that

0:43:01.760 --> 0:43:05.680
<v Speaker 1>particular moment. They did show it off not too long

0:43:05.800 --> 0:43:08.759
<v Speaker 1>after that. They did, and they did admit they were

0:43:08.800 --> 0:43:11.880
<v Speaker 1>working on an augmented reality project and they wanted to

0:43:11.920 --> 0:43:14.600
<v Speaker 1>get feedback from people about how they would use it

0:43:15.120 --> 0:43:19.920
<v Speaker 1>and what they thought about this concept. A couple of

0:43:19.960 --> 0:43:24.160
<v Speaker 1>months later, they held the Google Io Developer Conference. I've

0:43:24.200 --> 0:43:27.880
<v Speaker 1>been to one of these. They're very very nerdy. It

0:43:28.040 --> 0:43:33.000
<v Speaker 1>is interesting. It gets incredibly technical, very fast, because it's

0:43:33.080 --> 0:43:37.239
<v Speaker 1>meant for people who are developing apps for Google platforms.

0:43:38.160 --> 0:43:41.480
<v Speaker 1>The event took place in San Francisco's Moscone Center, and

0:43:41.640 --> 0:43:45.359
<v Speaker 1>high above the center was a blimp with several skydivers

0:43:45.360 --> 0:43:48.480
<v Speaker 1>and wingsuits and parachutes, and each person in that group

0:43:48.520 --> 0:43:50.520
<v Speaker 1>was wearing a pair of Google Glass. And in the

0:43:50.560 --> 0:43:53.520
<v Speaker 1>middle of a totally different presentation, Sarah a Brand runs

0:43:53.560 --> 0:43:55.520
<v Speaker 1>up on stage and he says, I'm sorry to interrupt,

0:43:55.760 --> 0:43:58.760
<v Speaker 1>but we've got a time sensitive event going on right now,

0:43:59.120 --> 0:44:02.080
<v Speaker 1>and he switches to video showing the blimp above the

0:44:02.120 --> 0:44:05.200
<v Speaker 1>Mousconi Center. Then they switch to a camera inside the

0:44:05.239 --> 0:44:07.480
<v Speaker 1>blimp itself and you see the team there, and you

0:44:07.520 --> 0:44:09.560
<v Speaker 1>see that each member of the team is wearing a

0:44:09.560 --> 0:44:14.280
<v Speaker 1>pair of Google Glass. They start a Google hangout using

0:44:14.280 --> 0:44:16.920
<v Speaker 1>their Google Glass, and then you can see the screens

0:44:16.960 --> 0:44:19.920
<v Speaker 1>from each of their perspectives. So now you're getting a

0:44:19.960 --> 0:44:23.360
<v Speaker 1>first person view of these people who are inside the blimp.

0:44:23.719 --> 0:44:26.200
<v Speaker 1>And eventually, once the blimp is in the right location,

0:44:26.440 --> 0:44:29.040
<v Speaker 1>they make a jump. They jump out of the blimp,

0:44:29.360 --> 0:44:33.279
<v Speaker 1>they fall, they launched their shoots, they land on the

0:44:33.360 --> 0:44:36.960
<v Speaker 1>roof of the Muscony Center. They hand over a package

0:44:37.360 --> 0:44:40.720
<v Speaker 1>to a person riding a mountain bike and he's also

0:44:40.800 --> 0:44:43.880
<v Speaker 1>got Google glass on. He rides over to the edge

0:44:43.960 --> 0:44:47.239
<v Speaker 1>of the building, switches over into repelling gear, repels down

0:44:47.280 --> 0:44:50.640
<v Speaker 1>the side, gets inside the Mousconi Center, gets on a

0:44:50.680 --> 0:44:55.640
<v Speaker 1>different mountain bike, rides over into the conference room, down

0:44:55.680 --> 0:44:59.080
<v Speaker 1>the aisle, straight over to the stage, and bring Serage

0:44:59.239 --> 0:45:03.359
<v Speaker 1>brand package that has inside of it a fresh pair

0:45:03.400 --> 0:45:07.920
<v Speaker 1>of Google glass. It was a heck of a demo.

0:45:09.120 --> 0:45:12.800
<v Speaker 1>I watched it live, not in the Mosconi Center. I

0:45:12.880 --> 0:45:15.320
<v Speaker 1>was watching it remotely. I was not at that particular

0:45:15.360 --> 0:45:17.600
<v Speaker 1>io event, and my jaw was on the floor to

0:45:17.760 --> 0:45:24.280
<v Speaker 1>see this display of wearable technology in such a cool application.

0:45:24.600 --> 0:45:26.840
<v Speaker 1>You know, this this Google hangout that's showing me what

0:45:26.960 --> 0:45:30.719
<v Speaker 1>it's like to skydive from a first person perspective. And

0:45:30.760 --> 0:45:34.360
<v Speaker 1>then this journey from the seat the roof of the

0:45:34.400 --> 0:45:42.200
<v Speaker 1>building down into the center itself. It was an effective demonstration. Now,

0:45:42.200 --> 0:45:45.200
<v Speaker 1>in August, Google would receive a patent. Now this was

0:45:45.239 --> 0:45:47.800
<v Speaker 1>not the same one for the head mounted display patent

0:45:48.000 --> 0:45:51.040
<v Speaker 1>that one wouldn't be granted until two thirteen, But this

0:45:51.080 --> 0:45:53.239
<v Speaker 1>was a patent for a process and the title of

0:45:53.280 --> 0:45:57.200
<v Speaker 1>the patent was unlocking a screen using eye tracking information.

0:45:58.280 --> 0:46:01.879
<v Speaker 1>So this would requireing some sort of camera facing back

0:46:01.960 --> 0:46:06.719
<v Speaker 1>toward a person's eye, and it would look at motions

0:46:06.840 --> 0:46:10.320
<v Speaker 1>of the eye and interpret that as various commands, including

0:46:10.440 --> 0:46:13.880
<v Speaker 1>unlocking a device. So you may have had a smartphone

0:46:13.880 --> 0:46:16.440
<v Speaker 1>at some point that allowed you to create a pattern

0:46:16.719 --> 0:46:20.319
<v Speaker 1>by tracing something on a screen. An old Android one

0:46:20.360 --> 0:46:23.560
<v Speaker 1>I used to use had a a grid of dots,

0:46:24.120 --> 0:46:27.480
<v Speaker 1>and you would connect dots in a particular pattern, set

0:46:27.560 --> 0:46:30.759
<v Speaker 1>that as your pattern of choice, and every time you

0:46:30.760 --> 0:46:32.719
<v Speaker 1>want to unlock the phone from that point forward, you

0:46:32.719 --> 0:46:35.080
<v Speaker 1>had to retrace that pattern. But you could do the

0:46:35.120 --> 0:46:39.719
<v Speaker 1>same thing with eye tracking if you had a virtual

0:46:40.040 --> 0:46:45.120
<v Speaker 1>display of dots and you stared at one dot until

0:46:45.239 --> 0:46:47.879
<v Speaker 1>the camera had picked up and acknowledged yes, you're looking

0:46:47.920 --> 0:46:49.920
<v Speaker 1>at the correct one, and then you just move your

0:46:49.920 --> 0:46:51.959
<v Speaker 1>eye from dot to dot, and this is like moving

0:46:52.000 --> 0:46:54.440
<v Speaker 1>your finger from dot to dot, and you could unlock

0:46:54.440 --> 0:46:58.200
<v Speaker 1>a screen in that way. That's just one particular approach

0:46:58.239 --> 0:47:00.720
<v Speaker 1>that you could use to unlock a screen use eye tracking.

0:47:02.080 --> 0:47:06.400
<v Speaker 1>This particular type of feature would not be included with

0:47:06.400 --> 0:47:08.400
<v Speaker 1>Google Glass, but it shows the kind of stuff they

0:47:08.440 --> 0:47:11.200
<v Speaker 1>were thinking about while they were putting all this together.

0:47:11.760 --> 0:47:14.120
<v Speaker 1>Yet Another pattern revealed what Google hoped to do with

0:47:14.160 --> 0:47:18.239
<v Speaker 1>Project Glass, and it used gestures. So these would be

0:47:18.280 --> 0:47:21.200
<v Speaker 1>hand gestures, actual hand gestures you would make in front

0:47:21.200 --> 0:47:25.239
<v Speaker 1>of your face lack of crazy person in order to

0:47:25.320 --> 0:47:28.120
<v Speaker 1>send commands to your Google Glass. So let's say you

0:47:28.200 --> 0:47:32.640
<v Speaker 1>see something on the street and you like it, it

0:47:32.719 --> 0:47:36.360
<v Speaker 1>could happen. Maybe you see a poster for a band

0:47:36.600 --> 0:47:39.200
<v Speaker 1>that you like and it's they're coming up with a

0:47:39.200 --> 0:47:42.800
<v Speaker 1>a show nearby. You could make a little heart shape

0:47:42.880 --> 0:47:48.520
<v Speaker 1>with your hand. Awe, so cute, you Millennials, And then

0:47:48.880 --> 0:47:51.080
<v Speaker 1>this would end up being picked up by the camera

0:47:51.320 --> 0:47:54.640
<v Speaker 1>and interpreted as liking the thing you are looking at.

0:47:54.800 --> 0:47:57.880
<v Speaker 1>Maybe it posts to a social media page saying, Jonathan

0:47:58.000 --> 0:48:00.520
<v Speaker 1>likes the fact that they might be bians is going

0:48:00.560 --> 0:48:03.480
<v Speaker 1>to be in Atlanta the Variety Playhouse playing a show,

0:48:03.880 --> 0:48:06.520
<v Speaker 1>and yes, I would like that. I love they might

0:48:06.560 --> 0:48:09.760
<v Speaker 1>be giants and the Variety Playhouse is a delightful venue.

0:48:10.680 --> 0:48:12.120
<v Speaker 1>I don't know that I would go so far as

0:48:12.160 --> 0:48:14.040
<v Speaker 1>to make the little heart shape of my hands, though

0:48:14.719 --> 0:48:18.400
<v Speaker 1>I do have my limits. But this shows another way

0:48:18.560 --> 0:48:23.520
<v Speaker 1>of how Google was thinking about interactions with its technology

0:48:23.560 --> 0:48:26.520
<v Speaker 1>and ways that you could control it beyond just using

0:48:26.600 --> 0:48:31.080
<v Speaker 1>a capacity, touchscreen or even voice commands. That also would

0:48:31.120 --> 0:48:33.759
<v Speaker 1>not find its way into Google Glass, but it might

0:48:33.800 --> 0:48:37.520
<v Speaker 1>find its way into some future Google product. Now, next

0:48:37.560 --> 0:48:40.560
<v Speaker 1>we'll explore a bit with Google Glass, and we will

0:48:40.600 --> 0:48:44.200
<v Speaker 1>pay handsomely for it. But before I jump into that,

0:48:44.719 --> 0:48:55.880
<v Speaker 1>let's take another quick break to thank our sponsor. In

0:48:56.000 --> 0:49:00.280
<v Speaker 1>a Google would open up an extremely limited program called

0:49:00.560 --> 0:49:04.000
<v Speaker 1>Glass Explorers. So I guess actually it was dragon Con,

0:49:04.880 --> 0:49:08.759
<v Speaker 1>not dragon Con, which totally makes sense. I can't tell

0:49:08.760 --> 0:49:11.600
<v Speaker 1>those years apart dragon Con to dragon Con, they all

0:49:11.640 --> 0:49:17.200
<v Speaker 1>bleed together. But this, this program, the Glass Explorer's program,

0:49:17.440 --> 0:49:20.200
<v Speaker 1>was a pilot testing program. It was really a beta

0:49:20.239 --> 0:49:23.120
<v Speaker 1>test for the technology itself, and you had to apply

0:49:23.560 --> 0:49:25.680
<v Speaker 1>to be in it. You actually had to fill out

0:49:25.719 --> 0:49:29.640
<v Speaker 1>an online form to explain how you would use Google

0:49:29.680 --> 0:49:33.080
<v Speaker 1>Glass and why you think you would be a good

0:49:33.120 --> 0:49:36.399
<v Speaker 1>candidate for the Glass Explorer program. And not only that,

0:49:36.760 --> 0:49:38.839
<v Speaker 1>but you had to pay for it. You couldn't just

0:49:39.080 --> 0:49:43.560
<v Speaker 1>get a pair. They cost one thousand, five hundred dollars

0:49:44.440 --> 0:49:48.080
<v Speaker 1>dollars for a pair of Google Glass. Now, the application

0:49:48.120 --> 0:49:50.640
<v Speaker 1>process was pretty simple, but it meant that Google could

0:49:51.000 --> 0:49:54.520
<v Speaker 1>very quickly go through these this huge number of applications

0:49:54.520 --> 0:49:56.920
<v Speaker 1>in the site, which one sounds like good choices and

0:49:56.960 --> 0:50:01.880
<v Speaker 1>which ones don't. Now. In my case, our company bought

0:50:01.920 --> 0:50:04.279
<v Speaker 1>the pair of Google glass. I applied for them, but

0:50:04.400 --> 0:50:06.640
<v Speaker 1>it was a company purchase, so I don't actually own

0:50:06.680 --> 0:50:10.879
<v Speaker 1>those Google glass anymore, but I was able to buy something.

0:50:10.920 --> 0:50:13.279
<v Speaker 1>Not going to tell you a funny little story that

0:50:13.400 --> 0:50:16.240
<v Speaker 1>happened to me, And this is all because Jonathan doesn't

0:50:16.239 --> 0:50:20.960
<v Speaker 1>pay enough attention when he fills out online forms. So

0:50:21.040 --> 0:50:22.680
<v Speaker 1>in the United States, there were a couple of different

0:50:22.680 --> 0:50:25.920
<v Speaker 1>places you could pick up a pair of these glasses

0:50:26.600 --> 0:50:29.120
<v Speaker 1>once you ordered them, and you had to physically go

0:50:29.800 --> 0:50:32.800
<v Speaker 1>to these locations. Google did not want to send anything

0:50:32.840 --> 0:50:35.319
<v Speaker 1>to anyone because they didn't want to deal with a

0:50:35.360 --> 0:50:41.480
<v Speaker 1>case of someone intercepting a shipment and stealing it or

0:50:41.600 --> 0:50:44.600
<v Speaker 1>selling it or breaking it apart or whatever. They wanted

0:50:44.600 --> 0:50:47.200
<v Speaker 1>to keep a tight rein on who actually got their

0:50:47.200 --> 0:50:49.759
<v Speaker 1>hands on these Google glass So as part of that,

0:50:49.800 --> 0:50:52.440
<v Speaker 1>you had to go to one of these physical locations

0:50:52.440 --> 0:50:54.440
<v Speaker 1>to pick up your pair. They did not have one

0:50:54.480 --> 0:50:57.120
<v Speaker 1>in Atlanta, which is where I live. They had them

0:50:57.120 --> 0:51:01.440
<v Speaker 1>in Los Angeles, in San Francisco, and New York. Out

0:51:01.480 --> 0:51:03.360
<v Speaker 1>of those, New York is the easiest for me. To

0:51:03.400 --> 0:51:06.240
<v Speaker 1>get to New York is a couple of hours flight

0:51:06.480 --> 0:51:09.760
<v Speaker 1>from Atlanta. If I want to go to San Francisco

0:51:09.840 --> 0:51:12.719
<v Speaker 1>or Los Angeles, you're talking four or five hours each way.

0:51:13.960 --> 0:51:17.319
<v Speaker 1>So I decided I would pick up my Google Glass

0:51:17.360 --> 0:51:19.360
<v Speaker 1>in New York, and I filled out the form and

0:51:19.360 --> 0:51:21.920
<v Speaker 1>I indicated the day and location where I wanted to

0:51:21.920 --> 0:51:25.440
<v Speaker 1>pick it up. But then I realized something I had

0:51:25.480 --> 0:51:28.360
<v Speaker 1>double booked myself. Something else was happening the day that

0:51:28.480 --> 0:51:31.680
<v Speaker 1>I had chosen, and Google Glass would allow you to

0:51:31.800 --> 0:51:37.279
<v Speaker 1>change your delivery date one time only. That's it. So

0:51:37.320 --> 0:51:39.560
<v Speaker 1>if you messed up, you can change it once and

0:51:39.600 --> 0:51:41.799
<v Speaker 1>that's all you could do. So I go back on

0:51:41.840 --> 0:51:44.359
<v Speaker 1>there and I'm like, well, I can't take this day

0:51:44.360 --> 0:51:45.960
<v Speaker 1>that I thought I was gonna do. I'm gonna do

0:51:46.000 --> 0:51:49.440
<v Speaker 1>this other day. So I chose a different day. I

0:51:49.480 --> 0:51:52.200
<v Speaker 1>did not realize, however, that by choosing a different day,

0:51:53.000 --> 0:51:56.839
<v Speaker 1>my choice of destination got reset to the default, which

0:51:56.880 --> 0:52:01.719
<v Speaker 1>was Los Angeles. So instead of rescheduling to flight in

0:52:01.800 --> 0:52:05.319
<v Speaker 1>New York, I rescheduled to fly to l A. So

0:52:05.360 --> 0:52:09.400
<v Speaker 1>I actually had to fly to Los Angeles, go to Venice, California,

0:52:09.480 --> 0:52:12.640
<v Speaker 1>which is where Google has an office, and pick up

0:52:12.640 --> 0:52:16.279
<v Speaker 1>my pair of Google Glass. Bright side of it is

0:52:17.200 --> 0:52:19.439
<v Speaker 1>the day after I got my Google Glass, I got

0:52:19.480 --> 0:52:21.480
<v Speaker 1>to really try it out at the happiest place on

0:52:21.520 --> 0:52:24.719
<v Speaker 1>Earth because I went to Disneyland and I brought my

0:52:24.760 --> 0:52:30.160
<v Speaker 1>Google Glass with me. So funny, stupid story about Jonathan

0:52:30.200 --> 0:52:32.960
<v Speaker 1>not paying attention. Moral of the story is pay attention

0:52:33.000 --> 0:52:37.839
<v Speaker 1>on your online forms, especially if you have to resubmit anyway.

0:52:38.880 --> 0:52:43.120
<v Speaker 1>Back in those days, I still wore eyeglasses. I've had

0:52:43.239 --> 0:52:46.120
<v Speaker 1>lazing eye surgery since then, but back in when I

0:52:46.160 --> 0:52:49.000
<v Speaker 1>got the Google Glass, I store still wore eyeglasses, and

0:52:49.360 --> 0:52:52.120
<v Speaker 1>Google Glass at that point had not been outfitted to

0:52:52.239 --> 0:52:56.680
<v Speaker 1>work with existing pairs of glasses. You could either wear

0:52:56.760 --> 0:52:59.120
<v Speaker 1>Google Glass or you could wear a pair of glasses,

0:52:59.120 --> 0:53:01.680
<v Speaker 1>but you couldn't really do both unless you worked for

0:53:01.719 --> 0:53:04.680
<v Speaker 1>Google like Sarah a brand, and you could have someone

0:53:04.800 --> 0:53:08.680
<v Speaker 1>might make a custom pair for you, so instead I

0:53:08.719 --> 0:53:10.640
<v Speaker 1>would have to wear contact lenses. This was one of

0:53:10.680 --> 0:53:13.480
<v Speaker 1>those early complaints about the Google Glass program. A lot

0:53:13.480 --> 0:53:17.680
<v Speaker 1>of people wanted to be able to attach the Google

0:53:17.760 --> 0:53:20.239
<v Speaker 1>Glass part to an existing pair of glasses, and there

0:53:20.280 --> 0:53:23.400
<v Speaker 1>was just no way you could do that. In May,

0:53:23.880 --> 0:53:26.680
<v Speaker 1>Google opened up the Explorer program and allowed more folks

0:53:26.719 --> 0:53:30.560
<v Speaker 1>to join, and there were talks of special Google Glass stores,

0:53:30.760 --> 0:53:34.120
<v Speaker 1>including floating barges off the coast of places like San

0:53:34.160 --> 0:53:36.719
<v Speaker 1>Francisco and New York. And these were meant to be

0:53:36.760 --> 0:53:40.480
<v Speaker 1>interactive text spaces and perhaps even a high end luxury

0:53:40.600 --> 0:53:45.800
<v Speaker 1>show room for Google Glass. But by June, so mayen

0:53:45.840 --> 0:53:48.480
<v Speaker 1>this is all in the news, and in fact, the

0:53:48.520 --> 0:53:50.600
<v Speaker 1>barges have been kind of coming together over the last

0:53:50.600 --> 0:53:53.480
<v Speaker 1>couple of years. But in June, the plans for the

0:53:53.520 --> 0:53:57.480
<v Speaker 1>barges were I guess scuttled is a good word if

0:53:57.480 --> 0:54:00.720
<v Speaker 1>we're talking about barges. The plans were uttle. The barges

0:54:00.760 --> 0:54:05.920
<v Speaker 1>weren't scuttled immediately, but the plans were. They never saw service,

0:54:05.960 --> 0:54:09.640
<v Speaker 1>they never came online, they never became stores. Uh. They

0:54:09.640 --> 0:54:11.600
<v Speaker 1>did raise a lot of interest as people watched them

0:54:11.680 --> 0:54:14.920
<v Speaker 1>take form on a daily basis, but they disappeared with

0:54:14.960 --> 0:54:17.520
<v Speaker 1>about as much of a whimper as could be. They

0:54:17.600 --> 0:54:22.520
<v Speaker 1>were never really explained, and so they kind of started

0:54:22.560 --> 0:54:25.399
<v Speaker 1>to become something and then went away before anyone could

0:54:25.400 --> 0:54:27.680
<v Speaker 1>really figure out what exactly they were going to to

0:54:27.760 --> 0:54:35.360
<v Speaker 1>turn into. In January, Google pulled the plug on the

0:54:35.400 --> 0:54:40.879
<v Speaker 1>Explorer program because ultimately it had been a failure, but

0:54:40.960 --> 0:54:44.799
<v Speaker 1>not necessarily for the reasons you might think. So let's

0:54:44.840 --> 0:54:49.560
<v Speaker 1>rewind a little bit. It's two thousand twelve and Project

0:54:49.600 --> 0:54:54.239
<v Speaker 1>Glass has a divided team. You've got two main camps

0:54:54.480 --> 0:54:58.799
<v Speaker 1>of engineers who are disagreeing about a fundamental aspect of

0:54:58.840 --> 0:55:02.960
<v Speaker 1>Google Glass. One team thinks this should be a persistent

0:55:03.080 --> 0:55:05.919
<v Speaker 1>wearable device, meaning you put it on and you wear

0:55:05.960 --> 0:55:09.080
<v Speaker 1>it all day long. It's like a fashion accessory, it

0:55:09.120 --> 0:55:13.600
<v Speaker 1>belongs as part of your outfit. The other team disagrees

0:55:13.640 --> 0:55:15.680
<v Speaker 1>and says no, this should be something that you're using

0:55:15.719 --> 0:55:19.160
<v Speaker 1>for specific use cases. So a situation comes up when

0:55:19.200 --> 0:55:21.879
<v Speaker 1>you would need Google Glass. That's when you put it on,

0:55:22.040 --> 0:55:24.120
<v Speaker 1>and then when that's over, you take it off again.

0:55:24.920 --> 0:55:28.520
<v Speaker 1>The two can't agree with which direction they should go in.

0:55:29.719 --> 0:55:33.200
<v Speaker 1>Sarah ga Brenn, who's excited about the technology but impatient

0:55:33.280 --> 0:55:35.520
<v Speaker 1>to wait and get all of this sussed out, has

0:55:35.560 --> 0:55:38.439
<v Speaker 1>an idea. Instead of relying on a relatively small group

0:55:38.480 --> 0:55:43.560
<v Speaker 1>of engineers and developers, why not create a beta testing program,

0:55:43.760 --> 0:55:46.279
<v Speaker 1>invite a wider group of people to use it in

0:55:46.360 --> 0:55:49.960
<v Speaker 1>the real world, and take that information as a way

0:55:50.000 --> 0:55:53.640
<v Speaker 1>of developing it further. So, in other words, you open

0:55:53.719 --> 0:55:56.680
<v Speaker 1>this up. You get a lot more information from a

0:55:56.719 --> 0:55:59.680
<v Speaker 1>lot more people using it in a lot of different situations,

0:56:00.080 --> 0:56:02.320
<v Speaker 1>and you see where it works and where it doesn't work,

0:56:02.440 --> 0:56:05.000
<v Speaker 1>and you make changes. If it works in one case,

0:56:05.120 --> 0:56:07.440
<v Speaker 1>maybe you pursue that a little more. If it doesn't

0:56:07.440 --> 0:56:10.439
<v Speaker 1>work in another, maybe you change gears or you try

0:56:10.480 --> 0:56:12.719
<v Speaker 1>to figure out a way to make it work in

0:56:12.760 --> 0:56:16.640
<v Speaker 1>that situation. But the point was opening it up to

0:56:16.920 --> 0:56:21.000
<v Speaker 1>more people meant more information, and more information meant that

0:56:21.040 --> 0:56:24.799
<v Speaker 1>they could make better decisions. And this was not a

0:56:24.920 --> 0:56:29.040
<v Speaker 1>bad idea. It could teach Google how people would use

0:56:29.040 --> 0:56:32.360
<v Speaker 1>the technology and where they should concentrate on building out features.

0:56:32.880 --> 0:56:35.520
<v Speaker 1>It was really just a larger part of the overall

0:56:35.560 --> 0:56:38.840
<v Speaker 1>Google Glass experiment, only there was a small problem. The

0:56:38.920 --> 0:56:43.080
<v Speaker 1>unveiling of Google Glass made it a prestige item. The

0:56:43.160 --> 0:56:46.160
<v Speaker 1>way they showed it off and the way they rolled

0:56:46.200 --> 0:56:50.760
<v Speaker 1>it out meant that it became an object of exclusivity.

0:56:52.200 --> 0:56:54.080
<v Speaker 1>You had to apply to be in the club for

0:56:54.160 --> 0:56:56.920
<v Speaker 1>one thing, so people were either in it or they weren't.

0:56:57.960 --> 0:57:01.400
<v Speaker 1>You had to pay for it, which meant that you

0:57:01.440 --> 0:57:04.000
<v Speaker 1>needed to have a pretty good amount of discretionary income

0:57:04.000 --> 0:57:07.400
<v Speaker 1>if you're going to buy something like this. Wearing Google

0:57:07.400 --> 0:57:10.520
<v Speaker 1>Glass didn't just say I'm interested in technology. It also

0:57:10.560 --> 0:57:13.399
<v Speaker 1>said I have the money to blow on something that

0:57:13.480 --> 0:57:17.920
<v Speaker 1>hasn't even become a product yet. And it also said

0:57:18.400 --> 0:57:21.880
<v Speaker 1>I'm in a club and you aren't. And on top

0:57:21.920 --> 0:57:25.280
<v Speaker 1>of that, people began to express concerns about privacy issues.

0:57:26.200 --> 0:57:28.480
<v Speaker 1>I mean, how could someone feel like they could maintain

0:57:28.480 --> 0:57:31.000
<v Speaker 1>any sort of sense of privacy if they're going out

0:57:31.040 --> 0:57:34.000
<v Speaker 1>in public and other people have cameras mounted on their

0:57:34.040 --> 0:57:36.720
<v Speaker 1>faces all the time. I mean, that's what Google glass was.

0:57:36.760 --> 0:57:40.120
<v Speaker 1>In part. It was an external camera pointing outward at

0:57:40.120 --> 0:57:43.680
<v Speaker 1>the world from the perspective of the person wearing it. Now,

0:57:43.880 --> 0:57:47.320
<v Speaker 1>Google Glass had included a light to indicate whether the

0:57:47.360 --> 0:57:50.200
<v Speaker 1>camera was on or not, so that way people could

0:57:50.200 --> 0:57:53.560
<v Speaker 1>see if perhaps video was being recorded or streamed live

0:57:53.640 --> 0:57:56.760
<v Speaker 1>over the internet, or if photo was being taken, and

0:57:56.760 --> 0:58:00.400
<v Speaker 1>if the light was off, then presumably it wasn't. Now

0:58:00.440 --> 0:58:04.120
<v Speaker 1>I would encounter strangers who would see me wearing these

0:58:04.160 --> 0:58:07.240
<v Speaker 1>glasses and they thought it was the most amazing thing ever.

0:58:07.440 --> 0:58:10.800
<v Speaker 1>And the day I received my parent Los Angeles, it

0:58:10.840 --> 0:58:13.440
<v Speaker 1>was like I was being treated as a celebrity. People

0:58:13.440 --> 0:58:15.800
<v Speaker 1>were stopping me to ask about the Google Glass. They

0:58:15.840 --> 0:58:18.640
<v Speaker 1>wanted to learn more. They were fascinated by the technology.

0:58:18.720 --> 0:58:21.640
<v Speaker 1>They wanted me to take pictures of them using it.

0:58:22.400 --> 0:58:24.960
<v Speaker 1>But then I got home and I got around my friends.

0:58:26.080 --> 0:58:28.280
<v Speaker 1>My friends were different because I hung out with my

0:58:28.280 --> 0:58:30.960
<v Speaker 1>friends all the time. They knew me. But now I've

0:58:30.960 --> 0:58:33.920
<v Speaker 1>got a camera on my face pointed at them, and

0:58:34.040 --> 0:58:36.440
<v Speaker 1>more than once I had friends asked me if I

0:58:36.520 --> 0:58:38.520
<v Speaker 1>might take off the Google Glass while I had a

0:58:38.520 --> 0:58:41.800
<v Speaker 1>conversation with them, because they didn't feel comfortable with the

0:58:41.800 --> 0:58:44.320
<v Speaker 1>thought of a camera looking at them, even if the

0:58:44.320 --> 0:58:47.200
<v Speaker 1>camera was demonstrably off. If they knew for a fact

0:58:47.320 --> 0:58:50.680
<v Speaker 1>I wasn't using Google Glass, it was still uncomfortable. And

0:58:50.760 --> 0:58:53.000
<v Speaker 1>this was a problem that was widespread. It wasn't just

0:58:53.080 --> 0:58:59.520
<v Speaker 1>anecdotal in my case. So people who were in this

0:58:59.600 --> 0:59:03.200
<v Speaker 1>program um began to be called a new name. The

0:59:03.280 --> 0:59:08.960
<v Speaker 1>official name was Glass Explorer, but the new name was Glasshole.

0:59:11.560 --> 0:59:16.040
<v Speaker 1>That hurt. The technology was not ready for a full

0:59:16.080 --> 0:59:18.800
<v Speaker 1>consumer product. It was never intended to be that. It

0:59:18.880 --> 0:59:22.960
<v Speaker 1>was meant to be a test bed for this technology.

0:59:23.120 --> 0:59:25.600
<v Speaker 1>And if you've got involved in the program, and if

0:59:25.600 --> 0:59:28.200
<v Speaker 1>you were honest with yourself about what you were doing

0:59:28.240 --> 0:59:31.640
<v Speaker 1>and what the product was for, what the Google Glass

0:59:31.720 --> 0:59:34.280
<v Speaker 1>was for You should have been fine with that. You

0:59:34.400 --> 0:59:37.080
<v Speaker 1>knew from the get go that this was a testing

0:59:37.520 --> 0:59:41.160
<v Speaker 1>phase of the technology, not something that was ready for

0:59:41.240 --> 0:59:45.000
<v Speaker 1>prime time. But people began to get frustrated with glasses

0:59:45.080 --> 0:59:48.520
<v Speaker 1>limited utility. They'd say, like, after a couple of months,

0:59:48.600 --> 0:59:52.160
<v Speaker 1>they just stopped wearing them because really, I mean, you've

0:59:52.160 --> 0:59:54.040
<v Speaker 1>got a camera in your pocket already, why do you

0:59:54.040 --> 0:59:57.600
<v Speaker 1>need another one. They weren't putting Google Glass through more

0:59:57.640 --> 1:00:00.640
<v Speaker 1>and more uses, which meant that the program was becoming

1:00:00.840 --> 1:00:06.040
<v Speaker 1>decreasingly important over at Google. They were getting less data,

1:00:06.360 --> 1:00:08.040
<v Speaker 1>which is what they needed in the first place to

1:00:08.080 --> 1:00:14.920
<v Speaker 1>make Google Glass a successful consumer product. So there wasn't

1:00:14.960 --> 1:00:19.600
<v Speaker 1>just enough. They're there to keep people's interest, and the

1:00:19.640 --> 1:00:22.520
<v Speaker 1>wrong sort of folks had jumped into the program. And

1:00:22.520 --> 1:00:24.400
<v Speaker 1>by wrong sort of folks, I mean people who thought

1:00:24.440 --> 1:00:26.880
<v Speaker 1>it was a prestigious thing to be in this club,

1:00:27.720 --> 1:00:31.360
<v Speaker 1>who spent the money as a way of having something

1:00:31.400 --> 1:00:34.280
<v Speaker 1>that other people did not have, not as a way

1:00:34.280 --> 1:00:36.880
<v Speaker 1>of expanding the technology, but as a way of expanding

1:00:36.880 --> 1:00:41.680
<v Speaker 1>their own status among others. And so interest in support

1:00:41.760 --> 1:00:45.240
<v Speaker 1>began to wane, both inside and outside the company. But

1:00:45.320 --> 1:00:49.160
<v Speaker 1>Glass did not disappear lots of those features became incorporated

1:00:49.160 --> 1:00:52.080
<v Speaker 1>into other stuff like Android and Google Home. The phrase

1:00:52.160 --> 1:00:55.760
<v Speaker 1>okay Google is still used to activate Google's Assistant, which

1:00:55.760 --> 1:00:57.480
<v Speaker 1>could be on the phone, it could be on Google Home,

1:00:57.520 --> 1:00:59.640
<v Speaker 1>it could be on other devices. And I apologize if

1:00:59.680 --> 1:01:01.880
<v Speaker 1>once a again I woke it up for those of

1:01:01.880 --> 1:01:06.480
<v Speaker 1>you who have Android devices nearby, and that can do

1:01:06.520 --> 1:01:09.400
<v Speaker 1>a lot of different stuff depending upon what Google Assistant

1:01:09.440 --> 1:01:12.160
<v Speaker 1>is running on. For example, at home, I can use

1:01:12.200 --> 1:01:14.360
<v Speaker 1>it to listen to different types of music or control

1:01:14.400 --> 1:01:17.200
<v Speaker 1>my lights on my phone. I can do all sorts

1:01:17.240 --> 1:01:22.720
<v Speaker 1>of different types of features. And you might even encounter

1:01:23.160 --> 1:01:27.760
<v Speaker 1>Google hardware Glass hardware in certain industries because, believe it

1:01:27.880 --> 1:01:30.920
<v Speaker 1>or not, Google Glass does still exist. Google still produces

1:01:30.960 --> 1:01:35.240
<v Speaker 1>them and still licenses it out, but only to other companies.

1:01:35.240 --> 1:01:37.640
<v Speaker 1>It's a business to business product now, it's not a

1:01:37.640 --> 1:01:41.680
<v Speaker 1>consumer product. This is a program called Google at our

1:01:41.800 --> 1:01:45.320
<v Speaker 1>Glass at work, I should say Glass at work. So

1:01:45.440 --> 1:01:48.560
<v Speaker 1>rather than this consumer product, this is a device that

1:01:48.640 --> 1:01:51.840
<v Speaker 1>gives real world assistant to people working in various industries,

1:01:52.920 --> 1:01:55.600
<v Speaker 1>and it all depends upon the augmented reality apps that

1:01:55.680 --> 1:01:58.840
<v Speaker 1>the glasses are running. But it could be something like

1:01:58.880 --> 1:02:02.200
<v Speaker 1>what I was talking about before, with mechanics, giving real time,

1:02:02.680 --> 1:02:06.240
<v Speaker 1>overlaid information on how to do a repair, or how

1:02:06.320 --> 1:02:08.840
<v Speaker 1>to take a part an engine, or how to build one.

1:02:09.840 --> 1:02:12.240
<v Speaker 1>It could be for medical use, it could be even

1:02:12.280 --> 1:02:15.160
<v Speaker 1>just for corporate use. There are a lot of reasons

1:02:15.200 --> 1:02:19.760
<v Speaker 1>that Google Glass could come in handy. So it is

1:02:19.800 --> 1:02:23.640
<v Speaker 1>still around. It's just not a prestige product for glass holes.

1:02:24.960 --> 1:02:29.040
<v Speaker 1>Now it's doing real work. The sad thing is, I

1:02:29.040 --> 1:02:31.880
<v Speaker 1>bet Google Glasses progress would be much further along if

1:02:31.920 --> 1:02:34.400
<v Speaker 1>there had not been such a hoopla about it when

1:02:34.400 --> 1:02:37.680
<v Speaker 1>it was first launched. If it had been launched more

1:02:37.840 --> 1:02:41.560
<v Speaker 1>like we're trying to develop this technology and less like

1:02:41.600 --> 1:02:45.320
<v Speaker 1>a rock star, then maybe people wouldn't have gotten so

1:02:45.440 --> 1:02:48.400
<v Speaker 1>wrapped up in it, And maybe that means that Google

1:02:48.440 --> 1:02:51.560
<v Speaker 1>would have been able to get more helpful information from

1:02:51.560 --> 1:02:53.840
<v Speaker 1>people who are really using the technology the way it

1:02:53.880 --> 1:02:57.760
<v Speaker 1>was intended, and maybe we would see Google Glass much

1:02:57.800 --> 1:02:59.760
<v Speaker 1>further in development, and maybe it would even be a

1:02:59.760 --> 1:03:04.280
<v Speaker 1>con sumer product. I'm sure it was discouraging to the

1:03:04.320 --> 1:03:09.560
<v Speaker 1>Google Glass team to see how things went awry, but

1:03:10.440 --> 1:03:13.520
<v Speaker 1>it does still exist and a R is still a thing.

1:03:14.360 --> 1:03:17.320
<v Speaker 1>There are related products that are also pushing augmented reality

1:03:17.320 --> 1:03:20.560
<v Speaker 1>into a new era. There's Microsoft's hollow lens. That's a

1:03:20.600 --> 1:03:23.520
<v Speaker 1>great example. There's Magic Leap, about which we know very

1:03:23.560 --> 1:03:27.360
<v Speaker 1>little bits and pieces of information leak out over time,

1:03:27.880 --> 1:03:30.560
<v Speaker 1>but we're always learning a little bit more. But I'm

1:03:30.560 --> 1:03:32.800
<v Speaker 1>always going to have a soft spot in my heart

1:03:33.120 --> 1:03:37.760
<v Speaker 1>for Google Glass. It's something that I think of and

1:03:37.800 --> 1:03:41.480
<v Speaker 1>it's something that I think if it had just had

1:03:41.560 --> 1:03:46.040
<v Speaker 1>a little bit of a lower key rollout, we'd be

1:03:46.040 --> 1:03:48.680
<v Speaker 1>looking at a very different world with wearables right now,

1:03:49.280 --> 1:03:53.040
<v Speaker 1>or at least a more advanced one. As for Google,

1:03:53.600 --> 1:03:56.160
<v Speaker 1>the company seems to maintain an optimistic outlook. If you

1:03:56.240 --> 1:03:59.120
<v Speaker 1>visit the Google Glass web page today, you'll be greeted

1:03:59.160 --> 1:04:02.520
<v Speaker 1>by a pretty simple shot, a photograph of a pair

1:04:02.560 --> 1:04:05.760
<v Speaker 1>of feet clad in Neon yellow sneakers, with the phrase

1:04:06.120 --> 1:04:10.040
<v Speaker 1>thanks for exploring with us. The journey doesn't end here,

1:04:11.560 --> 1:04:14.920
<v Speaker 1>but our journey does. It's time to wrap up this episode,

1:04:15.280 --> 1:04:18.280
<v Speaker 1>So if you guys have any suggestions, comments, or anything

1:04:18.320 --> 1:04:19.800
<v Speaker 1>like that, you should get in touch with me. You

1:04:19.800 --> 1:04:23.000
<v Speaker 1>can email me at tech Stuff at how stuff works

1:04:23.080 --> 1:04:25.480
<v Speaker 1>dot com, or you can drop me a line on

1:04:25.480 --> 1:04:27.600
<v Speaker 1>Facebook or Twitter. The handle for the show at both

1:04:27.600 --> 1:04:30.520
<v Speaker 1>of those is text Stuff H. S W. And remember,

1:04:30.560 --> 1:04:33.600
<v Speaker 1>you can watch me live on Wednesday and Friday afternoons

1:04:33.640 --> 1:04:37.080
<v Speaker 1>at twitch dot tv slash tech Stuff. Visit that link

1:04:37.120 --> 1:04:39.800
<v Speaker 1>to learn more about my live stream schedule. That's all

1:04:39.840 --> 1:04:43.120
<v Speaker 1>for now, and I'll talk to you again really soon.

1:04:48.080 --> 1:04:50.600
<v Speaker 1>For more on this and thousands of other topics, visit

1:04:50.680 --> 1:05:01.160
<v Speaker 1>how stuff works dot com