1page.title=Distribute to Android Wear
2page.image=/design/media/wear/ContextualExample.008_2x.png
3meta.tags="wear", "publish", "quality"
4page.tags="wear", "publish", "googleplay"
5page.metaDescription=Distribute your apps, games, and content to Android Wear.
6
7@jd:body
8
9<div id="qv-wrapper"><div id="qv">
10<h2>How to Participate</h2>
11<ol>
12<li><a href="#understand_guidelines">Understand the guidelines</a></li>
13<li><a href="#develop_app">Develop a great app for Wear</a></li>
14<li><a href="#test_app">Test for Wear App Quality</a></li>
15<li><a href="#opt_in">Opt-in</a></li>
16<li><a href="#track_review">Track your review</a></li>
17</ol>
18
19<h2>You Should Also Read</h2>
20<ol>
21<li><a href="{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a></li>
22<li><a href="{@docRoot}distribute/essentials/quality/core.html">Core App Quality</a></li>
23</ol>
24
25</div></div>
26
27<p>
28  If you've got a great app, Android Wear and Google Play can help you bring it to users. While all
29  apps are able to send basic notifications to Android Wear devices, you can go much further.
30  Extend your apps to support custom Wear interactions and offer a refined, engaging user
31  experience across all Wear devices. If your apps meet core app quality guidelines on handsets and
32  provide a high-quality experience for Android Wear devices, Google Play will showcase your apps
33  for easy discovery.
34</p>
35
36<p>
37  To get started, review the sections in this document to learn how to distribute your Wear apps
38  to users through Google Play. Be sure to read <a
39  href="{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a> for information on
40  the usability and quality standards that your apps should meet. When your app is ready, you can
41  opt-in for designation as an Android Wear app from the Developer Console.
42</p>
43
44<h2 id="how_to_participate">
45  How to Participate
46</h2>
47
48<p>
49  Google Play lets you make your Wear apps more discoverable for Wear users. You can develop and
50  publish using your existing Developer Console account and your current distribution and pricing
51  settings. It's easy to participate — the sections below outline the process.
52</p>
53
54<h3 id="understand_guidelines">
55  1. Understand guidelines and requirements
56</h3>
57
58<div style="float:right;margin:1em 0 1.5em 2em;">
59  <img src="{@docRoot}images/gp-wear-process.png">
60</div>
61
62<p>
63  To prepare for a successful launch on Android Wear, start by reviewing the guidelines for
64  creating great app experiences on Wear. See the <a href="{@docRoot}design/wear/index.html">Android
65  Wear design guidelines</a> for ideas on extending your app for Wear and details on design and
66  usability.
67</p>
68
69<p>
70  As you get started designing your Wear experience, make sure to read and understand the quality
71  criteria for Wear apps. Only apps that are usable on Wear will be designated as Wear apps on
72  Google Play — your apps can participate if they meet a set of basic quality criteria. See <a
73  href="{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a> for details.
74</p>
75
76<h3 id="develop_app">2. Develop a great app for Wear</h3>
77
78<p>
79Once you have read the guidelines, the next step is to develop your app. The following sections
80describe how to start building a great app experience for Wear.
81</p>
82
83<h4>Design first</h4>
84
85<p>
86  Android Wear aims to provide users with just the right information at just the right time. Great
87  Android Wear experiences are launched automatically, glanceable, and
88  require zero or low user interaction. Although all apps can send basic notifications to Wear
89  devices without any modification, great apps built for Wear are refined to offer a polished and
90  high-quality experience, work on different screen layouts, and deliver a compelling feature set
91  for users.
92</p>
93
94<p>
95  As you consider your Wear app, review the <a href=
96  "{@docRoot}training/building-wearables.html">developer documentation</a> and <a
97  href="{@docRoot}design/wear/index.html">usability guidelines</a> and plan on utilizing them to the
98  greatest extent possible. You can design a great notification experience for users with the APIs
99  provided in the SDK and support library. You may also choose to build an app that runs directly
100  on the wearable.
101</p>
102
103<h4>Package your app</h4>
104
105<p>
106  We recommend that you deliver your Wear experience as part of your existing app for phones,
107  tablets, and other devices, using the same package name and store listing. This lets users
108  upgrade to your Wear experience seamlessly and also lets you take advantage of the reviews and
109  ratings you’ve earned in your app for phones and tablets. For wearable apps that depend on an
110  app for functionality, you should always package it within that app. To learn how, read <a
111  href="{@docRoot}training/wearables/apps/packaging.html">Packaging Wearable Apps</a>.
112</p>
113
114<h4>Test on a variety of devices</h4>
115
116<p>
117  Throughout design and development, it's important to have suitable devices on which to prototype
118  and test your user experience. It's highly recommended that you acquire one or more Android Wear
119  devices or develop with different emulator configurations and set up your testing environment as
120  early as possible. It’s important that you optimize your design on both square and round layouts.
121</p>
122
123<h3 id="test_app">3. Test for Wear App Quality</h3>
124
125<p>
126  Your Wear apps should be designed to perform well and look great on Android Wear, and they should
127  offer the best user experience possible. Google Play will showcase selected high-quality Wear
128  apps for easy discovery. Here’s how you can participate and deliver an Android Wear app that
129  users will enjoy:
130</p>
131
132<ul>
133  <li>Meet Core App Quality guidelines
134    <ul>
135      <li>Follow <a href="{@docRoot}design/index.html">Android Design
136      guidelines</a>. Pay special attention to using <a href=
137      "http://www.google.com/design/spec/material-design/introduction.html">material
138      design</a> in your app.
139      </li>
140
141      <li>Test your apps against the <a href=
142      "{@docRoot}distribute/essentials/quality/core.html">Core App Quality
143      guidelines</a>.
144      </li>
145    </ul>
146  </li>
147  <li>Meet <a href="{@docRoot}distribute/essentials/quality/wear.html">Wear App
148  Quality</a> criteria
149    <ul>
150      <li>Follow our best practices for <a href="{@docRoot}training/building-wearables.html">
151      Wear app development</a></li>
152      <li>Make sure your app meets all of the <a href=
153      "{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a> criteria</li>
154    </ul>
155  </li>
156</ul>
157
158<h3 id="opt_in">4. Opt-in to Android Wear and publish</h3>
159
160<p>
161  When you've built your release-ready APK and tested to ensure that it meets all of the <a
162  href="{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a> criteria, upload it
163  to the Developer Console. Update your store listing with Wear screenshots and set distribution
164  options as needed. If you aren't familiar with how to prepare for launch on Google Play, see the
165  <a href="{@docRoot}distribute/googleplay/publish/preparing.html">Launch Checklist.</a>
166</p>
167
168<p>
169  Before you publish to users, you may opt-in to Android Wear from the <strong>Pricing and
170  Distribution</strong> section of the Developer Console. Opt-in means that you want your app to
171  be made more discoverable to Android Wear users through Google Play, and that your app meets <a
172  href="{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a> criteria.
173</p>
174
175<p>
176  After you've opted-in and saved changes, you can publish your app as usual. In addition, Google
177  Play submits your app for review against the <a
178  href="{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a> criteria and
179  notifies you of the result. See the next section for details on how to track the approval status
180  of your app.
181</p>
182
183<p>
184  If your app meets all <a href="{@docRoot}distribute/essentials/quality/wear.html">Wear App
185  Quality</a> criteria, Google Play makes it more discoverable to Android Wear users. Your app is
186  also eligible for higher-visibility featuring in app collections and promotions.
187</p>
188
189<p>
190  Note that opt-in and review do not affect the availability of your app in the Google Play Store
191  &mdash; your app is available as soon as you publish.
192</p>
193
194<p>
195  Here are the steps to opt-in to Android Wear in the Developer Console:
196</p>
197
198<ol>
199  <li>Make sure your app meets all <a href=
200  "{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a> criteria
201  </li>
202
203  <li>Add Wear screenshots to the app’s store listing
204  </li>
205
206  <li>In the <strong>All Applications</strong> page, click the app you want to opt-in.
207  </li>
208
209  <li>Under <strong>Pricing and Distribution</strong>, scroll down to find <em>Android Wear</em>
210  and the opt-in checkbox.
211  </li>
212
213  <li>Click the checkbox next to <em>Distribute your app on Android Wear</em>.
214  </li>
215
216  <li>Click <strong>Save</strong> to save your Pricing and Distribution changes.
217  </li>
218</ol>
219
220<div style="padding-top:1em">
221  <img style="border:2px solid #ddd;" src="{@docRoot}images/gp-wear-opt-in.png">
222  <p class="caption">
223    <strong>Opt-in for Wear:</strong> Include your app in Android Wear by opting-in from the
224    Developer Console.
225  </p>
226</div>
227
228<h3 id="track_review">5. Track your review and approval</h3>
229
230<p>
231  If your app meets the technical and quality criteria for Android Wear, as described above, your
232  app will be made more discoverable for users on Android Wear. If your app doesn’t meet the
233  criteria, you’ll receive a <strong>notification email sent to your developer account
234  address</strong>, with a summary of the areas that you need to address. When you’ve made the
235  necessary adjustments, you can upload a new version of your app to the Developer Console.
236</p>
237
238<p>
239  At any time, you can check the review and approval status of your app in the Developer Console,
240  under <em>Android Wear</em> in the app's <strong>Pricing and Distribution</strong>
241  page.
242</p>
243
244<p>
245  There are three approval states:
246</p>
247
248<ul>
249  <li>
250    <em>Pending</em> — Your app was sent for review and the review is not yet complete.
251  </li>
252
253  <li>
254    <em>Approved</em> — Your app was reviewed and approved. The app will be made more discoverable
255    to Android Wear users.
256  </li>
257
258  <li>
259    <em>Not approved</em> — Your app was reviewed and not approved. Check the notification email
260    for information about why the app was not approved. You can address any issues and opt-in and
261    publish again to initiate another review.
262  </li>
263</ul>
264
265<p>To understand how your apps are evaluated, please see the <a href=
266"{@docRoot}distribute/essentials/quality/wear.html">Wear App Quality</a> document. </p>
267
268
269  <h3>Related resources</h3>
270
271  <div class="resource-widget resource-flow-layout col-13"
272    data-query="collection:wearlanding"
273    data-cardSizes="6x2"
274    data-maxResults="3">
275  </div>
276