Google IO 2013 – Google Glass Sessions


All Google Glass related IO 2013 Sessions in one place


Google I/O 2013 – Voiding Your Warranty: Hacking Glass

Hyunyoung Song, P.Y. Laligand
Glass is ready for hacking! See what is possible with the hardware platform and how you can gain root access. Learn how to run your own experimental applications. Disclaimer: you’ll be stepping into uncharted and unsupported territory!


Google I/O 2013 – Building Glass Services with the Google Mirror API

The Google Mirror API is a simple but powerful set of RESTful APIs for building Glassware. In this session we’ll review some first principles for Glass development, paradigms of the Google Mirror API, and the rapid track from concept to prototype. We will cover both standard use cases and ones that push the boundaries of the API.


Google I/O 2013 – Fireside Chat with the Glass Team

Charles Mendis, Isabelle Olsson, Steve Lee, Timothy Jordan
Join several key members of the Glass team as they discuss the path that brought them here. We’ll discuss why Glass is so important to the evolution of wearable technology and how developers can most effectively engage in the ecosystem.


Google Developers Live at I/O 2013 – Project Glass: Icebreaker

Timothy Jordan, 3rd party developers
Icebreaker is the story of three developers from three parts of the country who came together at the Glass Foundry and built a Glass service in their spare time. We’ll take a brief look at the service and talk about the experience of developing with the Google Mirror API, and what design considerations came into play when building specifically for Glass.


Google I/O 2013 – Developing For Glass


0:08 TIMOTHY JORDAN: You haven’t even heard anything yet.
0:11 That’s OK.
0:12 You can applaud as much as you want for the next hour.
0:18 So I’m Timothy Jordan.
0:19 I’m a Developer Advocate on Project Glass.
0:23 A couple of things before we get started, just to set some
0:26 context, though many of you will already know
0:28 some of this detail.
0:30 Google[x]
0:31 is the moonshot factory at Google.
0:35 It’s about these radical ideas for changing the world and
0:40 improving the way we live.
0:42 And Project Glass is one of those moonshots.
0:45 It’s a moonshot about our relationship to technology.
0:49 This is strange standing up on this little step back here.
0:54 Let’s just pretend it doesn’t happen.
0:56 It’s about technology that’s there when you need it and out
0:59 of the way when you don’t.
1:01 And what do I mean by that?
1:03 Some of you have heard this story, but I’m going to tell
1:05 it again, because it’s really impactful for me.
1:08 When you’re at a concert and the band takes the stage,
1:11 nowadays 50,000 phones and tablets go into the air, which
1:18 isn’t all that weird, except people seem to be looking at
1:21 the tablets more than they are the folks on stage or the
1:24 experience that they’re having.
1:26 And it’s crazy.
1:27 Because we love what technology gives us.
1:31 But it’s a bummer when it gets in the way, when it gets in
1:33 between us and our lives.
1:35 And that’s what Glass is addressing is, how do we have
1:38 those benefits of technology and yet get it out of the way
1:42 at the same time?
1:44 Now up until recently, you had to take our word for that.
1:49 But we’ve started selling devices to
1:52 people outside of Google.
1:54 In fact, I see a lot of them in this room today.
1:55 Could you raise your hand if you have Glass?
1:58 Oh, a bunch of you.
2:00 And it’s a heck of an adventure we’re on together.
2:03 Who would have thought a year ago we’d be in this room
2:06 adopting this new technology together
2:09 and building it together?
2:11 And that’s really what this session is about, that and my
2:16 really cool roller coaster video.
2:19 Fair warning, there are not going to be any airships or
2:22 parachuting today.
2:26 We did that, and we did it pretty well.
2:28 Today we’re going to focus on developers, that’s you, and
2:33 what you’re doing with Glass and the conversation that
2:35 we’re having together.
2:38 Now this session, I’m going to cover the general landscape of
2:42 building for Glass, the platform
2:44 and design and examples.
2:45 I’ll talk about that in a moment.
2:47 There are some other sessions that you’ll want to come to at
2:51 Google I/O today.
2:53 One of them is “Building on the Mirror API”.
2:56 Alain and Jenny are going to go into detail about using the
2:59 mirror API to deploy your Glass service.
3:03 There’s going to be a session on “Voiding Your Warranty”, if
3:05 you want to tinker around with Glass and have
3:07 some fun that way.
3:09 And then at the end of the day, we have a fireside chat
3:11 with some of our leadership, and that’s going
3:13 to be a lot of fun.
3:14 We’ll answer a lot of your questions then.
3:19 For right now, we’ve got three things on the menu.
3:24 First off, I’m going to talk about platform, what you can
3:27 do today with a Mirror API and a little bit more.
3:32 Next, I’m going to talk about design.
3:35 Now the platform, for those of you that have checked out the
3:39 documentation, is the easy part.
3:42 It’s JSON over REST.
3:43 It’s not new technology.
3:45 We’re just using it in new way.
3:47 And that’s where design comes in.
3:49 This is the interesting challenge with Glass right
3:51 now, and this is where we’re innovating, building the
3:54 service for a user that makes sense on Glass.
3:58 And to that end, we’re also going to take a look at some
4:01 examples, some of the early work people are doing in the
4:06 area of Glass, building these Glass services for users.
4:12 All right.
4:12 Now before we jump into all that material, I’d like to
4:14 give you a demo.
4:15 Who here has not seen a live demo of Glass?
4:19 There’s still a few of you.
4:21 OK.
4:21 And I understand that we have another room and a livestream.
4:23 So this is for all of you.
4:25 I’m just going to go over some of the basic concepts.
4:32 This is always fun to do live demos.
4:34 We’ll see if Wi-Fi works.
4:37 Either way, it’ll be fun.
4:38 I have a cable attached to this demo device so that you
4:41 can see my screen.
4:41 We did a little bit of hacking so you could see what I see.
4:44 Now it’s going to be more choppy and a little more
4:47 delayed on that screen.
4:49 It’s much more smooth on Glass.
4:50 And if you can make a new friend at Google I/O here who
4:53 has Glass, you can ask them very nicely if you can demo
4:55 their Glass.
4:56 I recommend that you do that.
4:58 Because putting Glass on and seeing this rich display and
5:01 experiencing it is so much different than just seeing it
5:04 on the projection screen here.
5:06 But I’ll give you a quick tour anyway.
5:11 Now the first thing that you note when I put on Glass– and
5:14 this speaks to my point about the purpose of Glass–
5:17 is that it’s not in the way.
5:19 It’s not in my line of sight, but it is in my field of view.
5:23 And the key thing there is that it’s not
5:25 between me and my life.
5:26 It’s not that tablet at the concert where I’m looking at
5:28 that instead of what I’m doing.
5:31 But at the same time, whenever I want Glass, all I have to do
5:33 is look up, and there it is.
5:35 By bringing technology closer, we can get it
5:38 more out of the way.
5:40 So when you do put on Glass, when you do get a chance to
5:42 demo, make sure that you take that step.
5:44 It’s really key.
5:46 There’s two ways to wake up or activate Glass.
5:50 One of them is with the touchpad here.
5:51 I’m just going to tap on the side there, and you’ll see I
5:54 come to this home screen.
5:56 It’s got a clock.
5:57 Now if I swipe down on that touched right at my temple,
6:02 it’s going to dismiss it.
6:02 It’s kind of like the Back button on your Android phone.
6:05 Another way I can activate Glass is by looking up with my
6:08 head, and I get the same screen.
6:12 Cool?
6:13 Right.
6:13 Voice commands.
6:14 Mind if I take a picture?
6:16 I’ll take that as a resounding, sure, go ahead.
6:20 OK, Glass, take a picture.
6:25 And there we are.
6:26 Aw, you all look so beautiful.
6:29 Now let’s go ahead and share that with the world, shall we?
6:34 Swipe forward, tap on that item.
6:38 I get this menu, tap on Share.
6:42 I’m going to swipe my Google+ friends
6:44 circle and tap to share.
6:47 That’s it.
6:49 So what you saw there is I took a picture.
6:51 That picture was then put on my timeline.
6:53 I swiped forward to get the last item on my timeline.
6:56 As I swiped forward, I go back in time.
6:59 If I tap on any of those items, I get a menu.
7:01 In this case, there was an option for sharing.
7:04 I took that.
7:04 I saw my sharing contacts, and I chose my
7:08 Google+ circle for friends.
7:10 I’m going to come back to all these concepts.
7:14 OK, Glass, google, how do you say welcome in German?
7:26 Did you all just start Wi-Fi?
7:31 Oh, there we go.
7:32 Well, it recognized what I said.
7:33 Now if I had a strong connection in this conference
7:36 room, it would then come back and showed me willkommen and
7:40 would have said it to me at the same time.
7:42 Now you notice I don’t have anything in my ear, but I can
7:45 still get audio.
7:46 And it’s relatively private to me.
7:48 If you were right next to me, you might hear a murmur.
7:50 But otherwise, it’s just for me.
7:53 Pretty cool, huh?
7:54 All right.
7:55 So that’s your quick demo.
7:56 Let’s get back to the slides, shall we?
8:09 All right.
8:09 So let’s start with platform.
8:12 What we have out there today is the Google Mirror API.
8:15 I want to go through some of the concepts I just showed you
8:18 in the demo and how you can affect those
8:21 with the Mirror API.
8:23 This is how the Mirror API works.
8:26 It’s RESTful architecture.
8:30 JSON is the payload encoding, and OAuth
8:33 is the install process.
8:35 Now this is a developer conference, so I’m expecting
8:37 to see a lot of hands here.
8:38 Who knows what REST is?
8:41 A lot of hands.
8:42 Great.
8:43 Who knows what JSON is?
8:44 A lot of hands again.
8:46 Excellent.
8:47 And who knows what OAuth is?
8:49 Slightly fewer, but still a lot of hands.
8:51 OK.
8:51 That’s great.
8:52 Let me just touch on each of those for the
8:54 audience playing at home.
8:56 OAuth is an authentication mechanism.
8:59 And for the Mirror API, it’s analogous
9:01 to the install process.
9:02 The user gives permission to the Glass service to write
9:06 into their timeline and get updates.
9:10 JSON is the encoding, JavaScript Object Notation.
9:13 It’s pretty much the language that we send over REST, which
9:17 is the protocol.
9:18 And that’s just HTTP.
9:20 It’s like submitting a web form, but in the background.
9:26 And all that work happens right here.
9:28 And this is what I think is really key about the Mirror
9:31 API is that it’s super simple to develop for, and yet you
9:35 could also build powerful services.
9:37 All your work is going to be right here between your
9:40 service and Google.
9:42 And then Google handles the sync to Glass, dealing with
9:46 any connectivity issues and actually rendering things on
9:49 the client on Glass.
9:56 And there’s a handful of major topics we’re
9:58 going to talk about.
9:58 First, we’re going to talk about the Timeline.
10:00 You saw that.
10:00 We’re going to talk about Share Contacts.
10:03 You saw those.
10:03 It’s my Google+ friends I shared with.
10:06 We’re going to talk about Subscriptions.
10:08 This is how your service gets updates when a
10:10 user performs an action.
10:12 And I might touch a little bit on Location.
10:15 You can get Location updates periodically
10:19 from Glass as well.
10:23 OK So first off, Timeline cards.
10:25 Now Timeline cards can be text.
10:28 It can be images, video.
10:31 It can be rich HTML.
10:34 And they can also be bundles.
10:37 So now you saw, when I was on the Timeline there, there was
10:40 a single item .
10:41 It was an image.
10:41 I tapped on it, and I got a menu.
10:43 If that item had a page scroll in the upper right, like this
10:46 Timeline item here, and I tapped on it, it would open up
10:50 into a sub-timeline.
10:54 This is how you can group multiple Timeline cards
10:57 together into a single top level Timeline item.
11:01 And this is good for a couple different things, and I’ll
11:03 discuss in detail some best practices here
11:05 in the design section.
11:07 But you might want to do pagination with this.
11:10 Or you might want to do threading.
11:11 For example, if I’m going to have a conversation over SMS,
11:14 that’s going to be in a threaded bundle with my latest
11:17 message back or forth on top.
11:19 I tap in, and I can go through the whole conversation.
11:22 Or maybe I want to show a little bit more of a summary
11:27 than just on one Timeline card.
11:29 So I insert a long text string, and it automatically
11:32 paginates for me.
11:37 Now menu items, like the Share menu item that you saw when I
11:40 tapped on the image, you can add these yourself.
11:43 And they can be of two kinds.
11:44 One, they can be a system menu item.
11:47 And that you just have to name.
11:48 And it uses some built-in functionality of Glass.
11:52 This could be Reply, Read Aloud.
11:53 These are system menu items.
11:55 Reply will put the user into voice dictation mode, take
11:58 transcription, send you that text and the audio file, and
12:02 then you can use that as you do in your service.
12:05 For Read Aloud, Glass will read aloud to speakable text
12:08 or the text that it finds on the Timeline item.
12:11 There can also be custom menu items.
12:14 These are still going to be simple, quick interactions
12:17 that you build.
12:18 But they can have your name and your icon, and they can do
12:21 whatever your service wants them to do.
12:27 Now Shared Contacts.
12:29 Shared Contacts can be for sharing, like I shared to my
12:32 Google+ circle for friends, and then they see that image
12:34 moments later, or something like Ice Breaker, which I’m
12:37 going to talk about a little bit later.
12:39 Some of you might have been playing while you’re here at
12:41 Google I/O. Now that’s just a service that takes an image
12:45 and does something different or interesting with it.
12:49 Now much like the Timeline, which is a RESTful collection
12:52 that you can insert, update, and delete items from, Shared
12:57 Contacts is also a collection.
13:00 And typically how you would do this in the flow of your
13:03 service is the user would OAuth–
13:06 say, hi, I wanted to give you permissions to
13:07 do stuff for me.
13:09 And then immediately your service would insert a shared
13:14 contact and subscribe to updates from that shared
13:17 contact, or anything else the user does in the Timeline that
13:21 the service wants to pay attention to.
13:24 Now the way those subscriptions work, again
13:27 another collection.
13:29 You insert a subscription, and then you start to get updates
13:33 on the endpoint that you specify.
13:38 All right?
13:39 So we have three major collections so far, Timeline,
13:43 insert cards, add menu items, Shared Contacts for the
13:48 sharing menu, and Subscriptions.
13:51 The one last one is Location.
13:54 I’ll talk about that in a moment.
13:55 For Subscriptions, think of it this way.
13:58 If you’ve done pubsubhubbub before, it’s sort of similar.
14:01 You’re going to subscribe by inserting a request into
14:04 Google that creates an item in the subscription collection.
14:08 And then as the user takes actions covered by that
14:11 subscription, Google will inform you by calling the
14:15 endpoint that you specify.
14:17 It’s a lightweight ping, so it doesn’t take a
14:20 lot of network traffic.
14:21 And most of the time all you need is that lightweight ping,
14:23 because it includes a Timeline ID that you
14:25 likely already know.
14:27 But if you want more information, you can then pull
14:30 that item from the Timeline item collection.
14:33 Now Location is very similar.
14:35 You can subscribe to Location.
14:38 And then as the user’s location gets updated, you get
14:42 a notification.
14:43 You pull from the Location collection to get the actual
14:48 latitude and longitude.
14:51 That make sense?
14:53 All right.
14:53 So that’s the platform as we know it today, the Google
14:56 Mirror API.
15:02 Let’s talk a little bit about what the Google Mirror API is
15:04 good for and some of the use cases that will feel a little
15:07 bit forced.
15:09 In our conversations about building stuff on the
15:13 platform, we’re always thinking, as we do around
15:16 Google, what’s good for the user?
15:17 What’s going to provide an excellent Glass
15:21 experience for the user?
15:21 And in those conversations, about 80% to 90% of the ideas
15:25 we come up with are great Glass services for the Google
15:28 Mirror API.
15:30 These include being able to send content to the user and
15:34 microinteractions with that service, like being able to
15:37 reply, or being able to add an emoticon to something or +1
15:43 something, and being able to share out from Glass images
15:48 and video, either to be posted on a social network or for
15:52 your service.
15:53 All those things work incredibly well
15:55 on the Mirror API.
15:57 You can develop them very, very quickly.
16:00 But there’s a handful of things that you might want a
16:05 different kind of aspect to the platform for.
16:09 Those can be when you want your service to work offline.
16:15 Now if I get updates from “The New York Times,” I can see
16:18 them, even if I don’t have a connection.
16:20 But to actually get those updates, I needed a connection
16:22 at that time, or to do those microinteractions.
16:24 Well, what if I have something like Navigation, as you see
16:27 here, where I want to be able to interact and get an
16:33 immediate response from Glass?
16:36 Or what if I want to access hardware features, like the
16:42 Location, in real time on Glass?
16:44 Well, for something like that, you need a native API.
16:46 And that’s something we’re working on right now.
16:48 It’s called the Glass Development Kit.
16:52 We don’t have a lot of details about this right now, because
16:54 we’re actively building it.
16:56 And since we’re in the explorer period and we’re
16:58 building it at the same time, it’s actually a really unique
17:02 place for a product to be, because we’re having a
17:05 conversation right now about what we need to make sure that
17:08 we add to the Glass Development Kit.
17:12 So my ask do you–
17:13 I make an announcement, and then I ask you to do
17:15 something for me–
17:17 is to tell us, what are your dreams for Glass that would
17:20 use the Glass Development Kit but not the Mirror API?
17:23 And what do you want to make sure we cover in that?
17:28 Later in the day, if you go to the hack your Glass session,
17:31 HY and PY might talk a little bit more about the GDK.
17:34 And we might talk about in the Fireside Chat.
17:36 And of course, if you want to come up and ask me later, we
17:38 can talk about it in more depth.
17:40 And I’ll take questions at the end.
17:45 All right.
17:47 So we’ve talked about platform.
17:48 We’ve talked about the Google Mirror API, which is what you
17:50 build with today to get services to users and play
17:53 with the Glass experience and really understand the design
17:56 and user experience of Glass.
17:57 And we’ve talked a little bit about the GDK that’ll be
18:00 coming some time in the future, where you’ll be able
18:03 to do things like offline and immediate access to hardware.
18:09 The user experience, this big next section of my talk, is
18:15 about design.
18:16 It’s about how do you make an excellent Glass service for
18:19 the user, not just technically?
18:20 But what are the paradigms that you use?
18:22 What are the user patterns that you use?
18:24 And to start with, we have four guidelines that you’ve
18:27 heard me speak about before–
18:29 I’ve covered these in more depth elsewhere, but I want to
18:32 touch on them, because they really add context to all of
18:34 the other items that talk about today–
18:37 the first of which is to design for Glass.
18:41 And this is really key, and there’s a remarkable amount of
18:44 depth in here.
18:46 Because at the top level, you don’t want to take an
18:48 experience on mobile or on the web and just
18:50 stamp it out on Glass.
18:51 It’s not going to work, because Glass is
18:54 fundamentally different.
18:56 And the one essential thing that you must
18:58 do is test on Glass.
19:00 Use Glass in your daily life.
19:03 Add your service, and use your service in your daily life,
19:06 and then you’re really going to know what
19:08 works and what doesn’t.
19:11 The second big thing here is don’t get in the way.
19:17 Remember I talked about what are the things that are good
19:19 for a Glass user.
19:22 Well, getting in the way is not good.
19:24 Getting in the way takes them out of their life and puts a
19:26 barrier between them and what they’re doing.
19:28 And that’s not what we’re doing with Glass.
19:30 We want your service to improve their life.
19:35 And sort of a corollary here is that you never would want
19:38 to take precedence over the user’s experience.
19:41 So you would never want to send them a notification that
19:43 if they didn’t respond would degrade their experience with
19:46 your service.
19:48 They should be able to ignore notifications, and your
19:51 service keeps chugging along, giving them what they want
19:54 when they need it.
19:57 Keep it timely.
19:59 Glass is a very now device.
20:02 Your phone, you might do stuff over the last week.
20:04 Look at your calendar four days from now.
20:08 Your laptop, you’ve got data on there from the last few
20:10 months or year.
20:11 But Glass is really about what are you doing right now.
20:15 And when you think about that your service, you want to
20:16 deliver content to the user that’s important to them at
20:19 that moment.
20:25 And then one last one.
20:26 Avoid the unexpected, especially the unexpected and
20:29 the unpleasant.
20:30 And this is bad on any platform.
20:32 But it’s particularly dangerous on Glass when the
20:36 experience is so intimate to the user.
20:38 They’re wearing your experience.
20:41 So you really need to respect that relationship, and don’t
20:46 do anything unexpected.
20:47 Just Be honest about the intention of your application,
20:51 about your Glassware.
20:53 And give them preferences to be able to get notifications
20:56 maybe during certain times or know how many they’re going to
20:59 get before they sign up.
21:02 All right.
21:02 So those are our four guidelines.
21:03 And those are things that you can kind just
21:04 stick in your pocket.
21:06 And when you look at your Glass service and you have a
21:07 question, is this going to be right for the user, you can
21:10 measure it against those four things really easily.
21:14 And we’ve talked about those before, but since that time
21:18 we’ve been spending more and more time with our partners.
21:20 And we’ve gotten a lot of little lessons as well, a lot
21:23 of user patterns that work really well and a lot of
21:25 learnings around the different paradigms in Glass that I’d
21:28 like to share with you.
21:32 So here are the types of Timeline cards
21:34 that you might use.
21:36 You’ve got text, HTML templates, images, and video.
21:43 I’m going to touch on some notes for each of these.
21:47 Now we also document these on our documentation, and we’ll
21:49 continue to expand these best practices, these tips and
21:52 tricks, as we move forward and as we learn together in this
21:56 explorer period.
21:58 First off, if you’re only sending text, just send text.
22:03 Don’t use an HTML template.
22:05 And the cool thing here is that if the text is too long
22:08 for one Timeline item.
22:09 it’s going to autopaginate.
22:13 So a user can tap on that Timeline item, and there’ll be
22:16 a Read More menu item, and they’ll be able to swipe
22:19 through that text.
22:21 If what you’re sending to the user is text, this is the
22:23 easiest and quickest and most powerful way
22:25 to get that to them.
22:27 And it looks a little bit like this.
22:29 Again, you’ll see that text, tap on it, get to the Read
22:31 More, and you can swipe through multiple pages of
22:33 text, in this case, the dramatically
22:36 interesting Lorem Ipsum.
22:41 OK.
22:41 HTML.
22:42 Now this is when you once more rich or flexible designs.
22:47 And maybe you want to combine both text and
22:49 images on one item.
22:52 Now HTML is a little bit tricky on Glass.
22:54 You really need to test on Glass.
22:56 And we do have a great tool called the Developer
22:58 Playground.
22:59 It’s got the CSS built in.
23:01 You can edit HTML inline and see it right there the web
23:04 browser and hit send and have it go straight to Glass.
23:08 That’s really helpful.
23:09 And we also have these templates.
23:10 We’ve taken some time just like, OK, what are some of the
23:12 big categories of usage for Timeline items?
23:16 We’ve provided these templates for you to go in and edit and
23:20 make your own.
23:24 However, if you want to break past those templates and do
23:27 something a little bit more stylized and specific, you can
23:30 also add a style tag inline with the HTML.
23:33 Now it won’t do JavaScript.
23:35 But you can add your own CSS, your own
23:38 custom IDs and classes.
23:40 Just remember to always test on Glass.
23:43 Start with the Playground, and keep sending those to Glass to
23:45 make sure it renders the way you want it.
23:47 And also, if you use custom HTML, make sure that as we
23:50 upgrade the system software on Glass that you keep testing
23:53 that to make sure nothing changes.
23:58 We have a couple UI grid templates here to get you
24:02 thinking about what’s the padding and the spacing that
24:05 will make your Glassware consistent with the rest of
24:08 the Class UI so that it’s familiar and easy
24:11 to use for the users.
24:20 Photos and video attachment.
24:22 There’s a couple best practices in here.
24:24 First, it’s 16 by 9, and the resolution is 640 by 360.
24:30 You want to use that resolution, if you can.
24:34 And the reason is it’s going to transfer to Glass faster,
24:37 and it’ll be the perfect size for showing full screen.
24:41 It doesn’t need to be resized on Glass.
24:43 It’s going to look as you intended.
24:45 And for videos, they should be short.
24:48 This is for two reasons.
24:49 One, you’re sending it to Glass over the air.
24:51 It’s going to use the user’s data connection.
24:54 But another reason is that, again, we don’t want Glass to
24:57 get in the way of the user and their life.
25:01 So getting a video and looking for 30 seconds or maybe up to
25:05 a minute makes sense.
25:07 I can take that pause when I’m walking between meetings, and
25:09 that can be really magical experience.
25:11 But if you push me 30 minutes of video, I’m never going to
25:13 watch it, for one.
25:15 And it’s going to be distracting and
25:16 confusing to the user.
25:17 It’s about short interactions.
25:18 It’s not about staring up all day.
25:20 It’s about living your life.
25:24 And another thing that I’d like to announce today–
25:27 this will be available in the documentation soon–
25:29 is video streaming.
25:31 So what you know about the Mirror API so far is that if
25:34 you want to upload an image or a video, you add it as an
25:36 attachment to a Timeline item that you insert into the
25:39 Timeline collection.
25:41 You do this once for every user.
25:43 So if you have 1,000 users and you want one video to go to
25:46 all of them, you upload that video 1,000 times.
25:49 It makes more sense to do that for the video intended for
25:52 that user specifically and update to
25:54 them from your service.
25:56 If you’re going to broadcast things to users, what makes
25:59 the most sense is to do video streaming.
26:01 Now we’re going to add some more details about video types
26:03 and quality in our documentation, and that’s best
26:06 place to reference it.
26:07 But you so you know how this works is this is a URL
26:10 attachment.
26:11 So when you insert the Timeline item into the user’s
26:15 Timeline collection, instead of adding a multi-part
26:19 attachment with the video content inline, you can add
26:23 just a URL.
26:25 And then Google’s going to handle the rest.
26:26 That’s pretty cool, right?
26:31 Everybody’s who’s been inserting videos on the Mirror
26:33 API is nodding.
26:34 And that’s nice.
26:36 All right.
26:37 Let’s talk about bundling.
26:38 Bundling is super powerful but tricky.
26:44 There’s a few tips I can give you to do this right so it’s
26:46 going to be really obvious to the user and it’s going to
26:48 make a lot of sense to them.
26:51 First off, there’s many kinds of bundles.
26:55 There’s single item bundles, and there’s
26:57 multiple item bundles.
26:58 Now what do I mean by that?
27:00 A single item bundle is where you insert a single Timeline
27:02 item, you specify the HTML attribute as the cover card,
27:09 and then HTML pages is an array of strings.
27:12 They’re your subsequent pages when the user
27:13 taps into the bundle.
27:15 This is a single Timeline item, so it should logically
27:18 be a single item with multiple pages.
27:21 That’s really straightforward, right?
27:23 The multiple item one, this could be for threading, or it
27:27 could be a collection.
27:28 There’s a couple great examples of this.
27:30 You’ve seen “The New York Times” on Glass.
27:32 That’s a bundle of the latest top headlines from “The New
27:35 York Times” for the last hour.
27:39 You tap into it, and you’ll see those multiple items.
27:42 Threading is something like SMS or messaging back and
27:45 forth in a service.
27:50 All you need to do is insert additional items.
27:52 You set the bundle ID.
27:54 In the case of “The New York Times”, the way they insert
27:57 them will constitute the order.
27:59 In the case of threading, you don’t even worry about that,
28:01 because the latest items are always going to appear on top.
28:06 Now a trick for all of these things, especially the
28:08 multiple item bundles, is to have a digest cover.
28:12 This is a cover not where you say what’s in the bundle but
28:15 you show the user what’s in the bundle.
28:17 And “The New York Times” does a great job of this.
28:19 You’ll see this digest cover has images for a number of the
28:24 headlines contained within.
28:30 Menu items, a couple short notes about this.
28:33 Menu items are one line, and there’s just a few characters.
28:37 This is on purpose, because they’re short and actionable.
28:41 I can easily scan through a good menu and choose what I
28:44 want in just a few moments.
28:46 That means that not only is it really easy to recognize what
28:50 this menu item does, because it’s clear in one or two short
28:52 words, but there’s also a handful of menu items, not
28:56 more than that.
28:59 Always make sure to specify an icon.
29:02 And be careful with Dismiss and Delete.
29:07 These are similar, but they’re a little different.
29:10 Most the time you’re not going to want Dismiss.
29:12 It doesn’t make a lot of sense on Glass.
29:14 Because the way the Timeline works, for those of you that
29:17 have Glass, is you know when updates come in
29:22 and time moves on.
29:23 You just don’t go all the way back on Timeline.
29:25 It just kind of decays over time.
29:28 You’re only looking at your recent stuff.
29:31 So they sort of automatically dismiss, in a way.
29:34 So you wouldn’t want to get the user in the habit of
29:36 having to just dismiss, unless you wanted to give them the
29:39 option, like I don’t want to see this on my Timeline Or
29:41 maybe that’s an indication to your service of what kinds of
29:45 updates they like or they don’t like.
29:48 Delete, on the other hand, when you do this it shouldn’t
29:51 just remove it from the user’s Glass Timeline.
29:55 It should also delete that item on your service.
29:58 A great example of this is when I share an image to
30:00 Google+ and there’s that Delete Item.
30:02 I tap that Delete Item.
30:03 It deletes it from my Glass Timeline, and it deletes the
30:06 post on Google+.
30:08 It’s very clear to the user what it does.
30:14 OK.
30:14 Let’s talk about Shared Contacts.
30:16 A couple notes here.
30:17 Make sure that when you insert a shared contact that the
30:20 image that you use is 640 by 360.
30:23 That way, if it’s the one, it’ll show full screen and
30:26 it’ll be beautiful.
30:29 Make sure to always specify acceptTypes.
30:32 Now these are MIME types that say what your shared contact
30:35 can be used for.
30:36 So maybe you do image slash asterisk, in which case any
30:41 images that the user finds and they tap on that image and the
30:46 Share menu, your shared contact will show up.
30:49 Maybe you also want to do video.
30:52 Now when the user does share items on your service, we have
30:55 two things that people have started to use which make a
30:58 lot of sense, #throughglass and Sent through Glass.
31:02 So with your service, it makes sense to include a hashtag,
31:05 like it’s a post on your service.
31:07 Adding #throughglass is a great way to have a through
31:10 line of what that user is sharing while
31:12 on the go from Glass.
31:14 If you’re doing messaging, however, where maybe it
31:17 doesn’t make sense to have a hashtag, but you still want to
31:19 indicate to somebody that somebody was saying this while
31:22 they were walking between meetings, then Sent through
31:25 Glass makes a lot of sense there, just to append at the
31:28 end of the message.
31:30 Add these, and there’ll be a lot more clarity, as messages
31:33 are going to go through and similar
31:36 to the other Glassware.
31:40 OK.
31:41 Some of those details all on one screen for you.
31:44 There are numbers.
31:46 It’s all really straightforward.
31:52 I’ve been saying the sizes a lot, by the way, because
31:54 that’s one of the things that we’ve noticed as we’ve been
31:56 doing hackathons and building our own software that it was
32:00 one of those things that’s easy to forget.
32:01 But you really do want to play to the size
32:04 of the Glass screen.
32:14 All right.
32:15 Let’s talk about some examples, shall we?
32:18 Examples are really important right now.
32:22 And the reason is that we were all, collectively, me and
32:26 everybody else with Glass in this room, figuring out what
32:28 the best experience is on Glass.
32:30 And we’re building up a lot of collective knowledge about
32:33 these best practices.
32:37 And even though it’s early, some of these Glassware
32:40 already have the one out there.
32:42 And I’m going to talk about some of those.
32:45 You know about some of the Google products that are
32:49 already available on Glass, like Google+ and Gmail and
32:52 Google Now.
32:55 These are awesome experiences on Glass, and we’ve added to
32:58 those with some of our friends.
32:59 We also know that “The New York Times” and Path are
33:03 available on Glass.
33:06 There’s a few more folks that we’ve been working with to
33:09 build this early Glassware, these V1s that people are able
33:11 to use on Glass.
33:12 I’d just like to mention a few of those that are going to be
33:15 available to Glass users today.
33:21 I like that slide.
33:22 It’s OK.
33:23 You can applaud.
33:24 No?
33:31 TIMOTHY JORDAN: So this has been a lot of fun, because
33:33 we’ve gotten to work with a lot of really cool people
33:36 innovating in this space and building these really amazing
33:40 Glass experience for users.
33:42 Now it’s still early, but some of these experiences on Glass
33:46 really illustrate some excellent paradigms.
33:48 And I’d like to call out just a few of those and talk about
33:51 the cool stuff that they’re doing.
33:56 First off, Google+.
34:01 There’s a lot to Google+ on Glass.
34:03 There’s a lot that you can do with Google+.
34:04 You can share pictures and video.
34:06 You can get notifications.
34:08 You can comment on posts.
34:09 Or my favorite, you can start or receive Hangout on Glass.
34:15 If you haven’t tried it, it’s really fun.
34:17 You can join that Hangout, and people see what you’re seeing
34:20 wherever you are in the world.
34:23 I’d like to take a look at one feature in particular.
34:27 This is getting a Google+ notification.
34:31 Here my friend and colleague, Ossama, has plus mentioned me
34:34 yesterday in a Google+ post.
34:35 And I get this notification on Glass.
34:43 If I tap on that notification, I see two items.
34:45 One, I can comment or I can plus 1.
34:47 Plus 1 is great, because I can just kind of do that on the
34:49 go, and that’s it.
34:50 Or maybe I want to add a comment to the post, in which
34:52 case I tap on Comment and I just speak out loud.
34:56 And that will appear on the Google+ post on the web, and
35:03 the item in my Timeline gets updated.
35:08 And this makes sense, because Google+ owns that Timeline
35:11 item, and they can keep the comments as sort
35:14 of a threaded bundle.
35:16 Now I see the post Ossama made.
35:18 I tap inside there, and I can swipe through the comments.
35:21 And as other people add comments, either through Glass
35:24 or on the web or on mobile, that item
35:28 keeps getting updated.
35:29 And we have that conversation.
35:40 This is a lot of fun.
35:41 And one of the things that I really like Google+ is that
35:44 since we’ve got this concept of circles and the plus
35:46 mentioning, I end up getting the posts that I care about
35:49 with people that I want to communicate with, whether I’m
35:52 on the go or not.
35:54 And being able to do that on Glass is a really fun
35:55 experience.
35:58 The next one, CNN.
36:01 CNN and us have been working together on this really cool
36:04 experience that you may have checked out in the Sandbox.
36:07 They’re out they’re showing you.
36:09 And of course, you’ll be able to use it later today.
36:13 The first thing that you’ll notice when you sign up for
36:15 the CNN Glassware is this Settings page.
36:21 I love this Settings page.
36:23 They’re doing some really cool things here.
36:25 First off, they’re letting me send alerts between two times.
36:29 I just want to get updates from CNN during working hours,
36:32 or working hours plus a few in the evening.
36:35 And I can set that right here.
36:39 Also, I can select which topics I want to get on Glass,
36:43 which ones are interesting to me.
36:44 And I get an immediate indication of approximately
36:47 how many updates I’m going to get per day.
36:49 That’s super valuable on Glass.
36:51 Because maybe I just want to dip my toes in the water with
36:54 some sports and politics alerts.
36:56 Or maybe I want to go whole hog and get the top stories
36:58 throughout the day.
37:01 Now once I start getting items from CNN, they look like this.
37:05 They’re a bundle that represents a story.
37:09 I tap into that bundle, and the first item is some text
37:14 for that story that I can have read aloud.
37:16 I swipe forward, and I have a short video.
37:20 This was a really cool one about a taqueria in Florida
37:23 that serves lion tacos.
37:24 I don’t know how I feel about that, but I thought it was
37:27 interesting.
37:32 Now what’s neat about this is that when you put on Glass,
37:35 the first thing that you notice is how
37:37 brilliant the screen is.
37:40 You can see images in really high fidelity, and videos look
37:43 really cool on Glass.
37:45 And having CNN send me these short video from everywhere in
37:49 the world throughout the day, and I can look at them
37:51 whenever I want, is really a unique experience.
37:57 Twitter.
37:59 Twitter and Glass, they just work so well together.
38:04 There’s a bunch of stuff that you can do
38:05 with the Twitter Glassware.
38:06 You can get tweets from plus mentions.
38:11 You get the tweets that you have mobile notifications
38:15 turned on for.
38:17 So if I have mobile notifications turned on for my
38:19 friend, Sydney, as he tweets, I get those on Glass.
38:23 You get direct messages, and you can
38:25 respond to those messages.
38:28 And you can share a picture from
38:29 Glass directly to Twitter.
38:31 And it’ll post it as a photo tweet.
38:35 A tweet on Glass looks a bit like this.
38:37 As you know, our friends from NASA just returned to Earth.
38:42 And it was really fun watching all of their updates getting
38:45 retweeted by NASA astronauts and getting that on Glass
38:48 throughout the day.
38:49 Because they’re updating about their return and their tests
38:52 and seeing their family.
38:55 And if I want, I can reply to these tweets, I can retweet,
38:59 and I can favorite right from Glass.
39:03 Super simple.
39:04 And because Twitter is that short message model, it just
39:07 makes a lot of sense on Glass.
39:10 Another thing that I really love about the Twitter
39:12 Glassware is this direct messaging capability.
39:15 Now here Alain sent me a DM asking if I was ready for the
39:19 afters hour party.
39:23 To which I replied, most certainly.
39:24 Because of course I was.
39:25 It was awesome, right?
39:27 Yeah.
39:27 It was a good party.
39:29 I think that might be the best I/O party yet.
39:32 Anyway, I hit Reply.
39:34 I saved that message.
39:36 And that gets added to the thread on Glass.
39:40 Remember, I talked about these bundles and threaded bundles?
39:42 All Twitter had to do was insert one more item, set the
39:46 bundle ID for that bundle– which is any arbitrary string
39:51 it decides.
39:51 Maybe it’s an internal representation of this
39:54 conversation–
39:56 and that bundle grows.
39:58 And it keeps growing as we reply back and
40:01 forth to each other.
40:04 It’s pretty neat, huh?
40:06 All right.
40:07 Let’s talk about Evernote.
40:14 Evernote, as you know, is great for taking notes,
40:17 capturing ideas and experiences, and collaborating
40:20 with your friends.
40:23 One of the things that I do, one of my patterns with
40:26 Evernote, is I’ll take notes and then I’ll
40:28 reference those notes.
40:29 I do shopping lists all the time on Evernote, my common
40:33 shopping list every week.
40:34 And then I add items, remove items.
40:35 And then I’m in the store, and I have my phone out, and I’m
40:38 looking at that shopping list.
40:39 And it’s much cooler having that experience on Glass.
40:42 So here’s my shopping list for Google I/O. I’m not sure that
40:46 I got that last item, but I did get the extra socks.
40:52 Now on this Evernote note, if I tap on that Share arrow, I
40:56 get all the places I can share this note to.
41:00 And of course, I’m going to tap on Glass to send
41:03 this note to Glass.
41:06 Now Evernote, since this is primarily text, they do that
41:09 thing where they insert a Timeline item that’s text, and
41:12 it autopaginates.
41:14 In this case, it’s the shopping list.
41:16 It’s simple, and it’s easy.
41:17 I can see it on Glass, so I can go through the store and
41:19 buy these extra socks or unhealthy energy drinks
41:25 without having to go back and forth to my phone.
41:27 It’s a really cool experience.
41:33 All right.
41:34 Let’s talk about Facebook.
41:36 Facebook for Glass lets you share your photos on Facebook.
41:40 And you can choose who you want to share with, and you
41:43 can say something to add a description.
41:45 In this case, we’ve got this photo that
41:48 I’ve taken on Glass.
41:51 Now I’m going to tap that image, and I get options for
41:55 Share and Delete.
41:58 This is just, at this point, a picture on Glass.
42:01 When I tap on Share, I get my whole
42:03 list of sharing contacts.
42:05 And one of them, once I’ve set up the Facebook Glassware, is
42:08 going to be much friends on Facebook.
42:09 Now you can also share with public or with just yourself.
42:20 I’m going to tap on this sharing contact.
42:23 And what Glass does is it creates a new image on my
42:26 Glass Timeline.
42:28 This time it’s owned by the Facebook Glassware.
42:31 They get a notification I tapped on that Share target.
42:35 And what Facebook is doing is it’s going back to that
42:37 Timeline item and adding a new menu item, Add Description.
42:41 So this is immediately posted to my Facebook Timeline, but I
42:44 can tap here and add a description, say these are
42:46 white stargazers.
42:49 And then Facebook will update that Timeline item to also
42:53 include that caption, that description.
42:57 And it updates the post on Facebook as well.
43:04 Now that picture is going to show up on Facebook, so my
43:06 Facebook friends can see it when they visit my profile.
43:13 This pattern here is the ability to share a photo,
43:17 delete it right away if it’s an oops moment.
43:19 But then add a description is really key.
43:22 Because I can do all those things with Glass and sort of
43:25 just having that quick experience or add a little bit
43:27 more information to it.
43:29 I really recommend this pattern.
43:31 All right.
43:32 Let’s talk about “Elle.” Now I am not the target consumer for
43:36 “Elle.” But what they’re doing with Glassware I think is just
43:43 really cool.
43:44 They also have this great Settings page.
43:47 And they’re a really important, maybe the number
43:51 one, fashion magazine out there in the world, part of
43:54 the Hearst collection of magazines.
43:57 And it’s a neat experience on Glass.
44:00 You can select on the Settings page for all these different
44:04 topics, much like you do on CNN.
44:07 But “Elle” does something else that’s
44:09 really cool in the moment.
44:11 As I get these items on Glass throughout the day–
44:16 and this is a bundle with multiple pages–
44:22 and I tap on any one of those pages and I get this menu, I
44:26 can have this read aloud, I can share it, or right there
44:30 in the middle I can add to my reading list.
44:32 Now I love this flow for three reasons.
44:37 First off, I think it’s cool for the user.
44:40 As I’m reading “Elle” or other articles on Glass, a lot of
44:45 the time having that headline or that little bit of
44:47 information is exactly what I wanted.
44:49 I’m good.
44:50 But sometimes it’s like, oh, I want to read
44:52 more about this later.
44:54 Or maybe I want to bring it up on my computer at work on a
44:57 big screen and share it with my friends.
45:00 How do I do that?
45:01 Well, I tap on Reading List, and “Elle” adds this to the
45:05 Reading List on that Settings page I showed you, right at
45:07 the bottom.
45:08 And it’s all of the links that I’ve saved throughout my day.
45:11 So it’s cool for the user.
45:14 It also helps me, as a user, spend more time with “Elle.”
45:17 because now I’m also on their web product.
45:20 And finally, it helps “Elle” know what are some of the
45:23 articles that I want to spend more time with later, not just
45:26 the updates throughout the day.
45:28 So it’s really good for the user, and I think it’s really
45:30 good for the brand.
45:34 All right.
45:34 I want to do one more example.
45:36 And I love this story.
45:38 Ice Breaker is here at Google I/O. Whereas this isn’t
45:41 released on MyGlass website, you can go to this website,
45:45 and you can install it while you’re at I/O and play with
45:47 each other.
45:48 This is a game.
45:49 A lot of what we’ve talked about so far is very
45:51 productive, and sharing with friends, and
45:54 it’s a lot of fun.
45:55 But also, I want to have a whimsical
45:57 experience with Glass.
45:59 Now these three guys got together at one of our Glass
46:03 Foundry events, met each other, built some awesome
46:06 Glassware, and won first prize.
46:08 And afterwards, we were hanging out, and we came up
46:10 with this idea of Ice Breaker.
46:13 And they built it for Google I/O.
46:15 This is what you do.
46:16 You land on their page, the, and it’s going
46:20 to walk you through the whole flow.
46:21 But let me just touch on what happens.
46:25 First off, they send a welcome card.
46:26 And this is something “Elle” does as well
46:28 that I really like.
46:28 When you sign up for the Glassware, it immediately
46:30 inserts a card into your Timeline, so you know it all
46:33 worked, and the user gets that kind of warm, fuzzy feeling,
46:35 like now I’m signed up for Ice Breaker.
46:38 And it tells you a little bit about what’s
46:39 going to happen next.
46:41 As Ice Breaker gets location updates for where you are,
46:44 it’ll find somebody else also playing Ice Breaker and sends
46:49 you a card with their photo and their name and the
46:53 encouragement to go meet them and have a conversation, or
46:56 break the ice.
46:57 You can get directions to this person, you can pin or unpin
47:00 this card, and you can also give up if
47:03 you can’t find them.
47:05 Now let’s talk a little bit about those last two items.
47:08 First, the pinning, what this does is when I pin a card,
47:12 it’s a System Menu item.
47:14 It takes that card and puts it on the
47:15 left side of the Timeline.
47:17 That’s the space reserved for things going on right now.
47:20 Google Now is over there.
47:22 You’ve got your weather card, maybe some stocks that you’re
47:24 following, or other third party
47:27 Glassware that you’ve pinned.
47:29 In this case, I’m looking for Jonathan.
47:31 I want to make this new friend, so I’m going to keep
47:34 it pinned to the left side of me Timeline so I can look back
47:36 and like, OK, have I found him yet?
47:38 It’s like a fun person scavenger hunt.
47:42 The third option there is to give up.
47:44 Glass is a very now device.
47:46 Remember that?
47:47 So in the patterns of doing something with Glassware, like
47:51 breaking the ice and finding people to do that, what
47:54 happens if I can’t find Jonathan?
47:56 And in fact, Ice Breaker knows, since it’s getting
47:59 location updates, if we get too far away from each other,
48:02 it’ll send me a new person still at the conference that I
48:04 can find and make new friends with.
48:07 It’s really cool, because it’s in the moment, and it matters
48:09 to me right now.
48:12 Now I find Jonathan, and we have a conversation.
48:16 We get to know each other, and I take his picture, and I
48:19 share it with Ice Breaker.
48:21 He then gets a notification being like, did
48:23 Timothy really find you?
48:24 And did you have a good conversation?
48:26 If the answer is yes, then I get more points.
48:29 And I keep looking to make new friends who have Glass here at
48:32 Google I/O. Again, I really recommend you try this.
48:35 It’s a lot of fun.
48:43 All right.
48:43 Let’s talk a little bit about next steps, shall we?
48:50 We’ve talked about developing for Glass.
48:52 That was this session.
48:53 There’s three more sessions today, details about the
48:56 Mirror API, building Glass services right away.
49:00 “Voiding Your Warranty.” If you want to go off-roading
49:02 with Glass, cut loose, and do some crazy stuff–
49:07 or do some not-so-crazy stuff, they’ll talk about that too–
49:11 you can go to the “Void Your Warranty” session.
49:13 Now when I mentioned the GDK, that’s something you’re like,
49:16 oh, that’s what I really need for my service, which might
49:18 happen for a few of you, that’s a good place to go and
49:22 get some more material to start dreaming up those
49:24 experiences and give us some feedback about that GDK.
49:28 The Fireside Chat with the Glass team.
49:32 That’s at the end of the day.
49:33 That’s going to be a conversation.
49:34 I’ll answer just a couple questions here today.
49:37 But some of the bigger questions, I might be like,
49:39 come to the Fireside Chat.
49:41 And of course, please do bring your big questions there.
49:46 We also have a Sandbox out here on the
49:48 floor at Moscone Center.
49:50 So if you are live with us here at Google I/O, please
49:53 come by and say hi.
49:54 And let’s have a conversation about this stuff.
49:56 And visit some of our partners who are showing off their
49:59 Glassware there in the Sandbox.
50:02 Now we have some resources as well.
50:04 If you have questions, go to Stack Overflow.
50:06 There’s a Glass tag.
50:08 If you want to download some code and get started with some
50:10 starter projects, GitHub is the place to go.
50:13 And of course, we have an issue tracker for any bugs
50:15 that you might find.
50:16 Remember, we’re in the developer preview period.
50:19 So these conversations that you have on these resources
50:22 are really helping us get this API ready for the real world.
50:26 And the Mirror API is if you want to develop Glass services
50:30 that people are going to use and that you’ll be able to
50:32 distribute to users soon, then that’s where you start.
50:38 And if you want to get in depth with some more
50:40 conversations about Glass, we have a general community.
50:42 For those of you that do have Glass, you have access to this
50:45 site,
50:51 Thank you so much.
51:02 TIMOTHY JORDAN: All right.
51:03 So we have about seven minutes for just
51:05 a handful of questions.
51:07 Please head over to the microphones.
51:09 There’s one over here as well.
51:12 Please know that if you ask about feature requests, I
51:16 definitely want to hear them.
51:17 That’s what this explorer period is all about.
51:20 However, I’m not going to be able to comment on any future
51:22 releases or plans.
51:24 Yes.
51:25 AUDIENCE: Hi.
51:25 Know John Blossom, Shore Communications.
51:29 On the API where you’re showing the ability for
51:33 individual google glass apps to have command cards, are those
51:36 commands specific to the app or specific to the content?
51:39 Because it doesn’t look as if we really have the ability to
51:44 do the equivalent of tapping on hyperlinks in that HTML.
51:48 So is anybody thinking about how do you disambiguate
51:53 between buying this and buying that, say?
51:56 TIMOTHY JORDAN: That’s a great question.
51:57 So I think the question is really about the Menu options
52:00 on the Timeline item.
52:02 So the way you do that is that when you insert the Timeline
52:04 item, part of that JSON in that structure is all the Menu
52:08 items that you want to appear with that Timeline card
52:10 enumerated.
52:11 So it’s content-specific?
52:12 TIMOTHY JORDAN: It’s content-specific.
52:14 But you can build this however you want in your app.
52:16 So if you have a template of menu items for every certain
52:18 kind of Timeline item that you insert, and you just slap that
52:22 into your JSON every time, you can do that.
52:23 It’s really under the control of the Glass service.
52:26 And those can be the System Menu items, like Reply or Read
52:29 Aloud, or they can be any custom items that have
52:32 whatever name you choose.
52:33 TIMOTHY JORDAN: So let’s say you want to include a
52:36 hyperlink and you want to give the user the option to save
52:38 that for later, for when they’re at their computer, you
52:41 can add that as a Menu item.
52:42 AUDIENCE: Cool.
52:43 And will the GDK, as it’s conceived today, include
52:46 signals from the headset?
52:50 Can you read from the headset things besides what are on the
52:53 command cards?
52:53 TIMOTHY JORDAN: So there will be.
52:55 I don’t have any details about exactly what.
52:56 But there will be access to some of the hardware features
52:59 of Glass exposed in the GDK.
53:01 Now the GDK itself–
53:03 I’ll add a little bit more information for those of you
53:05 that didn’t rush off to another session–
53:08 is essentially developing for Android with an extra library.
53:13 So if you’ve already use Android and you know those
53:16 paradigms really well, you’ll be able to download additional
53:19 code to target against that’ll give you more functionality
53:23 specific to Glass.
53:24 AUDIENCE: Cool.
53:25 Thank you.
53:25 TIMOTHY JORDAN: You’re welcome.
53:27 Question over here.
53:27 And then we’re just going to go back and forth.
53:29 AUDIENCE: Hi.
53:30 Steve Ogden from Starz.
53:31 TIMOTHY JORDAN: Hi, Steve.
53:32 AUDIENCE: Wondering, are you adding any new sensors?
53:35 And also, could you go over the existing
53:37 sensors within Glass?
53:40 TIMOTHY JORDAN: So I can tell you what the user
53:42 has access to today.
53:44 There is sort of an accelerometer.
53:47 They know if you look up to turn on
53:48 Glass, like I just did.
53:51 There’s a camera, and there’s a location built in to the
53:54 paradigm as well.
53:56 When it comes to the GDK, the best thing to do is if there’s
54:00 a specific sensor that you want, make sure that you let
54:03 us know on Stack Overflow.
54:04 Here’s my idea.
54:05 I want to make sure I have access to this.
54:07 And then we’ll work on that.
54:09 Thank you.
54:10 TIMOTHY JORDAN: We’ll do our best.
54:10 Thank you.
54:12 AUDIENCE: Hi, Tim.
54:12 Antonio [INAUDIBLE]
54:13 from [INAUDIBLE]
54:14 Apps.
54:16 AUDIENCE: Hi there.
54:17 You were my target for Ice Breaker, by the way.
54:19 So I need to take a picture of you right now so I
54:22 can send it to them.
54:23 Awesome.
54:24 So two quick questions.
54:25 You insisted that the image resolution should be 640/360,
54:30 but everything we send to Glass goes
54:32 through Google, right?
54:33 TIMOTHY JORDAN: Mm hmm.
54:34 AUDIENCE: So is Google doing some processing of the images,
54:36 like if we send something that is too big, you would reduce
54:40 it for us so that it gets the right resolution for the user?
54:43 TIMOTHY JORDAN: There’s a lot of optimization that we do
54:46 before the user sees something on Glass.
54:48 And I’m sure there’s more that we could do over time.
54:50 But the reason I say you should set the resolution to
54:53 full screen is that that gives you the most control over
54:55 resizing and how it’s going to look when it’s full screen.
54:57 And that’s always better.
54:59 The second question is you showed a few apps, like
55:02 Facebook, Twitter, Path, “New York Times”.
55:05 Are you going to have an app store or a place where you can
55:08 actually publish your app?
55:09 AUDIENCE: As an app developer, I’m interested in publishing
55:11 my apps there.
55:12 TIMOTHY JORDAN: That’s a really great question.
55:15 As everybody here knows, because we’re all developers,
55:18 a healthy ecosystem involves some story around discovery.
55:22 And right now, if the user wants to add one of these
55:25 Glassware or Glass services, they go to MyGlass, they’ve
55:28 got cards, and they can turn them on.
55:31 And we believe that that’s a great paradigm for showing
55:34 users how Glassware is there.
55:37 At the moment, we’re still in developer preview, so we’re
55:39 still working on the details about how that’s going to
55:41 evolve and how additional third-party Glassware is going
55:44 to get in there.
55:45 And those details will come.
55:46 But we’re definitely going to have something.
55:48 AUDIENCE: Cool.
55:48 Thanks.
55:50 AUDIENCE: Hi.
55:50 I’m Danny [INAUDIBLE].
55:51 I had a question about best practices.
55:54 I was speaking with CNN, and they mentioned that in their
55:57 Glassware app they were advised not to
55:59 use the Delete function.
56:00 And I was wondering, why would Google advise them not to use
56:04 that function?
56:04 Because you mentioned it.
56:05 TIMOTHY JORDAN: That’s a great question.
56:06 Yeah.
56:06 I talked about Delete and Dismiss.
56:08 Now in the case of sending data to the user that the
56:11 user’s going to look at and be like, hey, this is cool,
56:14 having them be able to delete them encourages sort of a user
56:17 paradigm of curating their Timeline.
56:20 Which doesn’t really make sense on Glass, because,
56:22 remember, there’s this single Timeline that
56:24 stretches into the past.
56:25 And since it’s such a now device, I’m going to be
56:28 looking at the recent few cards.
56:30 I’m not going to scroll to a week ago.
56:33 So why would I need to curate it?
56:35 AUDIENCE: Exactly.
56:36 OK.
56:36 Makes sense.
56:38 AUDIENCE: Hi.
56:38 I’m Lucas from [INAUDIBLE].
56:40 And you talked about you should test the Glass in our
56:45 apps as much as possible.
56:47 But how much earlier will get the other developers the Glass
56:50 before the customers will get them?
56:54 TIMOTHY JORDAN: So you’re asking, are we going to make
56:55 more Glass available before we’re selling to consumers?
56:58 I don’t know.
56:59 TIMOTHY JORDAN: Right now, we’ve just sort of finished
57:03 fulfilling and inviting people that have signed
57:05 up at I/O last year.
57:07 And we’re going on to the “If I Had Glass” winners.
57:10 That’s the next big thing.
57:11 What’s next?
57:12 I’m not sure.
57:13 I’m sure we’ll let you know.
57:14 A way that you can make sure we let you know is if you go
57:16 to, in there is a web form where you can
57:20 indicate your interest and say that you’re a developer.
57:22 Thanks.
57:23 TIMOTHY JORDAN: Thank you.
57:24 AUDIENCE: Hi.
57:25 I’m Sebastian from [INAUDIBLE].
57:27 I’m just wondering what features you’re going to allow
57:30 us in the GDK.
57:32 One of them that would be interesting is, are you going
57:36 to allow us to have access to the video stream so they we
57:38 can display information directly on what we are
57:41 seeing, something similar to layers on
57:44 Android, but for Glass?
57:48 TIMOTHY JORDAN: As I said before, I can’t comment on any
57:49 feature requests.
57:50 But I like hearing them.
57:52 I think right now the right time to think about this is
57:56 use the Mirror API.
57:59 Your dream for Glass, can you build that in the Mirror API?
58:02 And what that’s immediately going to tell you is, is this
58:05 going to be a simple and quick user experience that makes
58:08 sense on Glass?
58:09 And if it becomes really complicated really quick,
58:11 sometimes that might make sense for GDK, or maybe it
58:14 makes sense that it doesn’t work on Glass.
58:17 But please do go through that process of design thinking
58:20 about how this would work on Glass, and let
58:22 us know in the forums.
58:24 Thanks.
58:25 TIMOTHY JORDAN: Thank you.
58:25 And I think, with that, we’re just out of time.
58:29 Remember that we have the Sandbox area.
58:30 Please come up afterwards.
58:32 And let’s keep having this conversation.
58:34 Thank you so much.