WEBVTT - TechStuff Classic: The Google Glass Story

0:00:04.440 --> 0:00:12.559
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.560 --> 0:00:15.960
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:16.000 --> 0:00:19.880
<v Speaker 1>I'm an executive producer at iHeart Podcasts and how the

0:00:19.960 --> 0:00:22.880
<v Speaker 1>tech are you. So it is Friday, It's time for

0:00:23.000 --> 0:00:26.880
<v Speaker 1>a classic episode. The episode you're about to hear, originally

0:00:26.920 --> 0:00:31.600
<v Speaker 1>published on May twelfth, twenty seventeen, is called the Google

0:00:31.880 --> 0:00:36.200
<v Speaker 1>Glass Story. Hope you enjoy. I'm going to talk about

0:00:36.240 --> 0:00:39.120
<v Speaker 1>a subject that I've touched on in past episodes. In fact,

0:00:39.120 --> 0:00:41.360
<v Speaker 1>we did a full episode about this subject. I'm talking

0:00:41.400 --> 0:00:45.080
<v Speaker 1>about Google Glass. And while we did do an older

0:00:45.120 --> 0:00:49.360
<v Speaker 1>episode about this, I felt like we could really use

0:00:49.800 --> 0:00:52.800
<v Speaker 1>a chance to revisit this and kind of talk about

0:00:52.880 --> 0:00:55.920
<v Speaker 1>in the more modern style of this show. You might

0:00:55.920 --> 0:00:58.760
<v Speaker 1>remember the old version of tech Stuff was more conversational,

0:00:58.760 --> 0:01:03.000
<v Speaker 1>and this one's less, so it's more narrative. Well, Google

0:01:03.000 --> 0:01:07.200
<v Speaker 1>Glass was a big augmented reality project or an AR project,

0:01:07.200 --> 0:01:10.240
<v Speaker 1>out of Google's R and D labs, the Google X Labs,

0:01:10.240 --> 0:01:13.280
<v Speaker 1>that's the super secret research and development branch of Google.

0:01:14.280 --> 0:01:16.839
<v Speaker 1>And it probably was a little bit ahead of its time.

0:01:16.920 --> 0:01:19.960
<v Speaker 1>In fact, it really was ahead of its time, and

0:01:20.040 --> 0:01:22.640
<v Speaker 1>it was purposefully ahead of its time. That was part

0:01:22.680 --> 0:01:26.039
<v Speaker 1>of the problem, but I'm getting ahead of myself. It

0:01:26.240 --> 0:01:29.640
<v Speaker 1>might have suffered from some poor design and implementation, or

0:01:29.640 --> 0:01:33.760
<v Speaker 1>at least some choices that perhaps puzzled people. I wouldn't

0:01:33.760 --> 0:01:35.760
<v Speaker 1>go so far as to call them poor myself. I

0:01:35.800 --> 0:01:39.080
<v Speaker 1>actually really liked Google Glass. Maybe it was just too

0:01:39.160 --> 0:01:43.640
<v Speaker 1>darned expensive. It's pretty costly, but whatever the reason, and

0:01:43.680 --> 0:01:47.480
<v Speaker 1>we'll explore all of them. It's no longer a consumer

0:01:47.560 --> 0:01:50.720
<v Speaker 1>product that you can buy from Google. So today we're

0:01:50.720 --> 0:01:53.520
<v Speaker 1>going to talk about Project Glass, how it got started,

0:01:53.560 --> 0:01:56.680
<v Speaker 1>the technology behind it, and the failed experiment to turn

0:01:56.720 --> 0:01:59.520
<v Speaker 1>it into a consumer product, and where is it now.

0:02:00.440 --> 0:02:03.160
<v Speaker 1>The reason I decided to cover this is because the

0:02:03.200 --> 0:02:06.600
<v Speaker 1>week I'm recording this episode, The Telegraph ran an article

0:02:06.640 --> 0:02:09.799
<v Speaker 1>about some of the biggest flops in technology, and some

0:02:09.840 --> 0:02:12.200
<v Speaker 1>of the usual suspects were in there, like the Nintendo

0:02:12.360 --> 0:02:16.960
<v Speaker 1>Virtual Boy was one of the major flops listed. There

0:02:16.960 --> 0:02:20.600
<v Speaker 1>are also some heartbreaking intrease in there. The Sega Dreamcast,

0:02:20.639 --> 0:02:24.320
<v Speaker 1>for example. I know that's another video game component there,

0:02:24.639 --> 0:02:28.160
<v Speaker 1>a console. In this case, it was legitimately a really

0:02:28.200 --> 0:02:30.720
<v Speaker 1>good video game console. It just didn't do very well

0:02:30.720 --> 0:02:33.680
<v Speaker 1>in the market. But I still have one and it

0:02:33.720 --> 0:02:37.760
<v Speaker 1>was really really good. Then there was Google Glass. That

0:02:37.840 --> 0:02:39.960
<v Speaker 1>was also one of the ones that the Telegraph listed

0:02:40.480 --> 0:02:44.280
<v Speaker 1>another heartbreaker. So what's the story behind it? Well, I

0:02:44.320 --> 0:02:49.160
<v Speaker 1>can't talk about Google Glass without first talking about augmented reality,

0:02:49.520 --> 0:02:52.520
<v Speaker 1>can I? You know me? You know I can't. I

0:02:52.560 --> 0:02:56.120
<v Speaker 1>am physically incapable of doing that. I'm sure many of

0:02:56.120 --> 0:02:59.200
<v Speaker 1>you are familiar with the concept of augmented reality or AR,

0:02:59.760 --> 0:03:01.400
<v Speaker 1>but just in case, I'm going to give you a

0:03:01.480 --> 0:03:06.200
<v Speaker 1>quick refresher. So Thomas Cottle gets the credit for coining

0:03:06.200 --> 0:03:09.799
<v Speaker 1>the phrase augmented reality in nineteen ninety. He was specifically

0:03:09.800 --> 0:03:12.240
<v Speaker 1>talking about a system that would allow you to see

0:03:12.280 --> 0:03:16.000
<v Speaker 1>where wires needed to be laid out in say, the

0:03:16.520 --> 0:03:19.880
<v Speaker 1>fuselage of an airplane. So if you've ever been able

0:03:19.880 --> 0:03:22.679
<v Speaker 1>to walk into an airplane where it's been stripped down

0:03:22.720 --> 0:03:25.720
<v Speaker 1>so you can see the guts of it. I was

0:03:25.800 --> 0:03:28.320
<v Speaker 1>recently at an airplane museum where I got to do this.

0:03:28.400 --> 0:03:31.480
<v Speaker 1>I walk through what had been a former seven forty

0:03:31.520 --> 0:03:35.720
<v Speaker 1>seven and now included a section where everything got stripped

0:03:35.720 --> 0:03:39.720
<v Speaker 1>away so you could see essentially the bones the skeleton

0:03:39.880 --> 0:03:42.480
<v Speaker 1>of the seven forty seven, and part of that included

0:03:42.520 --> 0:03:46.200
<v Speaker 1>conduits through which wires would run well. When you're building

0:03:46.200 --> 0:03:48.320
<v Speaker 1>one of these airplanes, you need to know where those

0:03:48.720 --> 0:03:51.720
<v Speaker 1>wire conduits have to be so that you can make

0:03:51.720 --> 0:03:55.320
<v Speaker 1>sure they fit into the overall design. Coddle worked on

0:03:55.440 --> 0:03:59.600
<v Speaker 1>systems that would give a digital overlay as engineers would

0:03:59.600 --> 0:04:02.880
<v Speaker 1>look at this airplane design so that they could lay

0:04:02.960 --> 0:04:05.200
<v Speaker 1>the cables the proper way, make sure that they were

0:04:05.240 --> 0:04:08.720
<v Speaker 1>aligned so that they weren't going to end up messing

0:04:08.840 --> 0:04:13.400
<v Speaker 1>up the design some other way. And really, augmented reality

0:04:13.480 --> 0:04:17.880
<v Speaker 1>is just the integration of digital information into the real

0:04:17.960 --> 0:04:20.200
<v Speaker 1>world around us. And you can do this in lots

0:04:20.240 --> 0:04:24.680
<v Speaker 1>of different ways, but typically we talk about augmented reality

0:04:24.680 --> 0:04:28.960
<v Speaker 1>in terms of overlaying some sort of visual digital information,

0:04:29.160 --> 0:04:32.400
<v Speaker 1>like a digital display through which you can see a

0:04:32.520 --> 0:04:35.120
<v Speaker 1>view of the real world, and thus you can have

0:04:35.200 --> 0:04:39.400
<v Speaker 1>some augmented information on top of that view of reality.

0:04:40.360 --> 0:04:42.359
<v Speaker 1>So a good example of this might be a fighter

0:04:42.360 --> 0:04:45.880
<v Speaker 1>pilot who has a helmet that includes a digital heads

0:04:45.920 --> 0:04:49.760
<v Speaker 1>up display or HUD on the visor of the helmet itself,

0:04:49.839 --> 0:04:54.400
<v Speaker 1>so you might be able to visualize things like Allied

0:04:54.600 --> 0:04:57.440
<v Speaker 1>aircraft and you'd be able to see it and it

0:04:57.440 --> 0:05:00.600
<v Speaker 1>would be identified within your visor, so that you get

0:05:00.640 --> 0:05:05.599
<v Speaker 1>information about that. That's a simple example, simple in the

0:05:05.640 --> 0:05:08.039
<v Speaker 1>sense that you can easily imagine it. It's actually quite

0:05:08.080 --> 0:05:11.720
<v Speaker 1>complicated when you build the technology. A few high end

0:05:11.760 --> 0:05:15.200
<v Speaker 1>cars have similar features that give digitally enhanced information that

0:05:15.400 --> 0:05:19.440
<v Speaker 1>is projected or otherwise displayed on the windshield itself, which

0:05:19.480 --> 0:05:22.799
<v Speaker 1>gives the driver the ability to see certain special views.

0:05:23.080 --> 0:05:25.280
<v Speaker 1>You might be able to see, like an infrared view

0:05:25.440 --> 0:05:28.560
<v Speaker 1>of what is outside the car, or a projection of

0:05:28.560 --> 0:05:31.159
<v Speaker 1>things like the outside temperature, that sort of stuff. But

0:05:31.200 --> 0:05:33.680
<v Speaker 1>it tends to be in those luxury cars. You don't

0:05:33.680 --> 0:05:37.520
<v Speaker 1>see it in a lot of the lower production cars,

0:05:38.200 --> 0:05:45.160
<v Speaker 1>even the nicer ones. It's pretty rare. You also have,

0:05:45.600 --> 0:05:50.760
<v Speaker 1>I'm guessing an augmented reality device on you. More likely

0:05:50.800 --> 0:05:53.479
<v Speaker 1>than not most of you, I'm sure have smartphones. So

0:05:53.560 --> 0:05:55.839
<v Speaker 1>if you have a smartphone, you have a device that

0:05:55.960 --> 0:05:59.480
<v Speaker 1>is probably capable of running augmented reality apps. There are

0:05:59.560 --> 0:06:02.560
<v Speaker 1>tons of different apps in the AR space for all

0:06:02.640 --> 0:06:06.640
<v Speaker 1>of the major smartphone platforms, iOS and Android being the

0:06:06.640 --> 0:06:08.640
<v Speaker 1>two big ones, but there are ones for other ones

0:06:08.640 --> 0:06:11.680
<v Speaker 1>as well, and typically the way these work is that

0:06:11.720 --> 0:06:16.240
<v Speaker 1>you hold your phone up, your phone's backfacing camera pulls

0:06:16.279 --> 0:06:19.160
<v Speaker 1>in a view of the world around you. So it's

0:06:19.160 --> 0:06:21.839
<v Speaker 1>like you're getting a live view. It's like your phone

0:06:21.920 --> 0:06:24.320
<v Speaker 1>is a monitor for you to look at a live

0:06:24.480 --> 0:06:27.000
<v Speaker 1>camera feed of the world around you. But then the

0:06:27.040 --> 0:06:30.120
<v Speaker 1>app allows other digital information to be overlaid on top

0:06:30.200 --> 0:06:32.360
<v Speaker 1>of that view. So it might be something as simple

0:06:32.440 --> 0:06:36.080
<v Speaker 1>as directions of where to go. Say you've programmed your

0:06:36.120 --> 0:06:38.880
<v Speaker 1>phone saying I want to get to this one particular

0:06:38.920 --> 0:06:42.400
<v Speaker 1>coffee shop and it's about six blocks away, and you

0:06:42.440 --> 0:06:44.760
<v Speaker 1>hold your phone up and it tells you, all right,

0:06:44.760 --> 0:06:46.960
<v Speaker 1>you need to go three blocks straight ahead. Then you're

0:06:46.960 --> 0:06:50.159
<v Speaker 1>going to take a rite. That's a pretty simple again

0:06:50.800 --> 0:06:55.400
<v Speaker 1>concept for augmented reality, but it could do other stuff too,

0:06:55.480 --> 0:06:56.839
<v Speaker 1>Like you might be able to hold it up to

0:06:56.920 --> 0:06:59.040
<v Speaker 1>a sign that's written in a language you can't read,

0:07:00.040 --> 0:07:01.680
<v Speaker 1>and it might be able to read it and translate

0:07:01.720 --> 0:07:04.320
<v Speaker 1>it for you. We're seeing a lot of translate apps

0:07:04.360 --> 0:07:08.760
<v Speaker 1>that incorporate this kind of augmented reality, and it's pretty awesome,

0:07:09.040 --> 0:07:12.240
<v Speaker 1>at least in my opinion, is pretty awesome. But there

0:07:12.280 --> 0:07:15.360
<v Speaker 1>are tons of different ways to implement augmented reality and

0:07:15.760 --> 0:07:20.760
<v Speaker 1>just as many different use cases for AR, and it

0:07:20.880 --> 0:07:26.000
<v Speaker 1>ranges from just entertainment to productivity to industrial use and

0:07:26.040 --> 0:07:31.600
<v Speaker 1>beyond medicine, lots of different potential uses for AR now.

0:07:31.640 --> 0:07:35.400
<v Speaker 1>Google Glass started as a head mounted computer device that

0:07:35.400 --> 0:07:38.880
<v Speaker 1>would incorporate augmented reality features into a display that you

0:07:38.960 --> 0:07:42.200
<v Speaker 1>could look through and still see the world beyond. And

0:07:42.280 --> 0:07:44.800
<v Speaker 1>while the project was first teased in a video in

0:07:44.800 --> 0:07:49.560
<v Speaker 1>twenty twelve, the origins for this project go back much

0:07:49.760 --> 0:07:53.840
<v Speaker 1>further than that. And first, before there was even a Google,

0:07:54.280 --> 0:07:57.960
<v Speaker 1>there was a guy named Thad Starner. I've actually had

0:07:57.960 --> 0:08:01.239
<v Speaker 1>the good fortune to meet mister Starner because he works

0:08:01.240 --> 0:08:04.560
<v Speaker 1>at Georgia Tech. He's a professor there, and I visited

0:08:04.600 --> 0:08:09.280
<v Speaker 1>Georgia Tech. I visited the wearable computing labs, and I've

0:08:09.360 --> 0:08:13.440
<v Speaker 1>chatted with him. He's an interesting dude, and Georgia Tech's

0:08:13.520 --> 0:08:15.920
<v Speaker 1>just down the street from how stuff works, so it's

0:08:15.920 --> 0:08:18.200
<v Speaker 1>not hard for us to get over there. Well. He

0:08:18.240 --> 0:08:21.040
<v Speaker 1>also served as a technical lead for Google Glass. In fact,

0:08:21.080 --> 0:08:24.520
<v Speaker 1>I believe he served as technical lead longer than anyone

0:08:24.600 --> 0:08:27.840
<v Speaker 1>else in that position for that particular project. And it

0:08:27.880 --> 0:08:31.160
<v Speaker 1>was Starner's work in wearable technology and augmented reality that

0:08:31.200 --> 0:08:36.280
<v Speaker 1>you could say got the ball rolling. So you remember

0:08:36.280 --> 0:08:39.080
<v Speaker 1>I mentioned a guy named Coddle got the credit for

0:08:39.200 --> 0:08:43.560
<v Speaker 1>coining the phrase augmented reality. Well, Starner says that he

0:08:44.120 --> 0:08:48.160
<v Speaker 1>really coined that phrase independently of Coddle. Also in nineteen

0:08:48.240 --> 0:08:51.560
<v Speaker 1>ninety through a fellowship proposal, he wrote, and he thinks

0:08:51.559 --> 0:08:55.280
<v Speaker 1>that that might be the first appearance of augmented reality.

0:08:55.480 --> 0:08:59.240
<v Speaker 1>He wanted to use the phrase artificial reality when he

0:08:59.320 --> 0:09:03.320
<v Speaker 1>was originally talking about this concept. However, someone else was

0:09:03.360 --> 0:09:07.320
<v Speaker 1>already using that term. That someone was Timothy Leary, and

0:09:07.320 --> 0:09:09.199
<v Speaker 1>if you don't know who Timothy Leary is, you should

0:09:09.240 --> 0:09:12.600
<v Speaker 1>look that up. Leary was specifically talking about the kind

0:09:12.640 --> 0:09:15.800
<v Speaker 1>of reality you experience when you have partaken in mind

0:09:15.880 --> 0:09:21.880
<v Speaker 1>altering substances. So it wasn't exactly the context that Starner

0:09:21.920 --> 0:09:25.280
<v Speaker 1>wanted to imply when he was talking about his technology,

0:09:25.880 --> 0:09:28.200
<v Speaker 1>so he didn't adopt artificial reality, and he went with

0:09:28.240 --> 0:09:33.720
<v Speaker 1>augmented reality instead. In nineteen ninety three, which was years

0:09:34.040 --> 0:09:39.199
<v Speaker 1>before Google ever even existed, Starner created a wearable display.

0:09:40.200 --> 0:09:43.359
<v Speaker 1>So it was a display that attached to his glasses,

0:09:43.480 --> 0:09:46.080
<v Speaker 1>and really he worked with other people to design this.

0:09:46.200 --> 0:09:49.439
<v Speaker 1>He didn't build it by himself with his own two hands,

0:09:49.960 --> 0:09:52.720
<v Speaker 1>but he worked with designers to create a computer system

0:09:52.800 --> 0:09:56.080
<v Speaker 1>that incorporated a display that could clip onto his glasses,

0:09:56.080 --> 0:09:58.560
<v Speaker 1>and it was pretty big and bulky, and it was

0:09:58.640 --> 0:10:02.800
<v Speaker 1>not transparent. It was like having a small computer monitor

0:10:03.240 --> 0:10:06.840
<v Speaker 1>mounted on your glasses. And he started to wear this

0:10:07.559 --> 0:10:11.960
<v Speaker 1>all the time wherever he went. It was kind of

0:10:11.960 --> 0:10:17.160
<v Speaker 1>an experiment in finding out how you might use wearable computers,

0:10:17.559 --> 0:10:21.280
<v Speaker 1>what elements are important, which ones are not important, how

0:10:21.280 --> 0:10:25.520
<v Speaker 1>do you incorporate it into your daily life. So he

0:10:25.520 --> 0:10:28.280
<v Speaker 1>would wear this all the time, and it very often

0:10:28.280 --> 0:10:31.240
<v Speaker 1>would prompt people to ask questions about this weird thing

0:10:31.400 --> 0:10:36.560
<v Speaker 1>that he had on hims on his face mainly. Eventually

0:10:37.120 --> 0:10:39.200
<v Speaker 1>there was a build of this that started going by

0:10:39.240 --> 0:10:42.760
<v Speaker 1>a name called the Lizzy. It was a wearable computer,

0:10:42.880 --> 0:10:46.680
<v Speaker 1>complete with input devices and with that head Melton display

0:10:46.880 --> 0:10:53.800
<v Speaker 1>that again was kind of unsightly originally anyway, This display

0:10:53.920 --> 0:10:56.640
<v Speaker 1>was able to show a resolution of seven hundred and

0:10:56.640 --> 0:10:59.840
<v Speaker 1>twenty by two hundred and eighty pixels, so tiny resolution

0:11:00.480 --> 0:11:03.080
<v Speaker 1>compared to what you would find today, the very low

0:11:03.160 --> 0:11:08.240
<v Speaker 1>resolution compared to today's screens. It was also monochromatic, so

0:11:08.720 --> 0:11:12.760
<v Speaker 1>only one color. And connected to that was a one

0:11:12.840 --> 0:11:17.000
<v Speaker 1>handed keyboard called a twiddler, which I wish were a joke,

0:11:17.640 --> 0:11:19.679
<v Speaker 1>but it is not. So it was a little one

0:11:19.679 --> 0:11:23.120
<v Speaker 1>handed twiddler keyboard. It kind of reminds me of the

0:11:23.440 --> 0:11:26.920
<v Speaker 1>keypads on old cell phones where if you wanted to

0:11:26.920 --> 0:11:29.320
<v Speaker 1>send a text message and you had to hit the

0:11:29.400 --> 0:11:32.760
<v Speaker 1>letter E, you had to press the def key twice

0:11:32.760 --> 0:11:34.960
<v Speaker 1>in a row in order for you to select E

0:11:35.040 --> 0:11:38.520
<v Speaker 1>before you moved on to your next letter. According to Starner,

0:11:38.559 --> 0:11:40.400
<v Speaker 1>he could hit type up to one hundred and thirty

0:11:40.400 --> 0:11:44.720
<v Speaker 1>words per minute using this one handed keyboard method, which

0:11:44.760 --> 0:11:48.679
<v Speaker 1>is crazy fast. It's crazy fast even if you're using

0:11:48.679 --> 0:11:51.679
<v Speaker 1>two hands on a regular keyboard. So I was really

0:11:51.760 --> 0:11:57.360
<v Speaker 1>impressed to hear about that very large and heavy batteries

0:11:57.400 --> 0:11:59.559
<v Speaker 1>would give the computer more than ten hours of juice

0:11:59.559 --> 0:12:02.840
<v Speaker 1>before you need to recharge. But I mean, these batteries

0:12:02.840 --> 0:12:09.720
<v Speaker 1>weighed several pounds at least, so they weren't little, unobtrusive

0:12:10.360 --> 0:12:14.240
<v Speaker 1>things attached to the computer. It was like wearing a

0:12:14.280 --> 0:12:19.640
<v Speaker 1>hefty backpack, so it wasn't exactly comfortable to wear all

0:12:19.679 --> 0:12:23.520
<v Speaker 1>the time. And the computer was really serving as a platform,

0:12:23.640 --> 0:12:26.720
<v Speaker 1>a development platform. It was the basis for programmers to

0:12:26.800 --> 0:12:31.360
<v Speaker 1>design wearable computing applications. So it's not like it magically

0:12:31.360 --> 0:12:34.240
<v Speaker 1>gave Starner some sort of crazy computing ability. It was

0:12:34.320 --> 0:12:37.000
<v Speaker 1>rather an early wearable device to help explore the applications

0:12:37.000 --> 0:12:42.880
<v Speaker 1>and implementations of wearables without having to worry about creating

0:12:42.880 --> 0:12:47.719
<v Speaker 1>a specific product. So this was really exploratory, and when

0:12:47.760 --> 0:12:49.920
<v Speaker 1>you think about it, it was meant to say, we

0:12:50.040 --> 0:12:53.679
<v Speaker 1>think there's something here, but we don't exactly know what

0:12:53.720 --> 0:12:55.800
<v Speaker 1>it is yet. We don't know what the final form

0:12:55.840 --> 0:12:57.880
<v Speaker 1>is going to be, So I don't have an idea

0:12:58.000 --> 0:13:00.840
<v Speaker 1>for something that's going to be in a package on

0:13:00.880 --> 0:13:04.080
<v Speaker 1>a store shelf that other people can go out and buy. Rather,

0:13:04.200 --> 0:13:09.600
<v Speaker 1>I think computing has the capability of transforming our daily

0:13:09.640 --> 0:13:13.000
<v Speaker 1>lives in yet another way. Now keep in mind, this

0:13:13.040 --> 0:13:17.360
<v Speaker 1>isn't the early nineteen nineties. This is before smartphones, so

0:13:17.480 --> 0:13:20.360
<v Speaker 1>smartphones would go on to show us that, yes, indeed,

0:13:20.720 --> 0:13:23.320
<v Speaker 1>having a computer device that you can carry around with

0:13:23.360 --> 0:13:28.240
<v Speaker 1>you changes things. There's no question of that. The Internet

0:13:28.280 --> 0:13:31.360
<v Speaker 1>itself is a reflection of how much that has changed.

0:13:31.679 --> 0:13:36.360
<v Speaker 1>Internet advertising has changed dramatically because of mobile devices and

0:13:36.440 --> 0:13:40.080
<v Speaker 1>the popularity of them. So wearable computers definitely had the

0:13:40.080 --> 0:13:43.680
<v Speaker 1>potential to make an enormous impact, but we had to

0:13:43.679 --> 0:13:48.240
<v Speaker 1>figure out what sort of implementation made sense and what

0:13:48.320 --> 0:13:51.080
<v Speaker 1>kind of applications would you use it? For because just

0:13:51.080 --> 0:13:54.480
<v Speaker 1>to have something, just to have it that doesn't remain

0:13:54.520 --> 0:13:57.000
<v Speaker 1>compelling for very long. That would be part of the

0:13:57.040 --> 0:14:02.240
<v Speaker 1>problem of Google Glass later spoiler alone. Now. One of

0:14:02.280 --> 0:14:07.679
<v Speaker 1>those applications that Starner created early on was a program

0:14:07.760 --> 0:14:11.120
<v Speaker 1>that would keep track of everything he said, whether or

0:14:11.120 --> 0:14:13.120
<v Speaker 1>not it was straight voice to text. I am not

0:14:13.320 --> 0:14:16.720
<v Speaker 1>entirely certain. I'm sure by some point it really was.

0:14:17.640 --> 0:14:19.480
<v Speaker 1>But he would also be able to type things in

0:14:19.600 --> 0:14:23.800
<v Speaker 1>using the twiddler, which I remind you it's not a joke.

0:14:25.640 --> 0:14:27.960
<v Speaker 1>So it was kind of like a perpetual notes system.

0:14:28.040 --> 0:14:30.000
<v Speaker 1>He could keep track of things he was thinking about

0:14:30.000 --> 0:14:32.560
<v Speaker 1>and talking about, and then he could run a search

0:14:32.880 --> 0:14:35.760
<v Speaker 1>back against that see if he could find anything interesting

0:14:35.880 --> 0:14:38.560
<v Speaker 1>later on, and he said that about ninety five percent

0:14:38.600 --> 0:14:41.200
<v Speaker 1>of the time what he got back was garbage, wasn't

0:14:41.240 --> 0:14:44.800
<v Speaker 1>particularly interesting, insightful, or helpful. But about five percent of

0:14:44.800 --> 0:14:48.680
<v Speaker 1>the time it was totally the opposite. It was something

0:14:48.760 --> 0:14:52.880
<v Speaker 1>really worth knowing and remembering. So he thought of it

0:14:52.920 --> 0:14:57.200
<v Speaker 1>as something like a memory booster. It wasn't replacing his memory,

0:14:57.240 --> 0:15:02.000
<v Speaker 1>but augmenting it. Now, according to popular accounts, Starner attended

0:15:02.040 --> 0:15:05.720
<v Speaker 1>a conference in the late nineties and he met two

0:15:05.760 --> 0:15:09.080
<v Speaker 1>postgraduate students from Stanford, so this would be about nineteen

0:15:09.160 --> 0:15:13.800
<v Speaker 1>ninety eight. Those two postgraduate students were named Saragaie Brenn

0:15:13.840 --> 0:15:16.920
<v Speaker 1>and Larry Page, and if you're familiar with those two,

0:15:16.960 --> 0:15:20.000
<v Speaker 1>you know those are the co founders or Google. In fact,

0:15:20.040 --> 0:15:22.880
<v Speaker 1>they would found the company Google just a few short

0:15:22.920 --> 0:15:27.160
<v Speaker 1>months after this conference. Now, Brin and Page thought that

0:15:27.200 --> 0:15:31.520
<v Speaker 1>Starner's wearable computers were fascinating, and he gave them a

0:15:31.520 --> 0:15:34.960
<v Speaker 1>full demonstration of what the computer was capable of doing. However,

0:15:35.160 --> 0:15:38.000
<v Speaker 1>at the time, they were already focusing on a way

0:15:38.080 --> 0:15:42.600
<v Speaker 1>to improve search engines on the web, so they couldn't

0:15:42.640 --> 0:15:46.040
<v Speaker 1>really dedicate any attention to wearable computers. They were too

0:15:46.080 --> 0:15:50.960
<v Speaker 1>busy perfecting their search engine approach. And this was important

0:15:50.960 --> 0:15:54.480
<v Speaker 1>because back in the day before things like Google, the

0:15:54.520 --> 0:15:57.280
<v Speaker 1>algorithm that got so sophisticated that it was able to

0:15:57.360 --> 0:15:59.560
<v Speaker 1>ignore a lot of the tricks people were using to

0:15:59.560 --> 0:16:03.480
<v Speaker 1>try and direct traffic to their sites. Web search engines

0:16:03.520 --> 0:16:06.840
<v Speaker 1>were just okay. Most of them were looking for instances

0:16:07.080 --> 0:16:10.640
<v Speaker 1>of keywords appearing on a page, which meant that people

0:16:10.640 --> 0:16:14.400
<v Speaker 1>would try and fool search engines by inserting as many

0:16:14.440 --> 0:16:17.520
<v Speaker 1>different key search terms as possible at the bottom of

0:16:17.520 --> 0:16:19.800
<v Speaker 1>a page, even if the page had nothing to do

0:16:20.360 --> 0:16:24.040
<v Speaker 1>with that particular concept. And why would they do this

0:16:24.560 --> 0:16:27.920
<v Speaker 1>Because web advertising is based off of how many views

0:16:27.960 --> 0:16:31.240
<v Speaker 1>you get on a page. Page views are king at

0:16:31.360 --> 0:16:33.640
<v Speaker 1>least most web advertising is not all of it, but

0:16:33.720 --> 0:16:36.520
<v Speaker 1>a lot of it is. So if you were able

0:16:36.560 --> 0:16:38.720
<v Speaker 1>to direct a lot of traffic to your web page,

0:16:38.960 --> 0:16:41.760
<v Speaker 1>that was another page view, it didn't matter if what

0:16:41.840 --> 0:16:44.240
<v Speaker 1>that people founded that by the time they got there,

0:16:44.320 --> 0:16:45.960
<v Speaker 1>if it wasn't what they were looking for, and if

0:16:45.960 --> 0:16:48.640
<v Speaker 1>they bounced, you got the page view. You don't care

0:16:48.680 --> 0:16:52.560
<v Speaker 1>where they go afterward. Well, Google one of its big

0:16:52.640 --> 0:16:54.880
<v Speaker 1>missions was to create a better search engine that would

0:16:54.920 --> 0:17:00.520
<v Speaker 1>ignore all of the gamification of SEO and to try

0:17:00.560 --> 0:17:04.000
<v Speaker 1>and look for the links that are the best representation

0:17:04.119 --> 0:17:06.880
<v Speaker 1>of whatever it is you're searching for. So that's what

0:17:06.920 --> 0:17:11.800
<v Speaker 1>their real focus was on. However, this meeting between Starner

0:17:12.040 --> 0:17:17.000
<v Speaker 1>and Brennan Page may have been the first seed for

0:17:17.119 --> 0:17:20.200
<v Speaker 1>Google Glass, and it happened in nineteen ninety eight, before

0:17:20.320 --> 0:17:24.600
<v Speaker 1>Google was an official company. Now flash forward a decade,

0:17:24.640 --> 0:17:27.840
<v Speaker 1>it's two thousand and eight. Google by this time is

0:17:27.880 --> 0:17:32.840
<v Speaker 1>a huge company, incredibly successful, and it had just launched

0:17:32.840 --> 0:17:40.080
<v Speaker 1>its own smartphone operating system called Android. Starner immediately thought

0:17:40.080 --> 0:17:44.040
<v Speaker 1>that Android had promise as more than just an operating

0:17:44.080 --> 0:17:46.960
<v Speaker 1>system for a smartphone. It could be ported over to

0:17:47.080 --> 0:17:50.480
<v Speaker 1>all sorts of different devices and used for lots of

0:17:50.520 --> 0:17:54.960
<v Speaker 1>different stuff, particularly things that were small and nimble, stuff

0:17:54.960 --> 0:18:00.280
<v Speaker 1>that wasn't like your traditional laptop or desktop computer that

0:18:00.320 --> 0:18:04.119
<v Speaker 1>includes wearables. So he tried to get in touch with

0:18:04.240 --> 0:18:08.119
<v Speaker 1>Brennan Page. However, the phone number he had from ten

0:18:08.240 --> 0:18:13.160
<v Speaker 1>years previous was no longer going to either of them.

0:18:13.280 --> 0:18:16.840
<v Speaker 1>Big surprise, right, and he kind of let lie for

0:18:16.880 --> 0:18:19.240
<v Speaker 1>another couple of years. In twenty ten, he would write

0:18:19.240 --> 0:18:24.760
<v Speaker 1>an email to Saragai Brenn and he said, you should

0:18:24.760 --> 0:18:26.919
<v Speaker 1>probably come out to my lab at Georgia Tech and

0:18:26.960 --> 0:18:28.960
<v Speaker 1>take a look at the wearables and see where we've

0:18:29.000 --> 0:18:30.760
<v Speaker 1>gone in the last ten years. I think he'd be

0:18:30.840 --> 0:18:33.840
<v Speaker 1>really interested. And Brennan said, you know, we're thinking about wearables.

0:18:33.880 --> 0:18:37.280
<v Speaker 1>We think it's about time. And rather than us go there,

0:18:37.280 --> 0:18:39.400
<v Speaker 1>how about we fly you and your team out here

0:18:39.440 --> 0:18:41.600
<v Speaker 1>so you can give us a full day of demonstrations.

0:18:42.280 --> 0:18:44.679
<v Speaker 1>And Starner said yes, and next thing he knew, he

0:18:44.760 --> 0:18:48.760
<v Speaker 1>became a technical lead for Project glass Over at Google's

0:18:49.000 --> 0:18:55.000
<v Speaker 1>X division. By Shortly thereafter, after Starner joined the team,

0:18:55.480 --> 0:18:58.240
<v Speaker 1>Starner Brennan Page were able to bring over another leader

0:18:58.280 --> 0:19:00.720
<v Speaker 1>in wearable tech, someone that Starner had worked with in

0:19:00.760 --> 0:19:04.600
<v Speaker 1>the past, Greg Priest Dorman, who had pioneered work with

0:19:04.640 --> 0:19:07.399
<v Speaker 1>biofeedback systems in the seventies and into the eighties and

0:19:07.440 --> 0:19:12.199
<v Speaker 1>then moved into wearable computing. He's another huge name in wearables,

0:19:12.680 --> 0:19:17.959
<v Speaker 1>so he also joined the Google Glass development team. On

0:19:18.000 --> 0:19:21.879
<v Speaker 1>August eighteenth, twenty eleven, four Google employees filed a patent

0:19:21.920 --> 0:19:25.600
<v Speaker 1>for what was called a wearable device with input and

0:19:25.760 --> 0:19:29.919
<v Speaker 1>output structures. It's the title of a patent, and like

0:19:29.960 --> 0:19:33.359
<v Speaker 1>most patent titles, it's a little dry and it seems

0:19:33.400 --> 0:19:37.399
<v Speaker 1>pretty nondescript. The illustrations accompanying the patent include one that

0:19:37.520 --> 0:19:41.080
<v Speaker 1>closely resembles what the final form of Google Glass turned

0:19:41.080 --> 0:19:44.000
<v Speaker 1>out to be. Some of the other illustrations looked more

0:19:44.080 --> 0:19:46.520
<v Speaker 1>like a more or less normal pair of glasses. Some

0:19:46.560 --> 0:19:49.719
<v Speaker 1>of them looked a little strange or odd. The patent

0:19:49.760 --> 0:19:53.280
<v Speaker 1>described the general components for the invention, which you know

0:19:54.359 --> 0:19:56.840
<v Speaker 1>patents are supposed to do. In order for you to

0:19:56.880 --> 0:19:58.960
<v Speaker 1>get a patent on something, you have to actually explain

0:19:59.040 --> 0:20:01.880
<v Speaker 1>how the thing works the parts that are that it's

0:20:01.920 --> 0:20:05.800
<v Speaker 1>made out of. Otherwise you can't You're not supposed to

0:20:05.800 --> 0:20:09.800
<v Speaker 1>get a patent on it. So what did this cover? Well,

0:20:09.960 --> 0:20:12.800
<v Speaker 1>I suppose I can quote directly from the patent itself

0:20:13.640 --> 0:20:17.320
<v Speaker 1>under the claims section. The first and most important of

0:20:17.359 --> 0:20:24.760
<v Speaker 1>the claims reads thus late an electronic device comprising a

0:20:24.800 --> 0:20:27.399
<v Speaker 1>frame configured to be worn on the head of a user.

0:20:27.720 --> 0:20:30.720
<v Speaker 1>The frame including a bridge configured to be supported on

0:20:30.800 --> 0:20:34.280
<v Speaker 1>the nose of the user, a brow portion coupled to

0:20:34.560 --> 0:20:38.120
<v Speaker 1>and extending away from the bridge to a first end

0:20:38.200 --> 0:20:42.600
<v Speaker 1>remote therefrom and configured to be positioned over a first

0:20:42.640 --> 0:20:45.520
<v Speaker 1>side of a brow of the user, and a first

0:20:45.640 --> 0:20:48.720
<v Speaker 1>arm having a first end coupled to the first end

0:20:48.800 --> 0:20:51.920
<v Speaker 1>of the brow portion and extending to a free end,

0:20:52.200 --> 0:20:54.959
<v Speaker 1>the first arm being configured to be positioned over a

0:20:55.000 --> 0:20:58.480
<v Speaker 1>first temple of the user, with the free end disposed

0:20:58.520 --> 0:21:02.280
<v Speaker 1>near a first ear of the user, wherein the bridge

0:21:02.320 --> 0:21:05.920
<v Speaker 1>is adjustable for selective positioning of the brow portion relative

0:21:05.960 --> 0:21:09.680
<v Speaker 1>to an eye of the user. A generally transparent display

0:21:10.119 --> 0:21:12.800
<v Speaker 1>means for a fixing the display to the frame such

0:21:12.840 --> 0:21:15.480
<v Speaker 1>that the display is movable with respect to the frame

0:21:15.680 --> 0:21:19.240
<v Speaker 1>through rotation about a first axis that extends parallel to

0:21:19.280 --> 0:21:22.800
<v Speaker 1>the first brow portion, and an input device a fixed

0:21:22.840 --> 0:21:25.800
<v Speaker 1>to the frame and configured for receiving from the user.

0:21:25.840 --> 0:21:29.679
<v Speaker 1>And input associated with a function wherein information related to

0:21:29.680 --> 0:21:34.840
<v Speaker 1>the function is presentable on the display. What the what? Well,

0:21:35.359 --> 0:21:39.160
<v Speaker 1>I'm going to explain what that means, but first let's

0:21:39.160 --> 0:21:49.800
<v Speaker 1>take a quick break to thank our sponsor. All right,

0:21:49.840 --> 0:21:54.239
<v Speaker 1>So what did that patent speak actually mean? Because it

0:21:54.280 --> 0:21:58.840
<v Speaker 1>got so weird and dry, and that's typical for patents,

0:21:58.920 --> 0:22:02.600
<v Speaker 1>by the way. That's it's a very formulaic approach because

0:22:04.760 --> 0:22:08.480
<v Speaker 1>patent system is a bureaucracy and you have to conform

0:22:08.680 --> 0:22:11.760
<v Speaker 1>to the methodology of the bureaucracy in order to get

0:22:12.240 --> 0:22:17.080
<v Speaker 1>your idea through Otherwise, if it doesn't conform, you're not

0:22:17.320 --> 0:22:21.080
<v Speaker 1>likely to get a patent award. So what it actually

0:22:21.080 --> 0:22:23.359
<v Speaker 1>means is the invention would fit on your face like

0:22:23.400 --> 0:22:27.200
<v Speaker 1>a pair of glasses that one arm or stem if

0:22:27.200 --> 0:22:31.480
<v Speaker 1>you prefer, of these glasses would curve around the brow

0:22:31.800 --> 0:22:35.120
<v Speaker 1>above one eye to rest against the side of your head,

0:22:35.240 --> 0:22:38.760
<v Speaker 1>so over one eye, and in early Google glass it

0:22:38.800 --> 0:22:42.640
<v Speaker 1>was always the right eye. There'd be a little protrusion.

0:22:43.520 --> 0:22:46.160
<v Speaker 1>That's where at the end of that protrusion. That's where

0:22:46.160 --> 0:22:50.680
<v Speaker 1>the screen would be, the clear transparent screen. I guess

0:22:50.680 --> 0:22:52.439
<v Speaker 1>I can say clear and transparent like I can say

0:22:52.480 --> 0:22:57.520
<v Speaker 1>ATM machine. Then the other part of it would wrap

0:22:57.560 --> 0:23:01.480
<v Speaker 1>around back behind your ear, with a part of it

0:23:01.600 --> 0:23:04.919
<v Speaker 1>resting just behind your ear. More on that than just

0:23:04.960 --> 0:23:07.960
<v Speaker 1>a second, but that would be the main part of

0:23:08.040 --> 0:23:11.080
<v Speaker 1>Google Glass. The other section would just be a dumb

0:23:11.160 --> 0:23:15.399
<v Speaker 1>frame that exists really just to provide stability. So you

0:23:15.400 --> 0:23:17.000
<v Speaker 1>would have a part that would rest on the bridge

0:23:17.040 --> 0:23:21.800
<v Speaker 1>of your nose that would help support the stem I

0:23:21.840 --> 0:23:25.720
<v Speaker 1>was talking about. And on the other side your second ear,

0:23:25.760 --> 0:23:29.680
<v Speaker 1>because you remember the patent said first ear and first etc.

0:23:30.040 --> 0:23:33.119
<v Speaker 1>Et cetera. First brow. The other one would be the

0:23:33.160 --> 0:23:35.760
<v Speaker 1>second one. This is not important to the invention because

0:23:35.880 --> 0:23:40.359
<v Speaker 1>nothing of any technical import is going on on that side.

0:23:40.400 --> 0:23:43.679
<v Speaker 1>It's literally just a frame to hold the rest of

0:23:43.680 --> 0:23:46.959
<v Speaker 1>the technology in place. So over your right ear you

0:23:47.040 --> 0:23:49.880
<v Speaker 1>have the stem of the Google Glass, and in that

0:23:49.920 --> 0:23:53.480
<v Speaker 1>section you've got a control area. You've got your battery,

0:23:53.520 --> 0:23:56.879
<v Speaker 1>you've got your speaker, you've got your projector for the screen,

0:23:57.040 --> 0:24:00.639
<v Speaker 1>you've got inside, you've got the processor, you've got the

0:24:00.800 --> 0:24:04.360
<v Speaker 1>receiver for Bluetooth et cetera. On the other side, over

0:24:04.400 --> 0:24:07.679
<v Speaker 1>your left ear, it's just a regular little stem that

0:24:07.840 --> 0:24:09.760
<v Speaker 1>fits over your ear, kind of like a regular pair

0:24:09.760 --> 0:24:14.639
<v Speaker 1>of glasses. There's nothing, no technical elements inside that side

0:24:14.640 --> 0:24:22.840
<v Speaker 1>of it. It's just dumb plastic. So the part that's

0:24:22.880 --> 0:24:26.360
<v Speaker 1>right behind your ear, that's where the speaker was, that's

0:24:26.400 --> 0:24:28.800
<v Speaker 1>where the audio would come from. Obviously, if you're watching

0:24:28.840 --> 0:24:31.479
<v Speaker 1>a video or you're taking a call, you would need

0:24:31.480 --> 0:24:35.280
<v Speaker 1>to be able to hear things through the glasses. It's

0:24:35.320 --> 0:24:39.000
<v Speaker 1>cool because this particular speaker wasn't just playing audio blasting

0:24:39.000 --> 0:24:41.560
<v Speaker 1>it out into the real world. It was using bone

0:24:41.600 --> 0:24:46.800
<v Speaker 1>conduction to transmit audio so that you could hear it. Now,

0:24:46.800 --> 0:24:48.800
<v Speaker 1>if you stood close to someone who was wearing google

0:24:48.840 --> 0:24:51.040
<v Speaker 1>glass and they were playing audio, you would hear stuff.

0:24:51.080 --> 0:24:54.040
<v Speaker 1>Because when you get down to it, sound is vibration.

0:24:55.080 --> 0:24:58.640
<v Speaker 1>The sound that you are hearing right now is transmitted

0:24:58.800 --> 0:25:03.040
<v Speaker 1>through molecules vibrating at the frequency that I'm talking at,

0:25:03.080 --> 0:25:08.399
<v Speaker 1>and the amplification as well. The amplitude, So when you

0:25:08.440 --> 0:25:10.480
<v Speaker 1>get down to the fact that sound is just vibration,

0:25:10.880 --> 0:25:14.320
<v Speaker 1>bone conduction makes sense. It is what it sounds like.

0:25:14.560 --> 0:25:19.600
<v Speaker 1>Sound is transmitting through bone. Your bone conducts sound bones,

0:25:19.800 --> 0:25:22.000
<v Speaker 1>I should say, although in this particular case we're talking

0:25:22.040 --> 0:25:26.320
<v Speaker 1>about the skull, otherwise known in medical circles as the headbone,

0:25:27.480 --> 0:25:31.120
<v Speaker 1>So the headbone would transmit the sound from the speaker.

0:25:31.600 --> 0:25:34.480
<v Speaker 1>So what's happening is that? Well, I guess it helps

0:25:34.480 --> 0:25:37.400
<v Speaker 1>if we talk about just the regular sense of hearing first, right,

0:25:38.119 --> 0:25:42.480
<v Speaker 1>These vibrating air molecules enter your ear canal. They cause

0:25:42.520 --> 0:25:46.000
<v Speaker 1>your ear drum or your tympanic membrane if you prefer

0:25:46.520 --> 0:25:51.080
<v Speaker 1>to vibrate. Now, that vibration gets transmitted to a tiny

0:25:51.359 --> 0:25:54.560
<v Speaker 1>set of bones in your inner ear, which acts as

0:25:54.600 --> 0:25:58.800
<v Speaker 1>kind of like an amplifier, and they ultimately terminate on

0:25:58.920 --> 0:26:02.560
<v Speaker 1>an organ called the cochlea, which is sort of in

0:26:02.600 --> 0:26:05.560
<v Speaker 1>a spiral shell shape. It's got some fluid in it,

0:26:05.600 --> 0:26:08.840
<v Speaker 1>and it's got some finger like nerve endings in it

0:26:09.200 --> 0:26:13.080
<v Speaker 1>that are in this fluid. And when the coclia is vibrated,

0:26:13.160 --> 0:26:16.800
<v Speaker 1>then this fluid moves around and that stimulates the nerve

0:26:16.880 --> 0:26:19.679
<v Speaker 1>endings inside of it, which then sends signals to the

0:26:19.680 --> 0:26:23.639
<v Speaker 1>brain which then interpret that to be sound. It's pretty

0:26:23.680 --> 0:26:26.399
<v Speaker 1>cool when you really develop thought about it. Well, the

0:26:26.400 --> 0:26:28.680
<v Speaker 1>neat thing about bone conduction is you can bypass the

0:26:29.040 --> 0:26:33.240
<v Speaker 1>ear drum entirely. You can send vibrations through bone, which

0:26:33.320 --> 0:26:37.560
<v Speaker 1>then will reach the inner ear on their own bypassing

0:26:37.640 --> 0:26:40.719
<v Speaker 1>that pathway that all other sound tends to take and

0:26:41.720 --> 0:26:46.199
<v Speaker 1>vibrating the cochlea directly. So there are a lot of

0:26:46.240 --> 0:26:51.200
<v Speaker 1>sports earbuds or headbands or whatever that have these kind

0:26:51.200 --> 0:26:53.960
<v Speaker 1>of bone conduction speakers. Some people call them bone phones.

0:26:55.359 --> 0:26:59.919
<v Speaker 1>I do not, but some people do. And the Google

0:27:00.119 --> 0:27:03.600
<v Speaker 1>Lass had one of these types of speakers to again

0:27:03.720 --> 0:27:07.480
<v Speaker 1>transmit sound without it blasting out into the general world.

0:27:08.480 --> 0:27:10.879
<v Speaker 1>Pretty interesting stuff. And this meant that you could watch

0:27:10.920 --> 0:27:13.359
<v Speaker 1>things like videos, or listen to a voicemail or make

0:27:13.400 --> 0:27:17.640
<v Speaker 1>a call using Google Glass, and you could hear through

0:27:17.680 --> 0:27:19.520
<v Speaker 1>Google Glass. You didn't have to hold a phone up

0:27:19.560 --> 0:27:25.439
<v Speaker 1>to your other ear. Now, the invention also incorporated a

0:27:25.480 --> 0:27:28.400
<v Speaker 1>screen that was transparent, so, in other words, you had

0:27:28.440 --> 0:27:31.439
<v Speaker 1>to be able to see through the screen and be

0:27:31.520 --> 0:27:35.040
<v Speaker 1>able to view the outside world through it. It couldn't

0:27:35.040 --> 0:27:38.120
<v Speaker 1>have an opaque backing, so you couldn't silver the back

0:27:38.119 --> 0:27:41.639
<v Speaker 1>of the screen, which presents some challenges. So how do

0:27:41.680 --> 0:27:45.400
<v Speaker 1>you project images so that you can see a display

0:27:45.640 --> 0:27:49.080
<v Speaker 1>and read the digital information? Because again that's what augmented

0:27:49.119 --> 0:27:52.080
<v Speaker 1>reality is all about, right, it's overlaying that digital information

0:27:52.280 --> 0:27:54.760
<v Speaker 1>on top of a view of the actual world around you.

0:27:55.240 --> 0:27:56.879
<v Speaker 1>So if you can see through the screen, how do

0:27:56.960 --> 0:28:02.600
<v Speaker 1>you display images on that said screen? Well, Claim nine

0:28:03.520 --> 0:28:06.160
<v Speaker 1>on that same patent gives some information on that matter.

0:28:06.240 --> 0:28:10.080
<v Speaker 1>It says the electronic device of Claim one wherein the

0:28:10.160 --> 0:28:14.240
<v Speaker 1>generally transparent display is a prism of a transparent material

0:28:14.320 --> 0:28:17.600
<v Speaker 1>configured to make an image projected into a side of

0:28:17.640 --> 0:28:20.720
<v Speaker 1>the prism visible at a surface of the prism that

0:28:20.840 --> 0:28:23.520
<v Speaker 1>is at a non zero angle to the side of

0:28:23.560 --> 0:28:28.840
<v Speaker 1>the prism. Now what that means is that on casual glance,

0:28:29.440 --> 0:28:34.359
<v Speaker 1>the prism looks like an elongated cube of clear plastic,

0:28:35.160 --> 0:28:37.640
<v Speaker 1>and it looks like that's all it is. But if

0:28:37.640 --> 0:28:39.959
<v Speaker 1>you were to take a look at it from the top,

0:28:40.640 --> 0:28:42.960
<v Speaker 1>like the top of a pair of Google glass, and

0:28:42.960 --> 0:28:45.280
<v Speaker 1>you were looking down, you would see that there's a

0:28:45.560 --> 0:28:52.760
<v Speaker 1>fine line bisecting from one corner of this prism down

0:28:52.920 --> 0:28:57.800
<v Speaker 1>into about the middle of the prism, a this weird

0:28:57.840 --> 0:29:02.840
<v Speaker 1>little diagonal. This is an angle layer inside the prism,

0:29:03.000 --> 0:29:05.160
<v Speaker 1>and the way it works is it allows light to

0:29:05.200 --> 0:29:08.720
<v Speaker 1>pass through straight from ahead of you. So if you're

0:29:08.720 --> 0:29:11.040
<v Speaker 1>wearing the pair of Google Glass and you're looking at something,

0:29:11.320 --> 0:29:14.360
<v Speaker 1>light can pass straight through the prism, no problem. But

0:29:14.440 --> 0:29:16.880
<v Speaker 1>if light were to come from a right angle to

0:29:16.960 --> 0:29:20.960
<v Speaker 1>the right, as in a place where a little projector

0:29:21.200 --> 0:29:25.600
<v Speaker 1>in the Google Glass could project out images, it would

0:29:25.640 --> 0:29:29.760
<v Speaker 1>then redirect that light ninety degrees so that it goes

0:29:29.800 --> 0:29:32.920
<v Speaker 1>into your eyes. In other words, you can still see

0:29:32.920 --> 0:29:35.400
<v Speaker 1>the world in front of you because that light can

0:29:35.440 --> 0:29:39.360
<v Speaker 1>pass through unimpeded. Light coming from the right side, which

0:29:39.400 --> 0:29:44.680
<v Speaker 1>is where the little digital projector is, that gets reflected

0:29:44.760 --> 0:29:46.600
<v Speaker 1>into your eyes, so then you can see the digital

0:29:46.600 --> 0:29:50.520
<v Speaker 1>information overlaid on top of the world around you. So

0:29:50.640 --> 0:29:53.320
<v Speaker 1>think of its kind of like a mirror, but the

0:29:53.320 --> 0:29:56.840
<v Speaker 1>mirror only works if light is coming at it from

0:29:56.920 --> 0:30:00.240
<v Speaker 1>a very specific angle. It's, you know, in a way,

0:30:00.320 --> 0:30:02.520
<v Speaker 1>like one of those two way mirrors where you can

0:30:02.560 --> 0:30:04.560
<v Speaker 1>see through one way but not in the other. It's

0:30:04.640 --> 0:30:07.680
<v Speaker 1>kind of similar to that. So I thought that was

0:30:07.720 --> 0:30:12.840
<v Speaker 1>super neat. It was actually the most fascinating part of

0:30:12.880 --> 0:30:15.600
<v Speaker 1>Google Glass when I was first learning about it way

0:30:15.600 --> 0:30:19.040
<v Speaker 1>back in twenty twelve, when I was trying to learn

0:30:19.120 --> 0:30:21.240
<v Speaker 1>how it worked so I could write an article about it,

0:30:21.280 --> 0:30:24.400
<v Speaker 1>and in fact I did write at least a version

0:30:24.400 --> 0:30:26.560
<v Speaker 1>of how Google Glass works. I haven't looked on the

0:30:26.600 --> 0:30:29.200
<v Speaker 1>website to see if that's still my version, because we

0:30:29.280 --> 0:30:33.240
<v Speaker 1>update these articles on occasion and sometimes that changes the

0:30:33.360 --> 0:30:36.720
<v Speaker 1>authorship as well. But yeah, way back in the day,

0:30:36.720 --> 0:30:38.920
<v Speaker 1>I wrote an article about how Google Glass works, and

0:30:39.040 --> 0:30:40.840
<v Speaker 1>part of it was just learning about this prism and

0:30:40.880 --> 0:30:49.680
<v Speaker 1>I thought it was fascinating. In addition, the design of

0:30:49.720 --> 0:30:52.640
<v Speaker 1>this prism meant that it was slightly above your normal

0:30:52.680 --> 0:30:54.959
<v Speaker 1>line of sight. So this is that part of the

0:30:55.040 --> 0:30:58.320
<v Speaker 1>patent that talked about it being offset from your eye.

0:30:59.040 --> 0:31:03.560
<v Speaker 1>It's it's mounted a bit above where your natural line

0:31:03.600 --> 0:31:05.880
<v Speaker 1>of sight would be, so you would always have it

0:31:05.960 --> 0:31:08.320
<v Speaker 1>in your field of view, but it wouldn't necessarily be

0:31:08.360 --> 0:31:11.280
<v Speaker 1>in focus unless you were to glance upward so that

0:31:11.320 --> 0:31:14.520
<v Speaker 1>your right eye would be looking at the prism directly.

0:31:15.800 --> 0:31:20.320
<v Speaker 1>This was a specific design implemented by Google in order

0:31:20.360 --> 0:31:23.920
<v Speaker 1>to avoid things like people getting distracted by digital images

0:31:23.960 --> 0:31:26.200
<v Speaker 1>when they should be paying to the world around them,

0:31:26.600 --> 0:31:30.240
<v Speaker 1>and to make Google Glass something that you reference rather

0:31:30.280 --> 0:31:33.400
<v Speaker 1>than something that replaces your view of the world around you.

0:31:34.200 --> 0:31:36.200
<v Speaker 1>Very important if you're doing something like I don't know,

0:31:36.600 --> 0:31:40.920
<v Speaker 1>walking or driving or riding a bicycle, anything where you're

0:31:40.960 --> 0:31:43.400
<v Speaker 1>moving through a space. You want to be able to

0:31:43.440 --> 0:31:47.080
<v Speaker 1>make sure that you're not having your attention divided so

0:31:47.120 --> 0:31:49.960
<v Speaker 1>that you end up doing something stupid, like walking into

0:31:49.960 --> 0:31:54.960
<v Speaker 1>an open manhole or into a telephone pole. I have

0:31:55.080 --> 0:31:58.160
<v Speaker 1>done that before, for Realsi's but that was because I

0:31:58.200 --> 0:32:00.480
<v Speaker 1>was looking at a phone. I've been that guy. I

0:32:00.520 --> 0:32:03.200
<v Speaker 1>don't look at my phone when I'm crossing streets, but

0:32:03.280 --> 0:32:05.719
<v Speaker 1>I look at it when I'm walking down sidewalks, and

0:32:05.840 --> 0:32:08.120
<v Speaker 1>I have paid that price on multiple occasions. You think

0:32:08.120 --> 0:32:10.200
<v Speaker 1>I've learned by now, and I guess I have. I've

0:32:10.280 --> 0:32:16.480
<v Speaker 1>learned how to replicate that experience almost perfectly. The patent

0:32:16.520 --> 0:32:19.959
<v Speaker 1>also included an important component in Google Glasses control system,

0:32:20.000 --> 0:32:24.360
<v Speaker 1>which was a capacitive touch bar along that one stem,

0:32:24.600 --> 0:32:28.000
<v Speaker 1>the active stem of Google Glass. And I've talked about

0:32:28.080 --> 0:32:31.200
<v Speaker 1>capacitive touch before, but let's quickly go over that so

0:32:31.240 --> 0:32:34.040
<v Speaker 1>that we understand what I'm talking about. So with a

0:32:34.080 --> 0:32:38.160
<v Speaker 1>capacitive touch surface, you have the makings of a circuit, right.

0:32:38.600 --> 0:32:40.680
<v Speaker 1>All that remains is you have to have something to

0:32:40.760 --> 0:32:43.480
<v Speaker 1>close the circuit. You have to have something conductive make

0:32:43.680 --> 0:32:47.800
<v Speaker 1>contact with a capacitive surface so that a complete circuit

0:32:47.840 --> 0:32:51.120
<v Speaker 1>can form and when a complete circuit does form, there's

0:32:51.160 --> 0:32:54.920
<v Speaker 1>a voltage drop at the location of the touch. So

0:32:54.960 --> 0:32:56.880
<v Speaker 1>if I have a giant touch screen in front of me,

0:32:56.920 --> 0:32:59.960
<v Speaker 1>and it's a capacitive touch screen, and I reach down

0:33:00.240 --> 0:33:03.360
<v Speaker 1>with one finger and make contact with that screen, I

0:33:03.440 --> 0:33:06.000
<v Speaker 1>complete a circuit, and there's a voltage drop at the

0:33:06.000 --> 0:33:09.240
<v Speaker 1>point where I touched it. Software on the device is

0:33:09.280 --> 0:33:13.360
<v Speaker 1>able to interpret that as being an actual command of

0:33:13.360 --> 0:33:16.880
<v Speaker 1>some sort, and it might be selecting a program. It

0:33:16.960 --> 0:33:19.840
<v Speaker 1>might mean turning volume up or down. It might mean

0:33:20.160 --> 0:33:23.520
<v Speaker 1>swiping right because that dude you're looking at on tender

0:33:23.640 --> 0:33:25.880
<v Speaker 1>is pretty hot and you kind of want to know

0:33:26.080 --> 0:33:29.600
<v Speaker 1>what's his deal man, so you want to swipe right

0:33:29.640 --> 0:33:34.520
<v Speaker 1>on that. Lots of different applications. There are also resistive

0:33:34.600 --> 0:33:37.719
<v Speaker 1>touch screens that work on a slightly different principle. Those

0:33:37.760 --> 0:33:40.160
<v Speaker 1>are the ones that you have to actually use pressure

0:33:40.600 --> 0:33:44.520
<v Speaker 1>when you're making contact because it's not enough to touch it.

0:33:44.560 --> 0:33:47.920
<v Speaker 1>You actually have to press so that you're slightly deforming

0:33:47.960 --> 0:33:51.640
<v Speaker 1>the layers in order to create a circuit within the

0:33:51.720 --> 0:33:57.760
<v Speaker 1>display itself. But that's a totally different type of touch screen. Now,

0:33:57.760 --> 0:34:00.479
<v Speaker 1>in the case of Google Glass, the capacity panel is

0:34:00.800 --> 0:34:03.720
<v Speaker 1>a means to cycle through the various features that are

0:34:03.760 --> 0:34:07.440
<v Speaker 1>on the glasses. It's also a way to execute other

0:34:07.520 --> 0:34:10.879
<v Speaker 1>basic commands, so Google would go a step further than this.

0:34:11.520 --> 0:34:14.480
<v Speaker 1>You wouldn't have just touch commands. That was just one

0:34:14.520 --> 0:34:17.960
<v Speaker 1>way you could interact with Google Glass. They also incorporated

0:34:17.960 --> 0:34:21.560
<v Speaker 1>some motion controls and voice commands. So, for example, if

0:34:21.600 --> 0:34:23.399
<v Speaker 1>you wanted to turn your screen on and you wanted

0:34:23.440 --> 0:34:26.400
<v Speaker 1>to wake up Google Glass from its power saving mode,

0:34:26.640 --> 0:34:30.319
<v Speaker 1>you could choose an option where by tilting your head

0:34:30.400 --> 0:34:35.400
<v Speaker 1>backward at a fairly good rate, it would wake up Google.

0:34:35.440 --> 0:34:39.360
<v Speaker 1>It's kind of like saying sup to someone. We'll be

0:34:39.440 --> 0:34:41.600
<v Speaker 1>back with more about the Google Glass story in just

0:34:41.680 --> 0:34:53.359
<v Speaker 1>a moment. If you want to take a photo, you

0:34:53.400 --> 0:34:56.560
<v Speaker 1>could start with the phrase okay Google, which probably sounds

0:34:56.560 --> 0:34:59.080
<v Speaker 1>familiar to you if you have an Android device or

0:34:59.120 --> 0:35:02.359
<v Speaker 1>a Google Home and if I just activated it, I

0:35:02.400 --> 0:35:07.280
<v Speaker 1>am sorry. You could then follow up with take a picture,

0:35:07.760 --> 0:35:09.800
<v Speaker 1>so you could give a voice command to your Google

0:35:09.800 --> 0:35:12.360
<v Speaker 1>Glass to take photos. I can speak from experience that

0:35:12.400 --> 0:35:15.200
<v Speaker 1>people thought that this was the coolest thing ever when

0:35:15.280 --> 0:35:17.480
<v Speaker 1>Google Glass was brand new and only a few pairs

0:35:17.480 --> 0:35:21.720
<v Speaker 1>were out in the wild. In September of twenty twelve,

0:35:21.800 --> 0:35:24.399
<v Speaker 1>after I had a pair of Google Glass, and yes

0:35:24.520 --> 0:35:27.240
<v Speaker 1>I did have a pair of them. Technically, the company

0:35:27.320 --> 0:35:29.920
<v Speaker 1>purchased them. I was just the representative who got to

0:35:29.920 --> 0:35:32.759
<v Speaker 1>be the one to use them. When I had them,

0:35:33.880 --> 0:35:36.040
<v Speaker 1>I took them to dragon Con, which is a big

0:35:36.080 --> 0:35:39.200
<v Speaker 1>science fiction and fantasy convention here in Atlanta, and I

0:35:39.200 --> 0:35:41.840
<v Speaker 1>would ask people, may I take your picture? Because there

0:35:41.840 --> 0:35:43.319
<v Speaker 1>are a lot of people in costume, a lot of

0:35:43.400 --> 0:35:46.399
<v Speaker 1>great cosplay at dragon Con, and most of the time

0:35:46.400 --> 0:35:48.799
<v Speaker 1>people say yes absolutely. That's why I got dressed up.

0:35:49.040 --> 0:35:52.240
<v Speaker 1>And then I would say okay, Google, take a picture,

0:35:52.840 --> 0:35:55.920
<v Speaker 1>and they would look at me confused because they had

0:35:55.920 --> 0:35:58.360
<v Speaker 1>never seen Google Glass do that before. And then the

0:35:58.400 --> 0:36:01.520
<v Speaker 1>little light would flash on the Google Glass because that

0:36:01.520 --> 0:36:04.440
<v Speaker 1>would indicate that a photo had been taken. Google wanted

0:36:04.480 --> 0:36:07.359
<v Speaker 1>to have a physical indicator to let people know when

0:36:07.400 --> 0:36:10.800
<v Speaker 1>a camera was active. And then immediately they would freak

0:36:10.880 --> 0:36:13.680
<v Speaker 1>out about the fact that I was wearing the future

0:36:13.719 --> 0:36:17.120
<v Speaker 1>on my faith, and I would invariably have to take

0:36:17.120 --> 0:36:19.600
<v Speaker 1>another photo because the first one would mostly be if

0:36:19.640 --> 0:36:22.480
<v Speaker 1>you've ever seen a dog, look confused. That's what almost

0:36:22.520 --> 0:36:25.080
<v Speaker 1>all of the first photos look like from that Dragon Con.

0:36:25.120 --> 0:36:28.080
<v Speaker 1>Because I was talking to a pair of glasses and

0:36:28.120 --> 0:36:30.040
<v Speaker 1>they thought I was talking to them and they were wondering,

0:36:30.320 --> 0:36:33.520
<v Speaker 1>why am I saying this. These days, everyone would totally

0:36:33.560 --> 0:36:36.200
<v Speaker 1>understand what was going on. At the time, it was

0:36:36.200 --> 0:36:40.000
<v Speaker 1>pretty new. Now, to avoid making the headset too heavy

0:36:40.080 --> 0:36:43.319
<v Speaker 1>or too hot, the designers decided that Google Glass would

0:36:43.360 --> 0:36:46.400
<v Speaker 1>have to be a peripheral piece of technology, so in

0:36:46.440 --> 0:36:49.840
<v Speaker 1>other words, they didn't want it to be loaded down

0:36:49.960 --> 0:36:56.440
<v Speaker 1>with processors and with various connectivity chips like cellular connectivity,

0:36:56.480 --> 0:36:59.719
<v Speaker 1>Wi Fi, all of that kind of stuff. So you

0:36:59.760 --> 0:37:03.080
<v Speaker 1>would co pair it to another device, like a smartphone,

0:37:03.120 --> 0:37:07.000
<v Speaker 1>for example, and the smartphone would act as your link

0:37:07.320 --> 0:37:12.200
<v Speaker 1>between the glasses and the outside world. For the most part.

0:37:12.360 --> 0:37:15.239
<v Speaker 1>You could also do Wi Fi, I think, but obviously

0:37:15.400 --> 0:37:18.040
<v Speaker 1>WiFi is not pervasive, so if you're anywhere where there's

0:37:18.040 --> 0:37:20.560
<v Speaker 1>not Wi Fi, you would need to have almost like

0:37:20.600 --> 0:37:23.280
<v Speaker 1>a modem, and your smartphone would act as your modem

0:37:23.440 --> 0:37:26.680
<v Speaker 1>with a Bluetooth connection allowing for the communication between your

0:37:26.719 --> 0:37:30.680
<v Speaker 1>glasses and the phone. Now, that simplified the components that

0:37:30.719 --> 0:37:32.800
<v Speaker 1>needed to go into the glasses themselves, and that allowed

0:37:32.840 --> 0:37:36.000
<v Speaker 1>the designers to make it a little bit lighter and

0:37:36.120 --> 0:37:38.680
<v Speaker 1>not worry about so much heat generation. It also meant

0:37:38.680 --> 0:37:41.440
<v Speaker 1>that there was less of a drain on the battery,

0:37:41.600 --> 0:37:45.400
<v Speaker 1>which was perhaps the biggest challenge for the team was

0:37:45.440 --> 0:37:48.920
<v Speaker 1>designing a battery that would be light enough and yet

0:37:48.960 --> 0:37:51.600
<v Speaker 1>powerful enough to do what they wanted it to do.

0:37:52.200 --> 0:37:56.160
<v Speaker 1>They needed it to not make the glasses uncomfortable to

0:37:56.200 --> 0:37:59.000
<v Speaker 1>wear or really unwearable for any length of time, but

0:37:59.040 --> 0:38:01.040
<v Speaker 1>they also wanted to make sure they had enough juice

0:38:01.040 --> 0:38:02.480
<v Speaker 1>to get a decent amount of use out of it

0:38:02.520 --> 0:38:06.920
<v Speaker 1>before you had to recharge it. They also got around

0:38:06.960 --> 0:38:10.320
<v Speaker 1>this by having Google Glass go into sleep mode pretty quickly,

0:38:10.840 --> 0:38:13.719
<v Speaker 1>so that anytime you were not actively using it, it

0:38:13.719 --> 0:38:17.439
<v Speaker 1>could conserve power, and that way you could get maybe

0:38:17.480 --> 0:38:20.960
<v Speaker 1>another hour out of it. It drained pretty fast back

0:38:21.000 --> 0:38:26.200
<v Speaker 1>when I got one. Earlier wearable computers would require those

0:38:26.200 --> 0:38:28.839
<v Speaker 1>massive batteries I talked about before, ones that weighed four

0:38:28.920 --> 0:38:31.439
<v Speaker 1>or five pounds. Now, you don't want something like that

0:38:31.760 --> 0:38:37.520
<v Speaker 1>on your glasses. It would just be excruciating. So this

0:38:37.800 --> 0:38:40.520
<v Speaker 1>was a huge challenge. It remains a huge challenge in

0:38:40.600 --> 0:38:43.760
<v Speaker 1>wearables to this day is figuring out the balance between

0:38:44.560 --> 0:38:47.640
<v Speaker 1>the features you want to include and how much can

0:38:47.680 --> 0:38:50.239
<v Speaker 1>a battery provide before you're going to have to start

0:38:50.280 --> 0:38:54.200
<v Speaker 1>recharging it. Every few minutes. While the paperwork was being

0:38:54.280 --> 0:38:56.799
<v Speaker 1>drawn up with the patents, Starner and others were in

0:38:56.840 --> 0:39:01.240
<v Speaker 1>Google's labs building this actual hardware and testing it constantly.

0:39:01.760 --> 0:39:04.680
<v Speaker 1>Whenever they were in the lab, they were wearing these devices.

0:39:04.920 --> 0:39:07.120
<v Speaker 1>Whenever they were doing their regular jobs, they were wearing

0:39:07.120 --> 0:39:09.000
<v Speaker 1>these They were testing them, they were trying them out,

0:39:09.040 --> 0:39:11.640
<v Speaker 1>they were adding new features, taking old ones out when

0:39:11.680 --> 0:39:15.000
<v Speaker 1>they didn't work, building apps just for their own use,

0:39:15.400 --> 0:39:18.239
<v Speaker 1>to kind of really test the limits of what this

0:39:18.320 --> 0:39:20.680
<v Speaker 1>technology could do. And then at the end of the

0:39:20.800 --> 0:39:23.480
<v Speaker 1>day they would put them up and go home because

0:39:23.880 --> 0:39:27.160
<v Speaker 1>they weren't ready for the world to see Google Glass yet.

0:39:27.200 --> 0:39:30.560
<v Speaker 1>They didn't want to go out and start using it

0:39:30.719 --> 0:39:33.279
<v Speaker 1>outside where people might wonder what the heck is going on,

0:39:33.360 --> 0:39:35.359
<v Speaker 1>and then next thing you know, everyone's talking about it.

0:39:37.320 --> 0:39:40.600
<v Speaker 1>So in twenty eleven, Google employees submitted the patent for

0:39:40.840 --> 0:39:45.080
<v Speaker 1>the headmounted display. The Patent Office would eventually grant that

0:39:45.120 --> 0:39:49.560
<v Speaker 1>patent on February twenty first, twenty thirteen, which actually is

0:39:49.600 --> 0:39:52.799
<v Speaker 1>not that long at all. That's pretty fast in many

0:39:52.840 --> 0:39:56.560
<v Speaker 1>cases for between a patent application and when it's actually granted.

0:39:57.480 --> 0:40:00.239
<v Speaker 1>A couple of years is nothing. But then go we'll

0:40:00.280 --> 0:40:02.239
<v Speaker 1>let the cat out of the bag. In between those

0:40:02.239 --> 0:40:08.160
<v Speaker 1>two dates, in April twenty twelve, Google released a concept video,

0:40:08.800 --> 0:40:10.960
<v Speaker 1>and this was a video that was shown from a

0:40:11.000 --> 0:40:13.880
<v Speaker 1>first person view, so you were in the shoes of

0:40:13.920 --> 0:40:18.240
<v Speaker 1>a guy wearing some sort of device that had something

0:40:18.239 --> 0:40:20.879
<v Speaker 1>to do with Google. And the reason why I'm vague

0:40:20.960 --> 0:40:22.920
<v Speaker 1>is because the video was pretty vague. It was just

0:40:23.000 --> 0:40:25.319
<v Speaker 1>giving you an idea of what this experience might one

0:40:25.400 --> 0:40:28.280
<v Speaker 1>day be like. Clearly, it was a head mounted display

0:40:28.280 --> 0:40:31.880
<v Speaker 1>of some sort with a heads up display element to it,

0:40:32.440 --> 0:40:35.319
<v Speaker 1>and it allowed this guy to send messages, to make

0:40:35.360 --> 0:40:38.799
<v Speaker 1>phone calls, to take images, to share live video with

0:40:38.880 --> 0:40:42.080
<v Speaker 1>someone else. So, in other words, the camera on this

0:40:42.239 --> 0:40:46.160
<v Speaker 1>device could feed video directly to somebody somewhere else in

0:40:46.200 --> 0:40:52.719
<v Speaker 1>the world, and you could even alert the person of

0:40:52.760 --> 0:40:54.640
<v Speaker 1>what was going on in the world around them. So

0:40:54.880 --> 0:40:57.640
<v Speaker 1>at one point, he's on his way to an appointment

0:40:57.960 --> 0:40:59.920
<v Speaker 1>and he wants to take the subway, and as he

0:41:00.040 --> 0:41:02.600
<v Speaker 1>gets close to the subway, a little alert points up

0:41:02.880 --> 0:41:05.600
<v Speaker 1>and it says there are delays at the subway station,

0:41:05.640 --> 0:41:08.200
<v Speaker 1>and he's like, aw shucks, and so he decides to

0:41:08.239 --> 0:41:12.560
<v Speaker 1>walk instead. So some of this stuff would get worked

0:41:12.600 --> 0:41:15.759
<v Speaker 1>into Google Glass. Some of it wouldn't be directly worked

0:41:15.800 --> 0:41:20.200
<v Speaker 1>into Google Glass, but they could fudge it through other means.

0:41:20.520 --> 0:41:22.560
<v Speaker 1>But it was an interesting video and it got a

0:41:22.560 --> 0:41:26.960
<v Speaker 1>lot of people talking. It generated a lot of buzz. Now,

0:41:27.800 --> 0:41:31.359
<v Speaker 1>you might think, like with the subway example, was that

0:41:32.080 --> 0:41:37.480
<v Speaker 1>a case of machine vision understanding that the subway the

0:41:37.520 --> 0:41:40.759
<v Speaker 1>guy is walking to is a particular one in a

0:41:40.760 --> 0:41:43.960
<v Speaker 1>particular system, and that that one is one that's being

0:41:43.960 --> 0:41:48.200
<v Speaker 1>affected by delays. That was not worked into Google Glass

0:41:48.480 --> 0:41:51.520
<v Speaker 1>because the camera cannot be perpetually on. If it were,

0:41:51.680 --> 0:41:56.040
<v Speaker 1>the battery would drain very very quickly. Instead, what you

0:41:56.080 --> 0:42:01.759
<v Speaker 1>could do is you could incorporate GPS from a smartphone

0:42:02.520 --> 0:42:06.080
<v Speaker 1>as well as a person's calendar if they've added an

0:42:06.080 --> 0:42:10.200
<v Speaker 1>appointment to their calendar, and if the phone makes a

0:42:10.280 --> 0:42:12.759
<v Speaker 1>quote unquote guess that you are on your way to

0:42:12.880 --> 0:42:15.920
<v Speaker 1>set appointment, and it notices you're getting closer to a

0:42:15.960 --> 0:42:19.040
<v Speaker 1>subway station because of your GPS coordinates, it could then

0:42:19.080 --> 0:42:22.120
<v Speaker 1>send you an alert saying, oh, we've got this message

0:42:22.120 --> 0:42:25.480
<v Speaker 1>saying that that particular subway station is experiencing delays. Now,

0:42:25.480 --> 0:42:29.399
<v Speaker 1>from your perspective, it's almost like Google Glass looked at

0:42:29.400 --> 0:42:33.719
<v Speaker 1>the subway and then said, hey, buddy, let's walk. You're

0:42:33.800 --> 0:42:35.319
<v Speaker 1>never going to get there if you try and get

0:42:35.320 --> 0:42:38.520
<v Speaker 1>on the train. But in reality, it could be stuff

0:42:38.560 --> 0:42:40.680
<v Speaker 1>that's happening on the background. The nice thing is it

0:42:40.680 --> 0:42:44.839
<v Speaker 1>doesn't really matter how it happens. What matters is the experience.

0:42:45.360 --> 0:42:48.839
<v Speaker 1>Does the experience make sense? Is it compelling? Because if

0:42:48.840 --> 0:42:51.160
<v Speaker 1>it is, it doesn't matter if it was because of

0:42:51.440 --> 0:42:54.320
<v Speaker 1>machine vision or if it was because of a combination

0:42:54.719 --> 0:43:00.800
<v Speaker 1>of GPS and calendar apps and other information. The result

0:43:00.840 --> 0:43:03.560
<v Speaker 1>is the same either way. Other than the fact that

0:43:04.160 --> 0:43:06.920
<v Speaker 1>in the way I just described, it's not draining your

0:43:06.920 --> 0:43:09.400
<v Speaker 1>Google Glass battery super fast by having the camera on

0:43:09.520 --> 0:43:13.520
<v Speaker 1>all the time. The video got a lot of attention.

0:43:13.680 --> 0:43:16.200
<v Speaker 1>People were excited about it. People wanted to know more,

0:43:16.800 --> 0:43:20.120
<v Speaker 1>but Google did not show off Google Glass at that

0:43:20.200 --> 0:43:24.080
<v Speaker 1>particular moment. They did show it off not too long

0:43:24.239 --> 0:43:27.640
<v Speaker 1>after that, and they did admit they were working on

0:43:27.680 --> 0:43:31.200
<v Speaker 1>an augmented reality project and they wanted to get feedback

0:43:31.280 --> 0:43:33.880
<v Speaker 1>from people about how they would use it and what

0:43:34.000 --> 0:43:39.000
<v Speaker 1>they thought about this concept. A couple of months later,

0:43:39.960 --> 0:43:42.880
<v Speaker 1>they held the Google Io Developer Conference. I've been to

0:43:42.920 --> 0:43:47.160
<v Speaker 1>one of these. They're very very nerdy. It is interesting.

0:43:48.040 --> 0:43:51.880
<v Speaker 1>It gets incredibly technical very fast, because it's meant for

0:43:51.960 --> 0:43:56.919
<v Speaker 1>people who are developing apps for Google platforms. The event

0:43:57.000 --> 0:44:00.720
<v Speaker 1>took place in San Francisco's Moscone Center, and high above

0:44:00.800 --> 0:44:04.480
<v Speaker 1>the center was a blimp with several skydivers in wingsuits

0:44:04.480 --> 0:44:07.319
<v Speaker 1>and parachutes, and each person in that group was wearing

0:44:07.320 --> 0:44:09.400
<v Speaker 1>a pair of Google Glass. And in the middle of

0:44:09.400 --> 0:44:12.239
<v Speaker 1>a totally different presentation, Sarah gay Brenn runs up on

0:44:12.280 --> 0:44:14.520
<v Speaker 1>stage and he says, I'm sorry to interrupt, but we've

0:44:14.560 --> 0:44:17.640
<v Speaker 1>got a time sensitive event going on right now, and

0:44:17.680 --> 0:44:21.440
<v Speaker 1>he switches to video showing the blimp above the Moscone Center.

0:44:21.800 --> 0:44:24.320
<v Speaker 1>Then they switch to a camera inside the blimp itself

0:44:24.360 --> 0:44:26.279
<v Speaker 1>and you see the team there, and you see that

0:44:26.320 --> 0:44:28.480
<v Speaker 1>each member of the team is wearing a pair of

0:44:28.560 --> 0:44:33.680
<v Speaker 1>Google Glass. They start a Google hangout using their Google Glass,

0:44:33.960 --> 0:44:35.840
<v Speaker 1>and then you can see the screens from each of

0:44:35.880 --> 0:44:39.280
<v Speaker 1>their perspectives. So now you're getting a first person view

0:44:39.680 --> 0:44:42.880
<v Speaker 1>of these people who are inside the blimp. And eventually,

0:44:42.920 --> 0:44:45.239
<v Speaker 1>once the blimp is in the right location, they make

0:44:45.280 --> 0:44:48.480
<v Speaker 1>a jump. They jump out of the blimp, they fall,

0:44:48.719 --> 0:44:52.200
<v Speaker 1>they launch their shoots, they land on the roof of

0:44:52.239 --> 0:44:56.200
<v Speaker 1>the Moscone Center. They hand over a package to a

0:44:56.280 --> 0:44:59.879
<v Speaker 1>person riding a mountain bike and he's also got Google

0:45:00.120 --> 0:45:03.040
<v Speaker 1>glass on. He rides over to the edge of the building,

0:45:03.120 --> 0:45:07.000
<v Speaker 1>switches over into repelling gear, repels down the side, gets

0:45:07.040 --> 0:45:10.359
<v Speaker 1>inside the Moscone Center, gets on a different mountain bike,

0:45:10.920 --> 0:45:15.360
<v Speaker 1>rides over into the conference room, down the aisle, straight

0:45:15.400 --> 0:45:19.000
<v Speaker 1>over to the stage, and brings Sergei brin a package

0:45:19.040 --> 0:45:22.720
<v Speaker 1>that has inside of it a fresh pair of Google glass.

0:45:24.640 --> 0:45:28.600
<v Speaker 1>It was a heck of a demo. I watched it live,

0:45:28.960 --> 0:45:32.440
<v Speaker 1>not in the Moscone Center. I was watching it remotely.

0:45:32.480 --> 0:45:34.759
<v Speaker 1>I was not at that particular Io event, and my

0:45:34.880 --> 0:45:38.400
<v Speaker 1>jaw was on the floor to see this display of

0:45:38.440 --> 0:45:43.320
<v Speaker 1>wearable technology in such a cool application. You know, this

0:45:43.800 --> 0:45:47.000
<v Speaker 1>Google hangout that's showing me what it's like to skydive

0:45:47.040 --> 0:45:51.040
<v Speaker 1>from a first person perspective. And then this journey from

0:45:51.200 --> 0:45:54.279
<v Speaker 1>the sea, the roof of the building down into the

0:45:54.320 --> 0:46:01.200
<v Speaker 1>center itself. It was an effective demonstration. Now, in August

0:46:01.200 --> 0:46:03.640
<v Speaker 1>twenty twelve, Google would receive a pattern. Now this was

0:46:03.680 --> 0:46:06.240
<v Speaker 1>not the same one for the head mounted display pattern

0:46:06.440 --> 0:46:09.400
<v Speaker 1>that one wouldn't be granted until twenty thirteen, but this

0:46:09.520 --> 0:46:11.680
<v Speaker 1>was a patent for a process and the title of

0:46:11.719 --> 0:46:15.560
<v Speaker 1>the pattern was unlocking a screen using eye tracking information.

0:46:16.719 --> 0:46:20.040
<v Speaker 1>So this would require having some sort of camera facing

0:46:20.120 --> 0:46:24.480
<v Speaker 1>back toward a person's eye, and it would look at

0:46:24.640 --> 0:46:28.200
<v Speaker 1>motions of the eye and interpret that as various commands,

0:46:28.320 --> 0:46:31.759
<v Speaker 1>including unlocking a device. So you may have had a

0:46:31.760 --> 0:46:34.400
<v Speaker 1>smartphone at some point that allowed you to create a

0:46:34.520 --> 0:46:38.600
<v Speaker 1>pattern by tracing something on a screen. An old Android

0:46:38.600 --> 0:46:42.040
<v Speaker 1>one I used to use had a grid of dots,

0:46:42.560 --> 0:46:45.920
<v Speaker 1>and you would connect dots in a particular pattern, set

0:46:45.960 --> 0:46:49.160
<v Speaker 1>that as your pattern of choice, and every time you

0:46:49.160 --> 0:46:51.160
<v Speaker 1>wanted to unlock the phone from that point forward, you

0:46:51.160 --> 0:46:53.480
<v Speaker 1>had to retrace that pattern. Well, you could do the

0:46:53.560 --> 0:46:58.359
<v Speaker 1>same thing with eye tracking if you had a virtual

0:46:58.520 --> 0:47:03.640
<v Speaker 1>display of dots and you stared at one dot until

0:47:03.680 --> 0:47:06.279
<v Speaker 1>the camera had picked up and acknowledged yes, you're looking

0:47:06.360 --> 0:47:08.359
<v Speaker 1>at the correct one, and then you just move your

0:47:08.360 --> 0:47:10.399
<v Speaker 1>eye from dot to dot, and this is like moving

0:47:10.440 --> 0:47:12.880
<v Speaker 1>your finger from dot to dot, and you could unlock

0:47:12.880 --> 0:47:16.640
<v Speaker 1>a screen in that way. That's just one particular approach

0:47:16.680 --> 0:47:19.160
<v Speaker 1>that you could use to unlock a screen using eye tracking.

0:47:20.520 --> 0:47:24.840
<v Speaker 1>This particular type of feature would not be included with

0:47:24.880 --> 0:47:26.839
<v Speaker 1>Google Glass, but it shows the kind of stuff they

0:47:26.840 --> 0:47:29.640
<v Speaker 1>were thinking about while they were putting all this together.

0:47:30.200 --> 0:47:32.560
<v Speaker 1>Yet Another pattern revealed what Google hoped to do with

0:47:32.600 --> 0:47:36.680
<v Speaker 1>Project Glass, and it used gestures. So these would be

0:47:36.719 --> 0:47:39.600
<v Speaker 1>hand gestures, actual hand gestures you would make in front

0:47:39.640 --> 0:47:43.719
<v Speaker 1>of your face lack a crazy person in order to

0:47:43.800 --> 0:47:46.560
<v Speaker 1>send commands to your Google Glass. So let's say you

0:47:46.640 --> 0:47:50.839
<v Speaker 1>see something on the street and you like it. It

0:47:51.160 --> 0:47:54.840
<v Speaker 1>could happen. Maybe you see a poster for a band

0:47:55.040 --> 0:47:57.080
<v Speaker 1>that you like and it's they're coming up with a

0:47:58.239 --> 0:48:02.400
<v Speaker 1>show nearby. Make a little heart shape with your hand. Awe,

0:48:03.360 --> 0:48:08.120
<v Speaker 1>so cute, you Millennials, And then this would end up

0:48:08.160 --> 0:48:11.560
<v Speaker 1>being picked up by the camera and interpreted as liking

0:48:11.840 --> 0:48:14.239
<v Speaker 1>the thing you are looking at. Maybe it posts to

0:48:14.280 --> 0:48:17.439
<v Speaker 1>a social media page saying, Jonathan likes the fact that

0:48:17.719 --> 0:48:19.840
<v Speaker 1>they might be giants is going to be in Atlanta

0:48:19.960 --> 0:48:23.520
<v Speaker 1>the Variety Playhouse playing a show, And yes, I would

0:48:23.560 --> 0:48:25.799
<v Speaker 1>like that. I love they might be giants and the

0:48:25.880 --> 0:48:29.680
<v Speaker 1>Variety Playhouse is a delightful venue. I don't know that

0:48:29.719 --> 0:48:31.160
<v Speaker 1>I would go so far as to make the little

0:48:31.200 --> 0:48:34.480
<v Speaker 1>heart shape of my hands, though I do have my limits.

0:48:35.600 --> 0:48:38.760
<v Speaker 1>But this shows another way of how Google was thinking

0:48:38.800 --> 0:48:43.160
<v Speaker 1>about interactions with its technology and ways that you could

0:48:43.200 --> 0:48:46.640
<v Speaker 1>control it beyond just using a capacitive touchscreen or even

0:48:46.719 --> 0:48:50.680
<v Speaker 1>voice commands. That also would not find its way into

0:48:50.719 --> 0:48:53.080
<v Speaker 1>Google Glass, but it might find its way into some

0:48:53.120 --> 0:48:57.040
<v Speaker 1>future Google product. Now, next we'll explore a bit with

0:48:57.120 --> 0:49:01.360
<v Speaker 1>Google Glass, and we will pay handsomely for it. But

0:49:01.640 --> 0:49:04.600
<v Speaker 1>before I jump into that, let's take another quick break

0:49:04.880 --> 0:49:17.719
<v Speaker 1>to thank our sponsor. In April twenty thirteen, Google would

0:49:17.760 --> 0:49:22.560
<v Speaker 1>open up an extremely limited program called Glass Explorers. So

0:49:22.640 --> 0:49:24.960
<v Speaker 1>I guess actually it was dragon Con twenty thirteen, not

0:49:25.040 --> 0:49:28.520
<v Speaker 1>dragon Con twenty twelve, which totally makes sense. I can't

0:49:28.560 --> 0:49:31.359
<v Speaker 1>tell those years apart dragon Con to dragon Con, they

0:49:31.400 --> 0:49:36.840
<v Speaker 1>all bleed together. But this program, the Glass Explorer's program,

0:49:37.480 --> 0:49:40.240
<v Speaker 1>was a pilot testing program. It was really a beta

0:49:40.280 --> 0:49:43.200
<v Speaker 1>test for the technology itself, and you had to apply

0:49:43.600 --> 0:49:45.719
<v Speaker 1>to be in it. You actually had to fill out

0:49:45.719 --> 0:49:49.680
<v Speaker 1>an online form to explain how you would use Google

0:49:49.719 --> 0:49:53.080
<v Speaker 1>Glass and why you think you would be a good

0:49:53.120 --> 0:49:56.880
<v Speaker 1>candidate for the Glass Explorer program. Not only that, but

0:49:56.920 --> 0:49:59.319
<v Speaker 1>you had to pay for it. You couldn't just get

0:49:59.320 --> 0:50:04.040
<v Speaker 1>a pair. They cost one thousand, five hundred dollars fifteen

0:50:04.120 --> 0:50:07.520
<v Speaker 1>hundred dollars for a pair of Google Glass. Now, the

0:50:07.560 --> 0:50:10.400
<v Speaker 1>application process was pretty simple, but it meant that Google

0:50:10.440 --> 0:50:14.560
<v Speaker 1>could very quickly go through this huge number of applications

0:50:14.560 --> 0:50:17.160
<v Speaker 1>and decide which ones sound like good choices and which

0:50:17.160 --> 0:50:22.000
<v Speaker 1>ones don't. Now, in my case, our company bought the

0:50:22.000 --> 0:50:24.520
<v Speaker 1>pair of Google Glass. I applied for them, but it

0:50:24.560 --> 0:50:26.879
<v Speaker 1>was a company purchase, so I don't actually own those

0:50:26.920 --> 0:50:30.719
<v Speaker 1>Google glass anymore, but I was able to buy some.

0:50:30.920 --> 0:50:32.400
<v Speaker 1>Now I'm going to tell you a funny little story

0:50:33.120 --> 0:50:35.600
<v Speaker 1>that happened to me. And this is all because Jonathan

0:50:35.960 --> 0:50:39.040
<v Speaker 1>doesn't pay enough attention when he fills out online forms.

0:50:40.800 --> 0:50:42.360
<v Speaker 1>So in the United States, there were a couple of

0:50:42.400 --> 0:50:45.359
<v Speaker 1>different places you could pick up a pair of these

0:50:45.360 --> 0:50:48.920
<v Speaker 1>glasses once you ordered them, and you had to physically

0:50:49.000 --> 0:50:52.360
<v Speaker 1>go to these locations. Google did not want to send

0:50:52.440 --> 0:50:55.200
<v Speaker 1>anything to anyone because they didn't want to deal with

0:50:55.239 --> 0:51:01.040
<v Speaker 1>the case of someone intercepting a shipment and stealing it

0:51:01.280 --> 0:51:04.359
<v Speaker 1>or selling it or breaking it apart or whatever. They

0:51:04.360 --> 0:51:07.000
<v Speaker 1>wanted to keep a tight rain on who actually got

0:51:07.040 --> 0:51:09.759
<v Speaker 1>their hands on these Google glass So as part of that,

0:51:09.800 --> 0:51:12.440
<v Speaker 1>you had to go to one of these physical locations

0:51:12.480 --> 0:51:14.480
<v Speaker 1>to pick up your pair. They did not have one

0:51:14.480 --> 0:51:17.120
<v Speaker 1>in Atlanta, which is where I live. They had them

0:51:17.120 --> 0:51:21.480
<v Speaker 1>in Los Angeles, in San Francisco, and New York. Out

0:51:21.520 --> 0:51:23.400
<v Speaker 1>of those, New York is the easiest for me. To

0:51:23.440 --> 0:51:26.280
<v Speaker 1>get to. New York is a couple of hours flight

0:51:26.440 --> 0:51:29.720
<v Speaker 1>from Atlanta. If I want to go to San Francisco

0:51:29.840 --> 0:51:32.719
<v Speaker 1>or Los Angeles, you're talking four or five hours each way.

0:51:33.960 --> 0:51:37.080
<v Speaker 1>So I decided I would pick up my Google Glass

0:51:37.360 --> 0:51:39.360
<v Speaker 1>in New York, and I filled out the form and

0:51:39.400 --> 0:51:41.920
<v Speaker 1>I indicated the day and location where I wanted to

0:51:41.920 --> 0:51:45.480
<v Speaker 1>pick it up. But then I realized something I had

0:51:45.480 --> 0:51:48.400
<v Speaker 1>double booked myself. Something else was happening the day that

0:51:48.480 --> 0:51:51.719
<v Speaker 1>I had chosen, and Google Glass would allow you to

0:51:51.840 --> 0:51:57.279
<v Speaker 1>change your delivery date one time only. That's it, so

0:51:57.360 --> 0:51:59.560
<v Speaker 1>if you messed up, you could change it once and

0:51:59.600 --> 0:52:01.799
<v Speaker 1>that's all you could do. So I go back on

0:52:01.880 --> 0:52:04.359
<v Speaker 1>there and I'm like, well, I can't take this day

0:52:04.360 --> 0:52:05.840
<v Speaker 1>that I thought I was gonna do. I'm going to

0:52:05.920 --> 0:52:08.399
<v Speaker 1>do this other day. So I chose a different day.

0:52:09.280 --> 0:52:12.200
<v Speaker 1>I did not realize, however, that by choosing a different day,

0:52:13.040 --> 0:52:16.839
<v Speaker 1>my choice of destination got reset to the default, which

0:52:16.920 --> 0:52:21.759
<v Speaker 1>was Los Angeles. So instead of rescheduling to fly to

0:52:21.840 --> 0:52:25.400
<v Speaker 1>New York, I rescheduled to fly to La So I

0:52:25.440 --> 0:52:29.160
<v Speaker 1>actually had to fly to Los Angeles go to Venice, California,

0:52:29.480 --> 0:52:32.640
<v Speaker 1>which is where Google has an office, and pick up

0:52:32.680 --> 0:52:36.279
<v Speaker 1>my pair of Google Glass. Bright side of it is

0:52:37.239 --> 0:52:39.480
<v Speaker 1>the day after I got my Google Glass, I got

0:52:39.480 --> 0:52:41.480
<v Speaker 1>to really try it out at the happiest place on

0:52:41.560 --> 0:52:44.719
<v Speaker 1>Earth because I went to Disneyland and I brought my

0:52:44.760 --> 0:52:50.200
<v Speaker 1>Google Glass with me. So funny, stupid story about Jonathan

0:52:50.239 --> 0:52:52.920
<v Speaker 1>not paying attention. Moral of the story is pay attention

0:52:53.000 --> 0:52:57.879
<v Speaker 1>on your online forms, especially if you have to resubmit anyway.

0:52:58.920 --> 0:53:03.160
<v Speaker 1>Back in those days, I still wore eyeglasses. I've had

0:53:03.239 --> 0:53:06.319
<v Speaker 1>laser eye surgery since then, but back when I got

0:53:06.400 --> 0:53:10.160
<v Speaker 1>the Google Glass, I still wore eyeglasses, and Google Glass

0:53:10.200 --> 0:53:12.839
<v Speaker 1>at that point had not been outfitted to work with

0:53:13.400 --> 0:53:17.560
<v Speaker 1>existing pairs of glasses. You could either wear Google Glass

0:53:17.760 --> 0:53:19.320
<v Speaker 1>or you could wear a pair of glasses, but you

0:53:19.360 --> 0:53:22.480
<v Speaker 1>couldn't really do both unless you worked for Google like

0:53:22.760 --> 0:53:26.400
<v Speaker 1>Sergey Brinn, and you could have someone make a custom

0:53:26.440 --> 0:53:29.279
<v Speaker 1>pair for you. So instead I would have to wear

0:53:29.320 --> 0:53:32.000
<v Speaker 1>contact lenses. This was one of those early complaints about

0:53:32.000 --> 0:53:34.279
<v Speaker 1>the Google Glass program. A lot of people wanted to

0:53:34.280 --> 0:53:38.920
<v Speaker 1>be able to attach the Google Glass part to an

0:53:38.920 --> 0:53:40.799
<v Speaker 1>existing pair of glasses, and there was just no way

0:53:40.840 --> 0:53:44.520
<v Speaker 1>you could do that In May twenty fourteen, Google opened

0:53:44.560 --> 0:53:47.200
<v Speaker 1>up the Explorer program and allowed more folks to join,

0:53:47.760 --> 0:53:51.240
<v Speaker 1>and there were talks of special Google Glass stores, including

0:53:51.320 --> 0:53:54.640
<v Speaker 1>floating barges, off the coast of places like San Francisco

0:53:54.719 --> 0:53:57.360
<v Speaker 1>and New York. And these were meant to be interactive

0:53:57.400 --> 0:54:00.520
<v Speaker 1>tech spaces and perhaps even a high end life luxury

0:54:00.600 --> 0:54:04.719
<v Speaker 1>showroom for Google Glass. But by June twenty fourteen, so

0:54:04.840 --> 0:54:07.960
<v Speaker 1>May twenty fourteen, this is all in the news, and

0:54:08.040 --> 0:54:10.120
<v Speaker 1>in fact, the barges have been kind of coming together

0:54:10.160 --> 0:54:12.840
<v Speaker 1>over the last couple of years, but in June twenty fourteen,

0:54:12.880 --> 0:54:16.799
<v Speaker 1>the plans for the barges were I guess scuttled is

0:54:16.840 --> 0:54:19.720
<v Speaker 1>a good word if we're talking about barges. The plans

0:54:19.719 --> 0:54:23.479
<v Speaker 1>were scuttled. The barges weren't scuttled immediately, but the plans were.

0:54:24.880 --> 0:54:27.759
<v Speaker 1>They never saw service, they never came online, they never

0:54:27.800 --> 0:54:30.880
<v Speaker 1>became stores. They did raise a lot of interest as

0:54:30.920 --> 0:54:33.719
<v Speaker 1>people watched them take form on a daily basis, but

0:54:34.080 --> 0:54:36.480
<v Speaker 1>they disappeared with about as much of a whimper as

0:54:36.600 --> 0:54:41.440
<v Speaker 1>could be. They were never really explained, and so they

0:54:41.560 --> 0:54:44.360
<v Speaker 1>kind of started to become something and then went away

0:54:44.560 --> 0:54:47.000
<v Speaker 1>before anyone could really figure out what exactly they were

0:54:47.120 --> 0:54:54.160
<v Speaker 1>going to turn into. In January twenty fifteen, Google pulled

0:54:54.200 --> 0:54:59.040
<v Speaker 1>the plug on the Explorer program because ultimately it had

0:54:59.080 --> 0:55:02.680
<v Speaker 1>been a failure, but not necessarily for the reasons you

0:55:02.760 --> 0:55:08.120
<v Speaker 1>might think. So let's rewind a little bit. It's twenty

0:55:08.200 --> 0:55:13.040
<v Speaker 1>twelve and Project Glass has a divided team. You got

0:55:13.080 --> 0:55:17.120
<v Speaker 1>two main camps of engineers who are disagreeing about a

0:55:17.280 --> 0:55:22.160
<v Speaker 1>fundamental aspect of Google Glass. One team thinks this should

0:55:22.200 --> 0:55:25.160
<v Speaker 1>be a persistent wearable device, meaning you put it on

0:55:25.440 --> 0:55:27.400
<v Speaker 1>and you wear it all day long. It's like a

0:55:27.400 --> 0:55:32.560
<v Speaker 1>fashion accessory, it belongs as part of your outfit. The

0:55:32.600 --> 0:55:35.080
<v Speaker 1>other team disagrees and says, no, this should be something

0:55:35.080 --> 0:55:38.480
<v Speaker 1>that you're using for specific use cases. So a situation

0:55:38.600 --> 0:55:41.279
<v Speaker 1>comes up when you would need Google Glass. That's when

0:55:41.320 --> 0:55:43.239
<v Speaker 1>you put it on, and then when that's over, you

0:55:43.280 --> 0:55:47.439
<v Speaker 1>take it off again. The two can't agree with which

0:55:47.480 --> 0:55:51.560
<v Speaker 1>direction they should go in. Saragey Brinn, who's excited about

0:55:51.560 --> 0:55:54.360
<v Speaker 1>the technology but impatient to wait and get all of

0:55:54.360 --> 0:55:57.200
<v Speaker 1>this susted out, has an idea. Instead of relying on

0:55:57.239 --> 0:56:01.040
<v Speaker 1>a relatively small group of engineers and developers, why not

0:56:01.200 --> 0:56:05.279
<v Speaker 1>create a beta testing program invite a wider group of

0:56:05.280 --> 0:56:08.000
<v Speaker 1>people to use it in the real world and take

0:56:08.000 --> 0:56:11.560
<v Speaker 1>that information as a way of developing it further. So,

0:56:11.600 --> 0:56:15.120
<v Speaker 1>in other words, you open this up, you get a

0:56:15.160 --> 0:56:18.000
<v Speaker 1>lot more information from a lot more people using it

0:56:18.040 --> 0:56:20.799
<v Speaker 1>in a lot of different situations, and you see where

0:56:20.800 --> 0:56:23.560
<v Speaker 1>it works and where it doesn't work, and you make changes.

0:56:23.760 --> 0:56:26.160
<v Speaker 1>If it works in one case, maybe you pursue that

0:56:26.200 --> 0:56:28.880
<v Speaker 1>a little more. If it doesn't work in another, maybe

0:56:28.880 --> 0:56:31.080
<v Speaker 1>you change gears or you try to figure out a

0:56:31.080 --> 0:56:34.560
<v Speaker 1>way to make it work in that situation. But the

0:56:34.600 --> 0:56:39.080
<v Speaker 1>point was opening it up to more people meant more information,

0:56:39.320 --> 0:56:42.640
<v Speaker 1>and more information meant that they could make better decisions.

0:56:43.800 --> 0:56:47.799
<v Speaker 1>And this was not a bad idea. It could teach

0:56:47.840 --> 0:56:50.160
<v Speaker 1>Google how people would use the technology and where they

0:56:50.200 --> 0:56:53.640
<v Speaker 1>should concentrate on building out features. It was really just

0:56:53.800 --> 0:56:57.040
<v Speaker 1>a larger part of the overall Google Glass experiment, only

0:56:57.080 --> 0:57:00.200
<v Speaker 1>there was a small problem. The unveiling of Google Glass

0:57:01.000 --> 0:57:04.920
<v Speaker 1>made it a prestige item. The way they showed it

0:57:04.960 --> 0:57:07.560
<v Speaker 1>off and the way they rolled it out meant that

0:57:07.600 --> 0:57:13.000
<v Speaker 1>it became an object of exclusivity. You had to apply

0:57:13.239 --> 0:57:15.640
<v Speaker 1>to be in the club for one thing, so people

0:57:15.640 --> 0:57:18.320
<v Speaker 1>were either in it or they weren't. You had to

0:57:18.320 --> 0:57:21.400
<v Speaker 1>pay fifteen hundred dollars for it, which meant that you

0:57:21.480 --> 0:57:24.000
<v Speaker 1>needed to have a pretty good amount of discretionary income

0:57:24.040 --> 0:57:27.080
<v Speaker 1>if you were going to buy something like this. Wearing

0:57:27.080 --> 0:57:30.240
<v Speaker 1>Google Glass didn't just say I'm interested in technology. It

0:57:30.280 --> 0:57:33.120
<v Speaker 1>also said I have the money to blow on something

0:57:33.280 --> 0:57:37.160
<v Speaker 1>that hasn't even become a product yet. And it also

0:57:37.640 --> 0:57:41.680
<v Speaker 1>said I'm in a club and you aren't. And on

0:57:41.720 --> 0:57:45.320
<v Speaker 1>top of that, people began to express concerns about privacy issues.

0:57:46.240 --> 0:57:48.480
<v Speaker 1>I mean, how could someone feel like they could maintain

0:57:48.520 --> 0:57:51.040
<v Speaker 1>any sort of sense of privacy if they're going out

0:57:51.040 --> 0:57:54.000
<v Speaker 1>in public and other people have cameras mounted on their

0:57:54.040 --> 0:57:56.720
<v Speaker 1>faces all the time. I mean, that's what Google glass was.

0:57:56.760 --> 0:58:00.240
<v Speaker 1>In part. It was an external camera pointing outward the

0:58:00.280 --> 0:58:03.720
<v Speaker 1>world from the perspective of the person wearing it. Now,

0:58:03.920 --> 0:58:07.320
<v Speaker 1>Google Glass had included a light to indicate whether the

0:58:07.360 --> 0:58:10.200
<v Speaker 1>camera was on or not, so that way people could

0:58:10.200 --> 0:58:13.600
<v Speaker 1>see if perhaps video was being recorded or streamed live

0:58:13.640 --> 0:58:16.400
<v Speaker 1>over the internet, or if a photo was being taken,

0:58:16.680 --> 0:58:18.960
<v Speaker 1>and if the light was off, then presumably it wasn't.

0:58:20.280 --> 0:58:23.680
<v Speaker 1>Now I would encounter strangers who would see me wearing

0:58:23.720 --> 0:58:27.320
<v Speaker 1>these glasses, and they thought it was the most amazing thing. Ever,

0:58:27.440 --> 0:58:30.800
<v Speaker 1>and the day I received my parent Los Angeles, it

0:58:30.880 --> 0:58:33.400
<v Speaker 1>was like I was being treated as a celebrity. People

0:58:33.480 --> 0:58:35.840
<v Speaker 1>were stopping me to ask about the Google Glass. They

0:58:35.840 --> 0:58:38.600
<v Speaker 1>wanted to learn more. They were fascinated by the technology.

0:58:38.720 --> 0:58:41.600
<v Speaker 1>They wanted me to take pictures of them using it.

0:58:42.400 --> 0:58:44.960
<v Speaker 1>But then I got home and I got around my friends.

0:58:46.080 --> 0:58:48.280
<v Speaker 1>My friends were different because I hung out with my

0:58:48.320 --> 0:58:51.000
<v Speaker 1>friends all the time. They knew me. But now I've

0:58:51.000 --> 0:58:53.920
<v Speaker 1>got a camera on my face pointed at them. And

0:58:54.080 --> 0:58:56.480
<v Speaker 1>more than once I had friends ask me if I

0:58:56.560 --> 0:58:58.520
<v Speaker 1>might take off the Google Glass while I had a

0:58:58.520 --> 0:59:01.800
<v Speaker 1>conversation with them, because they didn't feel comfortable with the

0:59:01.840 --> 0:59:04.320
<v Speaker 1>thought of a camera looking at them, even if the

0:59:04.360 --> 0:59:07.280
<v Speaker 1>camera was demonstrably off, if they knew for a fact

0:59:07.320 --> 0:59:10.760
<v Speaker 1>I wasn't using Google Glass, it was still uncomfortable. And

0:59:10.760 --> 0:59:13.040
<v Speaker 1>this was a problem that was widespread. It wasn't just

0:59:13.120 --> 0:59:19.480
<v Speaker 1>anecdotal in my case. So people who were in this

0:59:19.680 --> 0:59:23.720
<v Speaker 1>program began to be called a new name. The official

0:59:23.800 --> 0:59:28.960
<v Speaker 1>name was Glass Explorer, but the new name was Glasshole.

0:59:31.600 --> 0:59:36.040
<v Speaker 1>That hurt. The technology was not ready for a full

0:59:36.080 --> 0:59:38.840
<v Speaker 1>consumer product. It was never intended to be that. It

0:59:38.920 --> 0:59:42.280
<v Speaker 1>was meant to be a test bed for this technology.

0:59:43.160 --> 0:59:45.600
<v Speaker 1>And if you got involved in the program, and if

0:59:45.640 --> 0:59:48.240
<v Speaker 1>you were honest with yourself about what you were doing

0:59:48.240 --> 0:59:51.320
<v Speaker 1>and what the product was for, or what the Google

0:59:51.320 --> 0:59:53.960
<v Speaker 1>Glass was for, you should have been fine with that.

0:59:54.200 --> 0:59:56.480
<v Speaker 1>You knew from the get go that this was a

0:59:56.680 --> 1:00:01.120
<v Speaker 1>testing phase of a technology, not something that was ready

1:00:01.120 --> 1:00:04.560
<v Speaker 1>for prime time. But people began to get frustrated with

1:00:04.560 --> 1:00:08.560
<v Speaker 1>glasses limited utility. They'd say, like, after a couple of months,

1:00:08.640 --> 1:00:12.160
<v Speaker 1>they just stopped wearing them because really, I mean, you've

1:00:12.160 --> 1:00:14.040
<v Speaker 1>got a camera in your pocket already, why do you

1:00:14.080 --> 1:00:17.640
<v Speaker 1>need another one. They weren't putting Google Glass through more

1:00:17.640 --> 1:00:20.680
<v Speaker 1>and more uses, which meant that the program was becoming

1:00:20.880 --> 1:00:25.560
<v Speaker 1>decreasingly important. Over at Google. They were getting less data,

1:00:26.360 --> 1:00:28.080
<v Speaker 1>which is what they needed in the first place to

1:00:28.080 --> 1:00:34.920
<v Speaker 1>make Google Glass a successful consumer product. So there wasn't

1:00:35.040 --> 1:00:39.600
<v Speaker 1>just enough there there to keep people's interest, and the

1:00:39.640 --> 1:00:42.520
<v Speaker 1>wrong sort of folks had jumped into the program. And

1:00:42.560 --> 1:00:44.400
<v Speaker 1>by wrong sort of folks, I mean people who thought

1:00:44.400 --> 1:00:46.920
<v Speaker 1>it was a prestigious thing to be in this club,

1:00:47.720 --> 1:00:51.360
<v Speaker 1>who spent the money as a way of having something

1:00:51.400 --> 1:00:54.280
<v Speaker 1>that other people did not have, not as a way

1:00:54.320 --> 1:00:56.880
<v Speaker 1>of expanding the technology, but as a way of expanding

1:00:56.920 --> 1:01:01.720
<v Speaker 1>their own status among others, and so interest and support

1:01:01.760 --> 1:01:05.240
<v Speaker 1>began to wane, both inside and outside the company. But

1:01:05.320 --> 1:01:09.200
<v Speaker 1>Glass did not disappear. Lots of those features became incorporated

1:01:09.200 --> 1:01:12.120
<v Speaker 1>into other stuff like Android and Google Home. The phrase

1:01:12.160 --> 1:01:15.760
<v Speaker 1>okay Google is still used to activate Google's Assistant, which

1:01:15.800 --> 1:01:17.480
<v Speaker 1>can be on the phone, it could be on Google Home,

1:01:17.520 --> 1:01:19.680
<v Speaker 1>it can be on other devices. And I apologize if

1:01:19.680 --> 1:01:22.000
<v Speaker 1>once again I woke it up for those of you

1:01:22.040 --> 1:01:26.640
<v Speaker 1>who have Android devices nearby, and that can do a

1:01:26.640 --> 1:01:29.480
<v Speaker 1>lot of different stuff depending upon what Google Assistant is

1:01:29.560 --> 1:01:32.320
<v Speaker 1>running on. For example, at home, I can use it

1:01:32.360 --> 1:01:34.480
<v Speaker 1>to listen to different types of music or control my

1:01:34.560 --> 1:01:37.320
<v Speaker 1>lights on my phone. I can do all sorts of

1:01:37.320 --> 1:01:43.560
<v Speaker 1>different types of features. And you might even encounter Google

1:01:43.680 --> 1:01:48.080
<v Speaker 1>hardware Glass hardware in certain industries because, believe it or not,

1:01:48.200 --> 1:01:51.240
<v Speaker 1>Google Glass does still exist. Google still produces them and

1:01:51.320 --> 1:01:55.400
<v Speaker 1>still licenses it out, but only to other companies. It's

1:01:55.440 --> 1:01:58.600
<v Speaker 1>a business to business product now, it's not a consumer product.

1:01:59.280 --> 1:02:02.240
<v Speaker 1>This is a program I'm called Google at our Glass

1:02:02.280 --> 1:02:05.640
<v Speaker 1>at work, I should say Glass at work. So rather

1:02:05.720 --> 1:02:08.920
<v Speaker 1>than this consumer product, this is a device that gives

1:02:08.920 --> 1:02:13.120
<v Speaker 1>real world assistant to people working in various industries, and

1:02:13.160 --> 1:02:15.800
<v Speaker 1>it all depends upon the augmented reality apps that the

1:02:16.000 --> 1:02:18.960
<v Speaker 1>glasses are running. But it could be something like what

1:02:19.040 --> 1:02:22.160
<v Speaker 1>I was talking about before with mechanics, giving real time,

1:02:22.680 --> 1:02:26.280
<v Speaker 1>overlaid information on how to do a repair or how

1:02:26.360 --> 1:02:28.880
<v Speaker 1>to take apart an engine or how to build one.

1:02:29.840 --> 1:02:32.280
<v Speaker 1>It could be for medical use, it could be even

1:02:32.360 --> 1:02:35.160
<v Speaker 1>just for corporate use. There are a lot of reasons

1:02:35.200 --> 1:02:39.760
<v Speaker 1>that Google Glass could come in handy. So it is

1:02:39.800 --> 1:02:43.680
<v Speaker 1>still around. It's just not a prestige product for glass holes.

1:02:45.000 --> 1:02:49.040
<v Speaker 1>Now it's doing real work. The sad thing is, I

1:02:49.040 --> 1:02:51.880
<v Speaker 1>bet Google glasses progress would be much further along if

1:02:51.920 --> 1:02:54.400
<v Speaker 1>there had not been such a hoopla about it when

1:02:54.440 --> 1:02:57.800
<v Speaker 1>it was first launched. If it had been launched more

1:02:57.960 --> 1:03:01.560
<v Speaker 1>like we're trying to develop this technology and less like

1:03:01.600 --> 1:03:05.280
<v Speaker 1>a rock star, then maybe people wouldn't have gotten so

1:03:05.440 --> 1:03:08.400
<v Speaker 1>wrapped up in it, And maybe that means that Google

1:03:08.440 --> 1:03:11.560
<v Speaker 1>would have been able to get more helpful information from

1:03:11.600 --> 1:03:13.840
<v Speaker 1>people who are really using the technology the way it

1:03:13.880 --> 1:03:17.800
<v Speaker 1>was intended, and maybe we would see Google Glass much

1:03:17.800 --> 1:03:21.160
<v Speaker 1>further in development and maybe would even be a consumer product.

1:03:22.080 --> 1:03:25.240
<v Speaker 1>I'm sure it was discouraging to the Google Glass team

1:03:25.800 --> 1:03:31.040
<v Speaker 1>to see how things went awry, but it does still

1:03:31.040 --> 1:03:35.080
<v Speaker 1>exist and AR is still a thing. There are related

1:03:35.120 --> 1:03:38.040
<v Speaker 1>products that are also pushing augmented reality into a new era.

1:03:38.120 --> 1:03:42.160
<v Speaker 1>There's Microsoft's hollow lens that's a great example. There's Magic Leap,

1:03:42.280 --> 1:03:45.560
<v Speaker 1>about which we know very little bits and pieces of

1:03:45.600 --> 1:03:48.800
<v Speaker 1>information leak out over time, but we're always learning a

1:03:48.800 --> 1:03:51.280
<v Speaker 1>little bit more. But I'm always going to have a

1:03:51.320 --> 1:03:54.560
<v Speaker 1>soft spot in my heart for Google Glass. It's something

1:03:54.560 --> 1:03:57.000
<v Speaker 1>that I think if it had just had a little

1:03:57.000 --> 1:03:59.840
<v Speaker 1>bit of a lower key rollout, we'd be looking at

1:03:59.880 --> 1:04:02.960
<v Speaker 1>a very different world with wearables right now, or at

1:04:03.040 --> 1:04:06.960
<v Speaker 1>least a more advanced one. Hope you enjoyed that classic

1:04:07.000 --> 1:04:10.760
<v Speaker 1>episode about Google Glass. Obviously you could argue this is

1:04:10.800 --> 1:04:16.920
<v Speaker 1>another case of Google shelving a product after having some

1:04:17.120 --> 1:04:21.919
<v Speaker 1>issues getting it to actually, you know, gain traction. Whether

1:04:22.000 --> 1:04:25.200
<v Speaker 1>Google will ever make a huge jump back in the

1:04:25.280 --> 1:04:28.040
<v Speaker 1>mixed reality remains to be seen. Honestly, it kind of

1:04:28.080 --> 1:04:31.160
<v Speaker 1>remains to be seen if anyone can really get that

1:04:31.240 --> 1:04:35.520
<v Speaker 1>technology to a point where it has mainstream adoption. It's

1:04:35.560 --> 1:04:39.320
<v Speaker 1>such an expensive and difficult technology to master that it

1:04:39.360 --> 1:04:42.080
<v Speaker 1>may be a while before we see that. Apple certainly

1:04:42.120 --> 1:04:43.840
<v Speaker 1>is going to give it a shot, so I have

1:04:43.880 --> 1:04:46.280
<v Speaker 1>to keep our eyes on that. Hope you're all well

1:04:46.560 --> 1:04:55.680
<v Speaker 1>and I'll talk to you again really soon. Tech Stuff

1:04:55.760 --> 1:05:00.320
<v Speaker 1>is an iHeartRadio production. For more podcasts from iHeartRadio, visit

1:05:00.360 --> 1:05:03.880
<v Speaker 1>the iHeartRadio app, Apple Podcasts, or wherever you listen to

1:05:03.920 --> 1:05:04.840
<v Speaker 1>your favorite shows.