An Introduction to Android Wear

An Introduction to Android Wear

name is Timothy Jordan. I’m a developer
advocate here at Google, and I’d like to give you a quick
introduction to Android Wear. Android Wear is a set of
APIs that extends the Android platform to a new
generation of wearables. Rich notifications can
appear on the wearable, with no modification to
the existing Android app. The developer can add just
a few more lines of code to extend the
wearable experience or go even deeper, by building
an app just for the wearable. Before we dive into the
details of the platform, let’s take a step back. What’s wrong with this picture? We spent some time looking
at technology usage and thought deeply
about the ways to help you stay more
connected to the digital world. But also more engaged with
what’s happening around you. Android Wear looks
to address this by showing you useful
information the moment you need it, and just in a glance. Let’s look at that in
a more technical way. This is your day
with your phone. Notice the length
of time it takes to pull out your phone
from your pocket, unlock it, navigate to what you
want, and then engage with it. There’s a hefty time
and attention cost, even for interactions that
should only require a moment. This is the same set of
interactions on a wearable. Notice the reduced
overhead per interaction. Now this is what we mean by
more present in the real world, and yet more connected
to the virtual world. What does this mean
for your development? Well, to start with,
and this is important, it’s a fundamentally different
user interaction model. And you can tell just by
looking at this device. It’s a fundamentally
different device from other mobile devices. To really nail the
user experience, you’ve got to
rethink it a little. When considering which
features of your service you’d like to make
available on the wrist, consider this question. What couldn’t we do on
the phone that we can now do on the wrist? What now becomes
possible with the user? And then focus on that. Also, you’ve got to try it. It may sound silly, but once
you get that emulator up and running, stand
up at your desk and pretend you’re
walking between meetings or across the street. Something to get yourself
in the situation, so you know what it feels like
to use the service on the go. Here’s an example
of what we mean by a very basic but
essential difference. This is the app
experience on your phone. Now we’ve trained users to
collect these shiny objects, and then search
for them when they want to do something,
which works OK on a phone. But if we put these same shiny
objects on a wearable, well, it just doesn’t make sense. It would be the same
time consuming paradigm, but on a device
intended to reduce those parts of the interaction. It just doesn’t make sense. How do we get outside
of this paradigm? How do we get past
this grid of icons? This is the Android
Wear interface. It’s simple, glanceable, and
built around microinteractions. The interface is divided
into two primary behaviors. The user can talk
to the wearable. You can think of
these as actions. The user might say, OK Google,
and then any voice command is available to them. The wearable can
talk to the user. Now think of this
as a context stream. It’s sort of like
enhanced notifications that matter to the
user right now, because it’s the
right time or place. OK. Let’s talk about developing
with Android Wear. First, notifications. The notifications on
your phone can also be displayed on the wearable. And to get this done you
don’t have to do anything. It just works out of the box. Also, notifications that buzz or
sound on the companion device, such as your phone, will
also buzz on the wearable. Enhanced notifications will
also show up on the wearable. And again, to get
this done you still don’t have to do anything. It also already
works out of the box. There are a few things that you
can do with your notifications, specifically on the wearable. And these do require
a few lines of code. Stacks allow you to bundle
multiple notifications together. Think inbox style notifications. Pages. They give you the ability to
show more than one glanceable screen of information to the
user for a single notification. And yes, Pages can be
combined with Stacks. Replies. They allow you to add
actions to notifications that the user can
control with their voice, via open-ended text input
or through pre-defined text responses. If you want to have code
running on the wearable, you’re going to have
to build an app. The SDK for apps
isn’t available yet. But here’s a few
notes to get you started thinking about them. You can create custom card
layouts and run activities directly on wearables. You can send data and
actions between the phone and a wearable with
data replication APIs and remote procedure calls. You can gather sensor data
and display it in a real-time on Android wearables. And you can register
your app to handle Voice Actions, like OK
Google, take a note. And that’s the
Android Wear platform. Please check out more detail
on our excellent documentation, I’m Timothy Jordan, and
I’ll see you next time.

67 Replies to “An Introduction to Android Wear”

  1. Can't wait for this! Just fits everything in a smart watch I am looking for and more! I am currently using a Sony Smartwatch 2 which is great, but seems to lack what Android wear thrives in. Going to be good to see how this plays out in the long run 🙂

  2. I was on my iphone most of this video.. yaaawn, what does this have to do with being on an iphone though? It's two different things. I go on my iphone if i'm bored, and occasionally it will display a message that can be read with a glance, just as android wear wants to do, it doesn't take more than two seconds to respond to the notification (lets say its a messenger message). i understand how this is useful if you don't want a smartphone, but just want something with a calender, calculator, alarm, tools etc, but they're talking about it as if they are trying to replace a smartphone with it, which won't happen !!

  3. There are fundamental problem here….
    User interacts with google wear by Google voice.
    However, Google voice sucks….. Now what???

  4. Another public beta just like the Glass? I still see no point in having two devices instead of just a phone. If I decide to wear a watch I would get an Omega Seamaster or a Breitling. 

  5. The chart at 1:30 looked completely fictitious.. I like the way this sounds otherwise.. but i never have more than 2or3 cards on google now.. it tells me the temperature and how long to get to work.. how intuitive is the wearable really gonna be if thats all google now gives me?

  6. You can't allow regular Android apps on Android Wear. You just can't. You need specific apps made only for it.

  7. I'm sorry, but I really want an android wearable, but this video toned me off of it big time… Why would I want a second device after seeing this??? First off, the voice interaction only works well under certain conditions (we all know that). Secondly, they compared searching the web on your phone to searching on that tiny screen, and then showed notifications that don't fit on the screen…

  8. I'm sorry, but I really want an android wearable, but this video toned me off of it big time… Why would I want a second device after seeing this??? First off, the voice interaction only works well under certain conditions (we all know that). Secondly, they compared searching the web on your phone to searching on that tiny screen, and then showed notifications that don't fit on the screen…

  9. Omg this is most annoying video i ever saw. Like some MLM annoying idiot is trying to sell me kirby vacuum cleaner.

  10. Until the wearable is an independent unit, not relaying on the phone, maybe equipped with headphone, or ear piece I find it a hard sell.

  11. Those mock-ups are terrible though. Why is the hour so small, and why don't you put the date on the watchface by default? Using the temperature as a default 'notification' is silly.

  12. Please stop building this around voice commands, no one wants to speak with their watches in public. Of course the voice commands should be there, but also a fast way to use it with your fingers. I found that, to me, the most pratical use of this would be to select and change the music that i am listening to. But if i have to say "change the artist to Pantera" at middle of the bus that drives to work at 7am while everyone else is asleep, it would be nothing short than useless to me. 

  13. Smartwatch will change the view about timepiece… It's whole new world compare to simple digital watch.. For example with moto360 u can have endless watch face which can be like other luxury brand watches with very affordable price.. We don't need movement just great display..

  14. voice doesnt really work that well. you should consider having a keyboard like fleksy or minuum or a keyboard that works by twisting your hand. 

  15. I can't wait for the I/O Conference. Please Google, everybody knows you can do everything, SPEED UP THE TIME until June 25th !

  16. Yay! One more step towards becoming the "advanced" Human species as seen in the movie Wall-E 😀 ! 

  17. Do not get me wrong, i lik the UI. But think about one very simple thing. Would you check your watch often to see how many degrees is outside, or to check the time.
    Why on earth you have made the temperature /weather so hugre, and reduced the clock to almost invisible. It makes muuuuch more sence to be exactly the way around. Don't you think? 🙂

  18. Зачот, Тимоти! В 5 минут презентации уложил объем материала, который просто хороший презентер укладывает в 15. И при этом, умудрился не потерять в доходчивости и эмоциональности.

  19. Lol everything he said was premade by google to convince dumb consumers to buy this crap. Sorry google, apple has real tech as oppose to gimmicks so you can stick your paradigm and micro interactions up your ass.  

  20. Seems stupid, you can't download music on to it, no bluetooth for headphones (again, let us put some damn music on it), no internet, no apps (like calculators or translators etc), no photo storage, NO INTERNET (can't get over that, everything should have internet access in this era). However, the Moto360 is the most beautiful thing I have ever seen. Android wear ruins it though.

  21. Too much waffle. Just give the raw information without the giggling and sales pitch watering it down so I can just get to coding already.

Leave a Reply

Your email address will not be published. Required fields are marked *