How to develop Android apps quickly and efficiently under

Android Wear aims to provide users with the right amount of the right amount of information at the right time. In line with this theme, Google has released design principles to help developers focus their thinking about Android Wear apps. We will provide a brief overview of this, as well as examine what is necessary for app development in the Android Wear environment and how the available APIs can be utilized to help Android developers develop apps for the Android Wear platform.　　The Android Wear Platform Android Wear is an open operating system for wearable devices with a new user interface - a result of Google's understanding of how we use our phones and how we engage more with our environment. For example, data shows that we use our phones to check our messages on average about 150 times a day. Every time we do this, we risk getting lost inside other apps, often consuming a lot of unnecessary time in a task program, and sometimes even completely forgetting the most important information we're looking up.　　The first devices to make Android Wear hot were the Samsung Gear Live and the LG G Watch, both of which were announced at the Google I/O conference in June. Watches are the first choice target for Android Wear, and it's true: most people use watches every day. These so-called smartwatches usually need to be paired with an Android phone, and by working seamlessly with the latest Android phones, Google is allowing users to see the utility of the Android Wear platform.　　In fact, all you need to get started with Android Wear is the following: 1. an Android 4.3 device; 2. an Android Wear app from the Google Apps Marketplace; and 3. a paired Android phone device with an Android Wear device.　　That's right. With that done, most of the information on your phone can be viewed on your wearable device. Not only can you view this information on your watch, but you can also interact with it, delete it, and more. What this shows is that it doesn't take any effort or very little time to get Android apps and paired devices running - Android phone users can do this.　　It's important to note that the phone and the wearable device are connected via Bluetooth. Wearables can't currently access the network independently, so they need to be connected through the phone.　　As flexible as Android Wear is, it's most focused on the watch category at the moment.　　At the beginning of September, Motorola released the much-anticipated smartwatch, the Moto 360. it's powered by Android Wear. The Moto 360 received great acclaim due to its beautiful design, and its $250 price tag has been well received by consumers. Other developers, including Asus, have already announced plans related to releasing Android Wear smartwatches too.　　Usage Modes The two main ways to interact with an Android Wear device are "Suggestions" and "Demands."　　"Suggestions, as the name suggests, are timely and useful information pushed to Android Wear devices in the form of notifications. The user interface sets this up as a card, as shown below.　　It's worth noting that the Wear app recognizes contextual context, so only in-text information is pushed. These notifications are timely, brief, and have minimal interaction with the user.　　As for the "on demand" usage model, the user signals the wearable device by voice and it responds with a message. The device contains a microphone that allows the user to invoke a standard set of actions by saying "OK, Google" or tapping on the home screen. The user interface prompts the user to say what action they want to perform. Standard actions include "take notes", "make a call" and "send a message". You can register standard commands with the application or customize the prompt text.　　Design Philosophy Now that we understand the basic usage patterns of Android Wear, it's time to look at the user interface and design guidelines.　　As you can see below, much of the information presented to the user is in the form of cards.　　Take note of the different parts of the card. Currently Android Wear app notifications will appear in the standard format above. But we're talking about a minimal amount of information that's easy to read and contextually relevant, and you'll need to spend some time thinking about when to add text notifications and the text that needs to be displayed.　　Notifications can be displayed on single or multiple cards. If multiple cards are used, users will need to swipe the page from left to right to view them.　　With an overlay, you can even view multiple notifications in a single card, as shown below.　　There are four key points to keep in mind when designing the Android Wear user experience that every Google Wear Design visual creative section, Android Wear apps should do: 1. Auto-launching: Users should not need to install apps on their Wear device separately, a Wear device is not a phone.Android Wear The app should be able to recognize time, place and activity and push relevant cards accordingly.　　2. easy to read: because users wear the device on their wrist, reading notifications should be as easy as checking the time on a traditional watch. Remember to pay special attention to the title: the shorter the better - you can see the main points at a glance.　　3. Effective use of Suggest and Demand modes: According to the Android Wear developer's page, "Android Wear is like a great personal assistant. It only stops when you don't need it at all, and it's always on hand to provide you with answers. "To provide this experience, developers should consider when and how to use the Suggest and Demand modes.　　4. Zero-Low Interaction with Users: Developing apps and programs is a matter of remembering that wearable devices are particularly small. Apps must be easy for the user to interact with, i.e. using sounds or simple swipe or tap gestures.　　The Android Wear design team has done a great deal of work documenting how to effectively integrate design concepts when expanding within existing Android Wear apps. (Check out the Android Wear design section.)