How to improve app design for Wear 2.0

  • Use a couple of app launchers in case your app has two or 3 discrete
    purposes:
    For instance, in case your app helps
    each process monitoring—with quite a lot of choices, movements,
    and perspectives—and historic research and control of tracked actions, you’ll be able to
    use a couple of app launchers to take care of those duties. Alternatively, in case your app has
    a easy house display, those options might be positioned in line, on the backside of
    the display.
  • Use peeking on the best of the motion drawer to supply fast get right of entry to
    to the principle motion:
    If there is not any number one motion related to
    the view, override the default conduct and power an overflow button to peek
    as a substitute, exposing all movements on the backside of a view, when tapped.
  • Ensure that for gadgets the use of Wear 2.0, your app takes good thing about those new UI
    patterns to supply a constant person revel in. Check out extra coaching
    sources for Wear
    Navigation and Actions
    and the Material Design specs for Navigation
    and Action
    Drawers.

    Notifications

    Wear 2.0 makes use of a more practical vertical navigation development, doing away with the horizontal
    swiping gesture to provide movements for a notification. Notification movements are
    now introduced as a unmarried number one motion (if acceptable) on the backside of a
    notification. If there is not any number one motion, increasing the notification will
    provide choices in one, vertically scrollable view.

    Notifications will paintings while not having many adjustments on each 1.x and 2.0
    gadgets, however seem fairly other:

    When developing apps for Wear 2.0 gadgets, improve the person revel in with
    notifications through making use of the next best possible practices:

    1. Support expandable notifications: Use BigTextStyle
      in order that customers can see extra content material on their watch.
    2. Use the collapsed view of the notification (if acceptable):
      Add the principle motion for your notification to the collapsed view of the
      notification the use of setContentIntent(), the place suitable.
    3. For messaging apps, use the MessagingStyle:
      Provide a wealthy chat app-like revel in within the expanded notification the use of this
      taste.
    4. Update person instructions that are particular to Wear 1.zero:
      Remove any textual content guiding customers to act on a card through swiping horizontally
      (the Wear 1.x development).
    5. Enhancing notifications to use inline movements: This lets in
      customers to do issues while not having faucet to see the expanded notification main points.
      Actions for messaging notifications can use a number of other enter strategies
      together with Smart Reply presets, voice, and keyboard enter. Take good thing about
      those options to supply added capability and pleasure customers.

    To be told extra about adding
    wearable features to notifications
    .

    Complications

    The headaches API in Wear 2.0 makes it a lot more straightforward for watch face builders
    and third-party information suppliers to floor vital knowledge customers need, at a
    look. Watch faces that make stronger the API may also be configured to use any of the
    information suppliers which were put in at the watch whilst keeping up entire
    keep an eye on over their look. Apps supporting the complication API permit the
    app’s information to be available on any watch faces that make stronger headaches. These
    headaches may also be displayed in quite a lot of bureaucracy (quick textual content, icon, ranged
    worth, lengthy textual content, small symbol, and big symbol) relying on what the knowledge
    supplier has configured and what sort of house has been allotted at the watch face.

    To make certain that headaches have compatibility the entire design of the watch face and
    correctly take care of their information kind, when including complication make stronger we propose
    watch face makers must:

    1. Use the TextRenderer
      elegance discovered within the Wear 2.0 SDK:
      This lets in the textual content inside
      headaches to be adjusted to their bounds through shrinking the textual content, dynamically
      supporting line breaks or ellipsizing strings once they exceed the limits of a
      text-based complication.
    2. Use the ComplicationDrawable
      elegance to set the background colour, form, border, and font choices for the
      headaches:
      This provides entire keep an eye on of ways the complication is
      rendered to the watch face.
    3. Design the watch face to supply some way for customers to configure or
      regulate headaches at the watch face via a settings menu:
      To
      find out how to assemble those settings see the watch face pattern
      on GitHub.
    4. Use the knowledge supplier test
      suite
      app to feed dummy information to the watch face headaches:
      This
      will assist you to to check that all the headaches render correctly and feature
      fonts formatted for their bounds.
    5. As a complication information supplier, disclose related information through the use of the
      ComplicationProviderService:

      Simply outline and configure what sorts of ComplicationData
      the app can give for headaches.

    Standalone capability on Wear gadgets

    1. Make certain your app is ready to take care of itself if there is not any spouse
      app put in when the use of the android..kind.watch characteristic
      flag
      : Using this selection allows your app to change into searchable and
      installable without delay on Wear gadgets while not having to set up a spouse
      telephone app, so make sure your app can take care of itself to steer clear of a complicated or damaged
      person revel in.
    2. Ensure your wearable app does not depend at the telephone app for
      sign-in/authentication or number one capability
      : When requiring
      difficult enter for authentication (for instance, password access) your wearable
      app can level to the spouse telephone, however must depend on internet UI for
      account/password access relatively than an app.
    3. Where a spouse app will have to be provide on a telephone to make stronger your app
      in every other manner, the app must use the CapabilityApi:

      This must be used to correctly direct customers to the Play Store checklist on their
      spouse instrument to set up the lacking app. Otherwise, the app must serve as
      by itself, the use of the Wear integrated Wi-Fi, GPS, or different connectivity purposes.

    4. Include wording about any spouse app necessities or in short
      point out how your Wear app must serve as throughout the Play Store checklist
      description
      : This will assist set expectancies and information customers to set up
      the proper apps for the most productive imaginable revel in.
    5. Incorporate the com.google.android.wearable.standalone
      flag within the manifest in case your Wearable app can serve as with none telephone
      spouse interplay
      : This flag signifies that the wearable app may also be
      put in and can totally serve as when no longer paired to an Android or iOS spouse
      telephone.

    Though so much was once lined right here, there are further sources you’ll be able to use to
    make certain that your apps or video games are optimized and use the most recent patterns and
    capability on Wear. Be certain to review
    the quality guidelines
    and take a look at the developer coaching documentation to
    be told extra best possible practices for wearable app
    development
    and wearable
    app design
    so as to construct high quality apps for Wear.

    How helpful did you to find this blogpost?







    Wear
    2.0 launched
    again in February with added make stronger for new options
    as well as to adopting new Material
    Design themes
    ,
    pointers,
    and a more practical vertical UI development. It additionally introduces a complications
    API
    , making it more straightforward for apps to supply information to watch faces, and watch
    faces to incorporate exterior information. The ultimate giant replace was once that, apps
    concentrated on Wear 2.0 now have the opportunity to perform in a standalone
    mode
    , while not having a connection to a spouse app at the telephone.

    There are a couple of design concerns in relation to navigation, notifications,
    the headaches API, and the standalone capability to will let you higher
    optimize for Wear 2.0 gadgets:

    Navigation

    1. Use the WearableDrawerLayout navigation drawer for easy and rare
      navigation:
      Simple navigation comprises duties equivalent to having access to app
      settings, switching customers or logging out. You can put in force
      this on Wear 2.0 to transfer between other perspectives or sections of the app by way of a
      swipe down from the highest of the display, or an motion drawer may also be arrange for
      context-specific movements when swiping up from the ground of the display.
    2. Present a navigation drawer as a single-page drawer to permit customers
      to navigate perspectives briefly:
      A navigation drawer may also be introduced as
      both a multi-page or single-page drawer. The single-page structure turns out to be useful for
      when the person is anticipated to navigate briefly between 7 or much less perspectives of the
      app. Remember that if the app is the use of a single-page drawer, the iconography
      must be transparent and comprehensible as there may not be any form of textual content
      labeling on this structure. If there are greater than 7 perspectives to navigate to or the
      perspectives don’t seem to be simply represented through icons, you must as a substitute use the multi-page
      drawer structure.

    3. Use a couple of app launchers in case your app has two or 3 discrete
      purposes:
      For instance, in case your app helps
      each process monitoring—with quite a lot of choices, movements,
      and perspectives—and historic research and control of tracked actions, you’ll be able to
      use a couple of app launchers to take care of those duties. Alternatively, in case your app has
      a easy house display, those options might be positioned in line, on the backside of
      the display.
    4. Use peeking on the best of the motion drawer to supply fast get right of entry to
      to the principle motion:
      If there is not any number one motion related to
      the view, override the default conduct and power an overflow button to peek
      as a substitute, exposing all movements on the backside of a view, when tapped.

    Ensure that for gadgets the use of Wear 2.0, your app takes good thing about those new UI
    patterns to supply a constant person revel in. Check out extra coaching
    sources for Wear
    Navigation and Actions
    and the Material Design specs for Navigation
    and Action
    Drawers.

    Notifications

    Wear 2.0 makes use of a more practical vertical navigation development, doing away with the horizontal
    swiping gesture to provide movements for a notification. Notification movements are
    now introduced as a unmarried number one motion (if acceptable) on the backside of a
    notification. If there is not any number one motion, increasing the notification will
    provide choices in one, vertically scrollable view.

    Notifications will paintings while not having many adjustments on each 1.x and 2.0
    gadgets, however seem fairly other:

    When developing apps for Wear 2.0 gadgets, improve the person revel in with
    notifications through making use of the next best possible practices:

    1. Support expandable notifications: Use BigTextStyle
      in order that customers can see extra content material on their watch.
    2. Use the collapsed view of the notification (if acceptable):
      Add the principle motion for your notification to the collapsed view of the
      notification the use of setContentIntent(), the place suitable.
    3. For messaging apps, use the MessagingStyle:
      Provide a wealthy chat app-like revel in within the expanded notification the use of this
      taste.
    4. Update person instructions that are particular to Wear 1.zero:
      Remove any textual content guiding customers to act on a card through swiping horizontally
      (the Wear 1.x development).
    5. Enhancing notifications to use inline movements: This lets in
      customers to do issues while not having faucet to see the expanded notification main points.
      Actions for messaging notifications can use a number of other enter strategies
      together with Smart Reply presets, voice, and keyboard enter. Take good thing about
      those options to supply added capability and pleasure customers.

    To be told extra about adding
    wearable features to notifications
    .

    Complications

    The headaches API in Wear 2.0 makes it a lot more straightforward for watch face builders
    and third-party information suppliers to floor vital knowledge customers need, at a
    look. Watch faces that make stronger the API may also be configured to use any of the
    information suppliers which were put in at the watch whilst keeping up entire
    keep an eye on over their look. Apps supporting the complication API permit the
    app’s information to be available on any watch faces that make stronger headaches. These
    headaches may also be displayed in quite a lot of bureaucracy (quick textual content, icon, ranged
    worth, lengthy textual content, small symbol, and big symbol) relying on what the knowledge
    supplier has configured and what sort of house has been allotted at the watch face.

    To make certain that headaches have compatibility the entire design of the watch face and
    correctly take care of their information kind, when including complication make stronger we propose
    watch face makers must:

    1. Use the TextRenderer
      elegance discovered within the Wear 2.0 SDK:
      This lets in the textual content inside
      headaches to be adjusted to their bounds through shrinking the textual content, dynamically
      supporting line breaks or ellipsizing strings once they exceed the limits of a
      text-based complication.
    2. Use the ComplicationDrawable
      elegance to set the background colour, form, border, and font choices for the
      headaches:
      This provides entire keep an eye on of ways the complication is
      rendered to the watch face.
    3. Design the watch face to supply some way for customers to configure or
      regulate headaches at the watch face via a settings menu:
      To
      find out how to assemble those settings see the watch face pattern
      on GitHub.
    4. Use the knowledge supplier test
      suite
      app to feed dummy information to the watch face headaches:
      This
      will assist you to to check that all the headaches render correctly and feature
      fonts formatted for their bounds.
    5. As a complication information supplier, disclose related information through the use of the
      ComplicationProviderService:

      Simply outline and configure what sorts of ComplicationData
      the app can give for headaches.

    Standalone capability on Wear gadgets

    1. Make certain your app is ready to take care of itself if there is not any spouse
      app put in when the use of the android..kind.watch characteristic
      flag
      : Using this selection allows your app to change into searchable and
      installable without delay on Wear gadgets while not having to set up a spouse
      telephone app, so make sure your app can take care of itself to steer clear of a complicated or damaged
      person revel in.
    2. Ensure your wearable app does not depend at the telephone app for
      sign-in/authentication or number one capability
      : When requiring
      difficult enter for authentication (for instance, password access) your wearable
      app can level to the spouse telephone, however must depend on internet UI for
      account/password access relatively than an app.
    3. Where a spouse app will have to be provide on a telephone to make stronger your app
      in every other manner, the app must use the CapabilityApi:

      This must be used to correctly direct customers to the Play Store checklist on their
      spouse instrument to set up the lacking app. Otherwise, the app must serve as
      by itself, the use of the Wear integrated Wi-Fi, GPS, or different connectivity purposes.

    4. Include wording about any spouse app necessities or in short
      point out how your Wear app must serve as throughout the Play Store checklist
      description
      : This will assist set expectancies and information customers to set up
      the proper apps for the most productive imaginable revel in.
    5. Incorporate the com.google.android.wearable.standalone
      flag within the manifest in case your Wearable app can serve as with none telephone
      spouse interplay
      : This flag signifies that the wearable app may also be
      put in and can totally serve as when no longer paired to an Android or iOS spouse
      telephone.

    Though so much was once lined right here, there are further sources you’ll be able to use to
    make certain that your apps or video games are optimized and use the most recent patterns and
    capability on Wear. Be certain to review
    the quality guidelines
    and take a look at the developer coaching documentation to
    be told extra best possible practices for wearable app
    development
    and wearable
    app design
    so as to construct high quality apps for Wear.

    How helpful did you to find this blogpost?







    Source link

    Reply