Android Wear-Design Principles for Android Wear (Design Principles)

 

 

Focus on not stopping the user and all else will follow (Focus on not planning the user and keeping everything going)

The watch is a perfect device shape that allows you to use it when doing other things, such as cooking, eating, walking, running, and even talking. If your application causes users to stop what they are doing, it is a good opportunity to consider how to use the principles in this section to upgrade the program.

Try:

Calculate the time consumption of a typical Wear application. If it takes more than 5 seconds, you should consider making your applications more concentrated. Let's also try to see how your applications affect your conscious thinking and eye focus in your conversation with others.

Each operation on the Left takes 5 seconds.

 

Design for big gestures (using big gesture Design)

When you slide through images on your phone, you have a large display area and you do not need to perform this operation accurately. This is also the best way to interact with wearable devices. Your users may use your applications in various situations, and recently frequently used entries may be displayed on the desktop.

Try:

Use your applications in various daily situations, such as walking, eating, talking to others, or ordering coffee. If you have to slow down or interrupt the conversation to perform precise operations when you have to walk, you should consider how to increase the scope of your gestures.

Use less and greater touch targets

 

Think about stream cards first (first time considering the information flow card)

The best experience on Wearable devices is that the corresponding content is displayed as needed. You can specify the time to display your card based on the trigger time on the sensor or the cloud. However, you can rely on voice or touch operations when devices cannot predict that users are in need of your applications.

Try:

Make a list to list the situations where all users may need your applications. What do these situations have in common? Is it the same geographic location? What is the same time in each day? Or some physical actions? You may list different situations-this is a good thing, because it means you can specify specific cards for these situations. Remember, if users think these cards are irrelevant, they will always have the opportunity to set your information flow card to the Do-not-Disturb Mode.

 

Do one thing, really fast (every task is fast)

Although the user may only use your application for several seconds each time, they may use your application many times each day. A long information flow card should carry only a small amount of information, and provide only a small number of operation buttons when the user slides.

Try:

How much information is needed in your design? Is every piece of information necessary, or can you break down some pieces of information into another card? If you are designing a card, don't forget you can include multiple pages in one card.

 

Design for the corner of the eye (designed for the remaining light of the eyes)

The longer the user needs to watch your application, the more serious it is that you have left the user away from the real world. Consider how to enhance the scalability of your applications so that users can get enough information from your applications and quickly return to what they are doing.

Try the following:

When your watch is showing your app, try to focus on your finger joint and use your remaining light to view your app. Can you feel what the device is running? Can you tell which application it comes from? Does the above background image help to express the information? Does it use images or different images and colors?

 

Don't be a constant shoulder tapper (do not change to a continuous vibrator)

The watch will stick to the user's skin for a long time. Based on this intimacy, the number of beeps you set on your watch should be less than the number you set on your phone.

Try:

When you are talking, imagine someone is setting your shoulders and interrupting you with messages pushed by your application. If the pushed message has no reason to interrupt the conversation, you should not interrupt the conversation.