Quality Criteria
+ + +You Should Also Read
+ +
++ Android Wear aims to provide users with just the right information at just the right time. Great + Android Wear experiences are launched automatically, glanceable, and require zero or low user + interaction. Designing apps for wearables is substantially different than designing for phones or + tablets. There are different strengths and weaknesses, different use cases, and different + ergonomics to take into consideration. +
+ ++ The first step toward creating a great experience for users on Wear is to read the + Android Wear design guidelines, which provides + instructions on how to build the best user experience for Wear apps. You should also review the + Building Apps for Wearables training, to + understand the basic implementation requirements for a Wear app. +
+ ++ Important: To ensure a great user experience, apps for wearables must meet + specific requirements for usability. Only apps that meet the following quality criteria will + qualify as an Android Wear app on Google Play. Qualifying as a Wear app will make it easier for + Android Wear users to discover your app on Google Play. +
+ ++ Note: You will be able to submit your apps for Android Wear review when the + public release of Android 5.0 launches on November 3. Stay tuned for more information about how to + submit your apps for Android Wear review through the Google Play Developer Console. +
+ ++ Functionality +
+ + ++ These criteria ensure that your app is configured correctly and provides the expected + functional behavior. +
+ + +| + Type + | ++ ID + | ++ Description + | +
|---|---|---|
| + General + | + ++ WR-GL + | +
+ + Handheld app includes either notifications with wearable-specific functionality or a wearable + app that runs directly on the Wear device. + (Learn how) + + |
+
| + Packaging + | + ++ WR-PK + | +
+ + Wearable apps that run directly on the device are packaged inside the primary handheld app. + (Learn how) + + |
+
| + Notifications + | + ++ WR-FW + | +
+ + Notifications with wearable-specific functionality use a {@code RemoteInput} or + {@code WearableExtender}. + (Learn how) + + |
+
| + WR-FR + | +
+ + Notifications for messaging apps allow users to reply via voice input or quick responses. + (Learn how) + + |
+|
| + WR-FG + | +
+ + Similar notifications are grouped together in a stack. + (Learn how) + + |
+|
| + Gestures + | + ++ WR-GP + | +
+
+ Full-screen activities use long press for the sole purpose of prompting to quit.
+ |
+
Related resources
+ + + ++ Visual Design and User Interaction +
+ + ++ These criteria ensure that your app follows critical design and interaction patterns to provide a + consistent, intuitive, and enjoyable user experience on wearables. +
+ +| + Type + | ++ ID + | ++ Description + | +
|---|---|---|
| + Layout + | + ++ WR-LL + | +
+ + App user interface is formatted appropriately for both square and round displays. + (Learn how) + + |
+
| + WR-TC + | +
+ + App text is large and glanceable with a suggested minimum size of 16sp. + (Learn how) + + |
+|
| + Launcher + | + ++ WR-LN + | +
+ + App launcher string is the app name, not a command phrase. + (Learn how) + + |
+
| + Notifications + | + ++ WR-NC + | +
+ + App displays confirmation animations when appropriate. + (Learn how) + + |
+
| + WR-NR + | +
+
+ Notification cards have the app icon visible at the top right edge. The one exception is if the
+ notification card has single-action controls, for example a media playback card.
+ |
+|
| + WR-WI + | +
+
+ Notification actions have a white icon, action title, and transparent background.
+ |
+|
| + WR-PB + | +
+ + Notification photo backgrounds are used only to convey information, not to brand a card. + (Learn how) + + |
+|
| + WR-PR + | +
+ + Notification photo backgrounds have a resolution of at least 400x400. + (Learn how) + + |
+|
| + Google Play + | + ++ WR-GS + | +
+ + App includes at least one Wear screenshot in Play details page. + (Learn how) + + |
+
Related resources
+ + + ++ Frequently Asked Questions +
++ After I submit my app for Android Wear review, how will I find out if my app does not meet + all the requirements for Wear? +
++ If your app does not meet the usability requirements described on this page, the Play Store team + will contact you through the email address specified in the Google Play Developer Console account associated with + the app. +
++ Caution: Make sure your app meets the functionality + requirements, otherwise your app will not be considered a Wear app and will not be reviewed + for Wear design and interaction. +
++ Note: You will be able to submit your apps for additional Android Wear review when + the public release of Android 5.0 launches on November 3. +
+ + ++ If my app does not meet the Wear requirements, will my new or updated app still appear on + Google Play for phones and tablets and still be installable on wearables? +
++ Yes. The requirements described above only determine whether your app will be identified as an + Android Wear app on Google Play and easier for Android Wear users to discover. If your app is not + accepted as a Wear app, it will still be available to other device types, such as phones and + tablets, and it will still be installable on wearables. +
diff --git a/docs/html/distribute/images/gp-wear-quality.png b/docs/html/distribute/images/gp-wear-quality.png new file mode 100644 index 0000000000000..41ae2bc493c12 Binary files /dev/null and b/docs/html/distribute/images/gp-wear-quality.png differ diff --git a/docs/html/jd_collections.js b/docs/html/jd_collections.js index c49f8cc931234..08c00902ac241 100644 --- a/docs/html/jd_collections.js +++ b/docs/html/jd_collections.js @@ -67,9 +67,9 @@ var RESOURCE_COLLECTIONS = { "distribute/essentials/quality/core.html", "distribute/essentials/quality/tablets.html", "distribute/essentials/quality/tv.html", + "distribute/essentials/quality/wear.html", "https://developers.google.com/edu/guidelines", - "distribute/essentials/optimizing-your-app.html", - "distribute/essentials/best-practices/games.html" + "distribute/essentials/optimizing-your-app.html" ] }, "distribute/users": { @@ -332,6 +332,22 @@ var RESOURCE_COLLECTIONS = { "training/tv/games/index.html" ] }, + "distribute/essentials/wearqualityguidelines/visualdesign": { + "title": "", + "resources": [ + "design/wear/index.html", + "training/building-wearables.html", + "training/wearables/ui/index.html" + ] + }, + "distribute/essentials/wearqualityguidelines/functionality": { + "title": "", + "resources": [ + "training/wearables/notifications/index.html", + "training/wearables/apps/index.html", + "training/wearables/notifications/voice-input.html" + ] + }, "distribute/essentials/core/performance": { "title": "", "resources": [ diff --git a/docs/html/training/wearables/apps/index.jd b/docs/html/training/wearables/apps/index.jd index 7d961b783ad16..ffb4131a2e16b 100644 --- a/docs/html/training/wearables/apps/index.jd +++ b/docs/html/training/wearables/apps/index.jd @@ -1,5 +1,6 @@ page.title=Creating Wearable Apps -page.image=wear/images/notifications.png +page.tags="wear","wearable","app" +page.image=wear/images/02_notifications.png @jd:body diff --git a/docs/html/training/wearables/notifications/index.jd b/docs/html/training/wearables/notifications/index.jd index 17f3cb3c57d44..a7b67333ff52b 100644 --- a/docs/html/training/wearables/notifications/index.jd +++ b/docs/html/training/wearables/notifications/index.jd @@ -1,4 +1,6 @@ page.title=Adding Wearable Features to Notifications +page.tags="wear","notifications","wearables" +page.image=wear/images/01_notifications.png @jd:body