Smartwatch App Design Guidelines & Antipatterns

Creation Process

The process involves: investigation of wearables, smartwatches and existing guidelines; the use and exploration of the apps on a smartwatch device; development of guidelines, antipatterns and recommendations for smartwatch app design; design of a mutable brand and exposure through this website.

12 Months

The complete process took a full year

The complete process took a full year in which we devised guidelines and antipatterns based on the experience and analysis done for an Android Wear OS device during a period of over 8 months. for developed the brand Zuri to help us expose

Creative Games

Used design games as a creative impulse

Design games such as a Design Slam where in short time spans, great amount of information is places on the table, discussed and processed.

Evolutionary

Changes happen every second. Let's be ready!

[Should be ready to grow, change, add and migrate.]

Adaptation

Find ourselves in others.

The principles for each guideline were matched with existing heuristics, guidelines or recommendations from Nielsen, Weinschenk and Barker, Maeda, Powels and ISO9142.

Personalization
Empower the user and personalize
Reveal relevant data to the user

Avoid showing everything, think about notifying the user with the right amount of information. Don’t saturate the user.Use user’s history to show information that the user likes and might be useful.

  • Dialog Principles – ISO 9241 Suitability for individualization
  • Susan Weinschenk Fulfillment
  • Susan Weinschenk Cultural Propriety
Learn from the user: Ask and anticipate the user’s needs

Don’t be afraid to ask the user about what he likes and anticipate without imposing decisions. Let him tell you if he didn’t like something.

  • Dialog Principles – ISO 9241 Suitability for individualization
  • Susan Weinschenk Interpretation
  • Susan Weinschenk Flexibility
Allow for customization by the user

Give a range of options for the user to choose from and create their own experience according to their needs and likes. Sometimes show him things a bit out of the box, so he can evolve and find new things we can enjoy.

  • Susan Weinschenk User Control
  • Susan Weinschenk Flexibility
Empathy
Think about their feelings and reactions
Think about the users’ reactions and what they might feel

Make emphatic inferences about users and their possible reactions upon proposed functionalities.

  • Susan Weinschenk Human Limitations
  • Susan Weinschenk Precision
Respect user’s privacy

Be Trustworthy, Earn Respect and Build Confidence.

Research to achieve a better empathy response

They are many good techniques promoted in user centered methodologies such as: focus groups, ethnography, questionnaires and user tests.

  • Susan Weinschenk Accommodation
Time and Moment
Seek for the perfect moment
Context is King

Content is relevant to the point where it is transmitted in the right context; taking into consideration cultural, geographical and demographical aspects of the user.

  • Susan Weinschenk Modal Integrity
  • Laws of Simplicity Law 6: Context
  • Gerhardt-Powals Use names that are conceptually related to function
Right Timing

To effectively engage with the users determine a span of interaction or message appropriate for the time being. Doing so in the right context creates a window of opportunity develop a ’moment’ (or ’micromoment’) for the user.

  • Laws of Simplicity Time
  • Gerhardt-Powals Include in the displays only the information needed by the user at a given time.
Glanceable
Design for fast viewing
Less is faster and easier to absorb

Show the least amount of content that's able to transmit a singular o simple message effectively. Therefore, by reducing distractions and imprinting clarity, the time needed to understand and process the information or data is minimized.

  • Nielsen Match between system and the real world
  • Gerhardt-Powals Fuse data
  • Laws of Simplicity Reduce
  • Laws of Simplicity Key 3: Power
  • Susan Weinschenk Simplicity
  • Susan Weinschenk Suitable Tempo
  • Gerhardt-Powals Reduce uncertainty
Keep a clear user interface

Keep user interfaces uncluttered, minimalistic, aesthetic and well organized.

  • Nielsen Aesthetic and minimalist design
  • Laws of Simplicity Organize
  • Susan Weinschenk Aesthetic Integrity
Respect the Hierarchy

Use color, size, type and spacing to elaborate a structure and hierarchy for which elements are in the most straightforward manner with the appropriate relevance.

  • Gerhardt-Powals Provide multiple coding of data when appropriate
  • Gerhardt-Powals Group data in consistently meaningful ways to decrease search time
Provide visual feedback

Current state and responses should be effectively communicated to the user through obvious and clear visual cues. This might include elements such as: affordances, icons, color, size and proximity. As well as transitions, such as movement, scaling and rotation.

  • Dialog Principles – ISO 9241 Dialogue self-descriptiveness
  • Susan Weinschenk Responsiveness
  • Gerhardt-Powals Limit data-driven tasks
  • Nielsen Visibility of system status
Aim for high recognition

Design should meet culturally, psychologically and context, from the target audience to create an effective glance.
To ease the recognition process, speak the user's language, talk in terms that the user will easily understand. Thus, avoiding wasting time by translating or interpreting the content.

  • Susan Weinschenk Linguistic Clarity
  • Susan Weinschenk Aesthetic Integrity
  • Susan Weinschenk Technical Clarity
  • Gerhardt-Powals Automate unwanted workload
  • Gerhardt-Powals Present new information with meaningful aids to interpretation
  • Nielsen Recognition rather than recall
Simpler Interactions
Get to the goal in a clear and simple way
Walkthrough the novice user

A learning experience should invite the user to grasp the new know-how. This invitation can be accepted or declined by the user.

  • Dialog Principles – ISO 9241 Suitability for learning
  • Susan Weinschenk User Support
  • Laws of Simplicity Law 4: Learn
  • Laws of Simplicity Law 9: Failure
  • Nielsen Help and documentation
Give Control

Give a range of maneuverability, freedom and flexibility to the user.
Avoid forcing the user into an anticipated decision.

  • Dialog Principles – ISO 9241 Controllability
  • Nielsen User control and freedom
Ease connectivity

Disconnecting and connecting with devices near or worn by the user should be done with ease.
Connectivity should be architected to be simple, intuitive and quick to do by the targeted audience or user.
In some cases, it may even be simplified to an automatic connection but still respecting the user's empowerment.

Agile interactions

Interactions should be clear and easy to perform by the user as possible. Therefore, it is vital to maintain the native interactions and/or well known interactions by them.
The right interaction for the right task is a must in the smartwatch world, for instance, voice input is promoted for commands and to simplify complex writing for the user.

  • Susan Weinschenk Modal Integrity
  • Susan Weinschenk Predictability
  • Nielsen Flexibility and efficiency of use
Predictable and Understandable Navigation

Be consistent with the way users navigate. Use understandable affordances that communicate effective feedback to satisfy the user's predictions with a short time span and without hesitation.

  • Dialog Principles – ISO 9241 Comformity with user Expectations
  • Susan Weinschenk Predictability
  • Susan Weinschenk Accuracy
  • Nielsen Error prevention
  • Nielsen Consistency and standards
Easy recovery

Allow the user to recover from errors easily.

  • Dialog Principles – ISO 9241 Error tolerance
  • Susan Weinschenk Forgiveness
  • Nielsen Help users recognize, diagnose, and recover from errors
Device Aware
Know the device's possibilities and limitations
Design on awareness

Design being aware of the different characteristics on every device. Consider limitations -such as battery life and screen size-, accessibility and ergonomics.

  • Susan Weinschenk Fulfillment
  • Susan Weinschenk Consistency
Standalone and Independent

Design must work as a standalone when in need, since connectivity is not guaranteed.

Link Data and Devices
Link devices, data, state and interactions
Interconnect Devices

Consider a direct connection with other devices.

Expose and consume data

Expose and consume data to an accessible and common repository that can be accessible to all related apps.

  • Laws of Simplicity Key 2: Open
Seamless State change

State changes in data and situations on one device should be reflected seamlessly on others.

Think of all as a whole

Devices are not isolated pieces of technologies.

Design for the future devices

New devices emerge and new data will be available. Think and design for the upcoming and not just for the current.

Cross-channel Consistency
Deliver a consistent experience
Accessible to "all" devices

Core experience usage and functionality must match and be satisfied on every available device.

Respect a common objective and experience

A global experience should be common to all channels (PC, mobile, wearable), still it also has to be adapted and unique to every device.

  • Susan Weinschenk Fulfillment
  • Laws of Simplicity Law 10: The One
Consistency within a multichannel

Each channel should be consistent visually and interaction-wise. Visual language must be shared among all the channels.
The actions taken to achieve a common goal should be similar and predictable as well as those on the other channels.

  • NASA Consistency
  • Nielsen Consistency and standards