Since the release of Android 5.0 last year, it has been focusing on wearables. This year has been in the weigh how to Amoy a Moto 360, but considering the iwatch released in April this year, estimated that the existing Android wearable brand, there will certainly be a lot of big changes in the function, now buy, estimated soon will be outdated too much, So I decided to start Moto 360 after the new Google I/O conference.
Although there is no hardware, this does not affect the foresight of the software. So after discovering an article about the development of Android Wear, it is very exciting, so I find time to translate it into a blog, readers.
Good, not much nonsense, the following is the original blog translation content, the original link is: Original
Android Wear has recently made many updates and improvements, and it's time to share the latest overview of the Wear platform. Of course, we haven't finished-more things will come-but today is the time to start or continue to develop the groundbreaking Android Wear user experience.
The Android wear platform emphasizes depth and flexibility. Based on this, it allows developers to use familiar APIs to create usable, programmable, and imaginative applications that can run directly on the watch. In the spirit of Android open source, you have the freedom to continually improve the user experience, including the creation of custom dials. You have three main building experiences: apps, custom dials, and notifications.
Application
Applications built for Android Wear can be run directly on the watch, and can do almost anything a mobile phone can do, from steps to waiting for entertainment. Some activities do not even need to be connected to a mobile phone, such as fitness and music applications. There are libraries that can help you move data between your phone and wearable devices, as well as create special effects and adaptable UIs. Here is a list of some of the great features you can access:
Feature |
Documentation |
Full screens activities with touch events |
Creating Custom UIs for Wear Devices |
Notifications and custom Actions |
UI Patterns for Android Wear |
Custom Watch Faces |
Creating Watch Faces |
Layouts for round and square devices |
Creating Custom UIs for Wear Devices |
Opengl |
Displaying Graphics with OpenGL ES |
Sensors
- Accelerometer
- Gyroscope
- Compass
- Barometer
- Heart Rate sensor
|
Sensormanager |
Haptics |
Vibrator |
Microphone |
Audiorecord |
Voice actions |
Adding Voice Capabilities |
Gps |
Detecting location on Android Wear |
Offline Storing of Data/music |
Transferring Assets |
Media playback controls |
Mediasession,mediacontroller |
Framework based on Android 5.0 API 21 |
Android 5.0 APIs |
Standalone or synchronized Apps |
Sending and Syncing Data |
Dial
The ability to create custom dials gives you direct access to the most prominent UI elements on the user's most personal device. The Wear API is simple enough to quickly build the dial, flexible enough to allow personalization. Again, given the depth and flexibility of the Android platform, you can create something beautiful and unique for the user.
The development journey begins with the simplicity of bringing the design to the wrist. The OnDraw method is at the heart of the Dial API, allowing you to draw any design you can imagine onto a canvas, with enough frame rates to play smooth animations. This restores the full fidelity when the watch is in interactive mode.
Also sometimes, when the watch is in outdoor mode, you can draw a more cautious version of the dial. It is also possible to organize the system UI appropriately for the design by setting other preferences. Once these basics are covered, the only thing that can limit you is your imagination! Plus the moon phase, current weather, or fitness stats, you'll go further with the hundred-foot head. Watch manufacturers refer to these items as "jumbled, confusion or complications" (complications)--but with Android these are hardly complicated (complicated). Once you have the data, you can draw it on the canvas at any time.
Notice
Of course, Android wear notifications are the easiest way to turn on the world of wearable devices. If you already have an Android app with notifications (notifications already working on wear), if you've enhanced notifications through action, this will be better and already working automatically. If you add wear-specific features such as stack, page, and voice reply to make the notification experience richer on your wrist, your app will go a step further.
The user experience you build for wear will take full advantage of the power and flexibility of the Android platform. This will be easy to start, and it's likely to create a truly groundbreaking UI for the user. By putting the three together, we will be able to create a user experience ecosystem that will be as diverse as the watch it runs and the person who wears it.
[Translate] build an Android Wear app with depth and flexibility