Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 1 | page.title=Launch Checklist |
| 2 | page.metaDescription=Essential overview of the complete process of delivering your app to users. Read this checklist early in development to help you plan for a successful launch on Google Play. |
| 3 | meta.tags="localizing, publishing, disttools" |
| 4 | page.tags="launch, publishing, Google Play" |
| 5 | page.image=/distribute/images/launch-checklist.jpg |
| 6 | |
| 7 | @jd:body |
| 8 | |
| 9 | <div id="qv-wrapper"> |
| 10 | <div id="qv" style="width:280px"> |
| 11 | <h2>Checklist</h2> |
| 12 | <ol> |
| 13 | <li><a href="#understand-publishing">1. Understand the Publishing Process</a></li> |
| 14 | <li><a href="#understand-policies">2. Understand Google Play Policies</a></li> |
| 15 | <li><a href="#test-quality">3. Test for Core App Quality</a></li> |
| 16 | <li><a href="#determine-rating">4. Determine Content Rating</a></li> |
| 17 | <li><a href="#determine-country">5. Determine Country Distribution</a></li> |
| 18 | <li><a href="#confirm-size">6. Confirm Overall Size</a></li> |
| 19 | <li><a href="#confirm-platform">7. Confirm Platform and Screen Ranges</a></li> |
| 20 | <li><a href="#decide-price">8. Decide Free or Priced</a></li> |
| 21 | <li><a href="#consider-billing">9. Use In-app Billing</a></li> |
| 22 | <li><a href="#set-prices">10. Set Prices for your Products</a></li> |
| 23 | <li><a href="#start-localization">11. Start Localization</a></li> |
| 24 | <li><a href="#prepare-graphics">12. Prepare Promotional Graphics, Screenshots, and Videos</a></li> |
| 25 | <li><a href="#build-upload">13. Build the Release-ready APK</a></li> |
| 26 | <li><a href="#plan-beta">14. Plan a Beta Release</a></li> |
| 27 | <li><a href="#complete-details">15. Complete the Store Listing</a></li> |
| 28 | <li><a href="#use-badges">16. Use Google Play Badges and Links</a></li> |
| 29 | <li><a href="#final-checks">17. Final Checks and Publishing</a></li> |
| 30 | <li><a href="#support-users">18. Support Users after Launch </a></li> |
| 31 | </ol> |
| 32 | </div> |
| 33 | </div> |
| 34 | |
| 35 | <div class="top-right-float" style="width:194px"><img |
| 36 | src="{@docRoot}distribute/images/launch-checklist.jpg"></div> |
| 37 | |
| 38 | <p> |
| 39 | Before you publish your apps on Google Play and distribute them to users, you |
| 40 | need to get the apps ready, test them, and prepare your promotional |
| 41 | materials. |
| 42 | </p> |
| 43 | |
| 44 | <p> |
| 45 | This page helps you understand the publishing process and get ready for a |
| 46 | successful product launch on Google Play. It summarizes some of the tasks |
| 47 | you'll need to complete before publishing your app on Google Play, such as |
| 48 | creating a signed, release-ready application package (APK), understanding the |
| 49 | requirements of the app, and creating the product page and graphic assets for |
| 50 | each of your apps. |
| 51 | </p> |
| 52 | |
| 53 | <p> |
| 54 | The preparation and publishing tasks are numbered to give you a rough idea of |
| 55 | sequence. However, you can handle the tasks in any sequence that works for |
| 56 | you or you can skip steps as appropriate. |
| 57 | </p> |
| 58 | |
| 59 | <p> |
| 60 | As you move toward publishing, a variety of support resources are available |
| 61 | to you. Relevant links are provided in each step. |
| 62 | </p> |
| 63 | |
| 64 | <div class="headerLine"> |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 65 | <h2 id="understand-publishing"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 66 | 1. Understand the Publishing Process |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 67 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 68 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 69 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 70 | </div> |
| 71 | |
| 72 | <p> |
| 73 | Before you begin the steps in this checklist, you should take a moment to |
| 74 | read and understand the overall publishing workflow and become familiar with |
| 75 | how the process works. In particular, you or your development team will need |
| 76 | to prepare your apps for release using a process common to all Android apps. |
| 77 | The <a href="{@docRoot}tools/publishing/publishing_overview.html">Publishing |
| 78 | workflow documents</a> provide the details on how publishing works and how to |
| 79 | get an APK ready for release. |
| 80 | </p> |
| 81 | |
| 82 | <p> |
| 83 | Once you are familiar with publishing in general, continue reading to |
| 84 | understand the issues that you should consider when publishing apps on Google |
| 85 | Play. |
| 86 | </p> |
| 87 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 88 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 89 | |
| 90 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 91 | "collection:distribute/toolsreference/launchchecklist/understanding" |
| 92 | data-sortorder="-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" |
| 93 | data-maxresults="6"> |
| 94 | </div> |
| 95 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 96 | <div class="headerLine"> |
| 97 | <h2 id="understand-policies"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 98 | 2. Understand Google Play Policies and Agreements |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 99 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 100 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 101 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 102 | </div> |
| 103 | |
| 104 | <p> |
| 105 | Make sure that you understand and follow the Google Play program policies |
| 106 | that you accepted when registering. Google Play actively enforces the |
| 107 | policies and any violations can lead to suspension of your apps or, for |
| 108 | repeated violations, termination of your developer account. |
| 109 | </p> |
| 110 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 111 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 112 | |
| 113 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 114 | "collection:distribute/toolsreference/launchchecklist/policies" data-sortorder= |
| 115 | "-timestamp" data-cardsizes="6x3" data-maxresults="6"> |
| 116 | </div> |
| 117 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 118 | <div class="headerLine"> |
| 119 | <h2 id="test-quality"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 120 | 3. Test for Quality |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 121 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 122 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 123 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 124 | </div> |
| 125 | |
| 126 | <p> |
| 127 | Before you publish apps on Google Play, it's important to make sure that they |
| 128 | meet the basic quality expectations for all Android apps, on all of the |
| 129 | devices that you are targeting. You can check your app's quality by setting |
| 130 | up a test environment and testing the app against a short set of |
| 131 | <strong>quality criteria that applies to all apps</strong>. For complete |
| 132 | information, see the <a href= |
| 133 | "{@docRoot}distribute/essentials/quality/core.html">Core App Quality</a> |
| 134 | guidelines. |
| 135 | </p> |
| 136 | |
| 137 | <p> |
| 138 | If your app is targeting tablet devices, make sure that it delivers a rich, |
| 139 | compelling experience to your tablet customers. See the <a href= |
| 140 | "{@docRoot}distribute/essentials/quality/tablets.html">Tablet App Quality</a> |
| 141 | guidelines for recommendations on ways to optimize your app for tablets. |
| 142 | </p> |
| 143 | |
| 144 | <p> |
| 145 | If you plan to make your apps available to Google Play for Education, then |
| 146 | you need to make sure they are suitable for a K-12 classroom and offer |
| 147 | outstanding educational value. See the <a href= |
| 148 | "{@docRoot}distribute/essentials/gpfe-guidelines.html">Education |
| 149 | Guidelines</a> for information on the characteristics your education apps |
| 150 | should exhibit. |
| 151 | </p> |
| 152 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 153 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 154 | |
| 155 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 156 | "collection:distribute/toolsreference/launchchecklist/quality" data-sortorder= |
| 157 | "-timestamp" data-cardsizes="6x3,6x3,6x3,9x3,9x3,9x3" data-maxresults="6"> |
| 158 | </div> |
| 159 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 160 | <div class="headerLine"> |
| 161 | <h2 id="determine-rating"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 162 | 4. Determine your App’s Content Rating |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 163 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 164 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 165 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 166 | </div> |
| 167 | |
| 168 | <p> |
| 169 | Google Play requires you to set a content rating for your app, which informs |
| 170 | Google Play users of its maturity level. Before you publish, you should |
| 171 | confirm what rating level you want to use. The available content rating |
| 172 | levels are: |
| 173 | </p> |
| 174 | |
| 175 | <ul> |
| 176 | <li> |
| 177 | <p> |
| 178 | Everyone |
| 179 | </p> |
| 180 | </li> |
| 181 | |
| 182 | <li> |
| 183 | <p> |
| 184 | Low maturity |
| 185 | </p> |
| 186 | </li> |
| 187 | |
| 188 | <li> |
| 189 | <p> |
| 190 | Medium maturity |
| 191 | </p> |
| 192 | </li> |
| 193 | |
| 194 | <li> |
| 195 | <p> |
| 196 | High maturity |
| 197 | </p> |
| 198 | </li> |
| 199 | </ul> |
| 200 | |
| 201 | <p> |
| 202 | On their Android devices, Android users can set the desired maturity level |
| 203 | for browsing. Google Play then filters apps based on the setting, so the |
| 204 | content rating you select can affect the app's distribution to users. You can |
| 205 | assign (or change) the content rating for your apps in the Developer Console, |
| 206 | no changes are required in your app binary. |
| 207 | </p> |
| 208 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 209 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 210 | |
| 211 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 212 | "collection:distribute/toolsreference/launchchecklist/rating" data-sortorder= |
| 213 | "-timestamp" data-cardsizes="9x3,6x3,6x3,9x3,9x3,9x3" data-maxresults="6"> |
| 214 | </div> |
| 215 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 216 | <div class="headerLine"> |
| 217 | <h2 id="determine-country"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 218 | 5. Determine Country Distribution |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 219 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 220 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 221 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 222 | </div> |
| 223 | |
| 224 | <p> |
| 225 | Google Play lets you control what countries and territories your apps are |
| 226 | distributed to. For the widest reach and the largest potential customer base, |
| 227 | you’d normally want to distribute to all available countries and territories. |
| 228 | However, because of business needs, app requirements, or launch dependencies, |
| 229 | you might want to exclude one or more countries from your distribution. |
| 230 | </p> |
| 231 | |
| 232 | <p> |
| 233 | It's important to determine the exact country distribution early, because it |
| 234 | can affect: |
| 235 | </p> |
| 236 | |
| 237 | <ul> |
| 238 | <li> |
| 239 | <p> |
| 240 | The need for localized resources in the app. |
| 241 | </p> |
| 242 | </li> |
| 243 | |
| 244 | <li> |
| 245 | <p> |
| 246 | The need for a localized app description in the Developer Console. |
| 247 | </p> |
| 248 | </li> |
| 249 | |
| 250 | <li> |
| 251 | <p> |
| 252 | Legal requirements for the app that may be specific to certain countries. |
| 253 | </p> |
| 254 | </li> |
| 255 | |
| 256 | <li> |
| 257 | <p> |
| 258 | Time zone support, local pricing, and so on. |
| 259 | </p> |
| 260 | </li> |
| 261 | </ul> |
| 262 | |
| 263 | <p> |
| 264 | With your target countries in mind, you should assess your localization |
| 265 | needs, both in your apps and in their Google Play listings details, and start |
| 266 | the work of localization well in advance of your target launch date. |
| 267 | </p> |
| 268 | |
| 269 | <p> |
| 270 | See <a href= |
| 271 | "{@docRoot}distribute/tools/localization-checklist.html">Localization |
| 272 | Checklist</a> for key steps and considerations in the localization process. |
| 273 | </p> |
| 274 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 275 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 276 | |
| 277 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 278 | "collection:distribute/toolsreference/launchchecklist/country" data-sortorder= |
| 279 | "-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" data-maxresults="6"> |
| 280 | </div> |
| 281 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 282 | <div class="headerLine"> |
| 283 | <h2 id="confirm-size"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 284 | 6. Confirm the App's Overall Size |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 285 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 286 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 287 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 288 | </div> |
| 289 | |
| 290 | <p> |
| 291 | The overall size of your app can affect its design and how you publish it on |
| 292 | Google Play. Currently, the maximum size for an APK published on Google Play |
| 293 | is <strong>50 MB</strong>. If your app exceeds that size, or if you want to |
| 294 | offer a secondary download, you can use <a href= |
| 295 | "{@docRoot}google/play/expansion-files.html">APK Expansion Files</a>, which |
| 296 | Google Play will host for free on its server infrastructure and automatically |
| 297 | handle the download to devices. |
| 298 | </p> |
| 299 | |
| 300 | <ul> |
| 301 | <li> |
| 302 | <p> |
| 303 | The maximum size for an APK published on Google Play is 50 MB. |
| 304 | </p> |
| 305 | </li> |
| 306 | |
| 307 | <li> |
| 308 | <p> |
| 309 | You can use up to two (2) APK Expansion Files, each up to 2GB in size, |
| 310 | for each APK. |
| 311 | </p> |
| 312 | </li> |
| 313 | </ul> |
| 314 | |
| 315 | <p> |
| 316 | Using APK Expansion files is a convenient, cost-effective method of |
| 317 | distributing large apps. However, the use of APK Expansion Files requires |
| 318 | some changes in your app binary, so you will need to make those changes |
| 319 | before creating your release-ready APK. |
| 320 | </p> |
| 321 | |
| 322 | <p> |
| 323 | To minimize the size of your app binary, make sure that you run the <a href= |
| 324 | "{@docRoot}tools/help/proguard.html">Proguard</a> tool or similar obfuscator |
| 325 | on your code when building your release-ready APK. |
| 326 | </p> |
| 327 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 328 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 329 | |
| 330 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 331 | "collection:distribute/toolsreference/launchchecklist/size" data-sortorder= |
| 332 | "-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" data-maxresults="6"> |
| 333 | </div> |
| 334 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 335 | <div class="headerLine"> |
| 336 | <h2 id="confirm-platform"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 337 | 7. Confirm the App's Platform and Screen Compatibility Ranges |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 338 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 339 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 340 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 341 | </div> |
| 342 | |
| 343 | <p> |
| 344 | Before publishing, it's important to make sure that your apps are designed to |
| 345 | run properly on the Android platform versions and device screen sizes that |
| 346 | you want to target. |
| 347 | </p> |
| 348 | |
| 349 | <p> |
| 350 | From an app-compatibility perspective, Android platform versions are defined |
| 351 | by <a href= |
| 352 | "{@docRoot}guide/topics/manifest/uses-sdk-element.html#ApiLevels">API |
| 353 | level</a>. You should confirm the minimum version that your app is compatible |
| 354 | with <a href= |
| 355 | "{@docRoot}guide/topics/manifest/uses-sdk-element.html"><minSdkVersion></a>, |
| 356 | as that will affect its distribution to Android devices once it is published. |
| 357 | </p> |
| 358 | |
| 359 | <p> |
| 360 | For screen sizes, you should confirm that the app runs properly and looks |
| 361 | good on the range of screen sizes and pixel densities that you want to |
| 362 | support. You should follow the advice provided in <a href= |
| 363 | "{@docRoot}guide/practices/screens_support.html">Supporting Multiple |
| 364 | Screens</a> to provide scalable support for multiple screen sizes. However, |
| 365 | if you have been unable to do so, declare the minimum screen-size supported |
| 366 | by your apps using <a href= |
| 367 | "{@docRoot}guide/topics/manifest/supports-screens-element.html"><supports-screens></a>. |
| 368 | Google Play will then restrict the availability of your apps accordingly, |
| 369 | making them available to devices with the declared screen size or large. |
| 370 | </p> |
| 371 | |
| 372 | <p> |
| 373 | To get a better understanding of the current device penetration of Android |
| 374 | platform versions and screen sizes across all Android devices, see the |
| 375 | <a href="{@docRoot}about/dashboards/index.html">Device Dashboard</a> charts. |
| 376 | </p> |
| 377 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 378 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 379 | |
| 380 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 381 | "collection:distribute/toolsreference/launchchecklist/platform" data-sortorder= |
| 382 | "-timestamp" data-cardsizes="6x3,6x3,6x3" data-maxresults="6"> |
| 383 | </div> |
| 384 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 385 | <div class="headerLine"> |
| 386 | <h2 id="decide-price"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 387 | 8. Decide Whether your App will be Free or Priced |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 388 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 389 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 390 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 391 | </div> |
| 392 | |
| 393 | <div class="figure"> |
| 394 | <img src="{@docRoot}images/gp-launch-checklist-1.png"> |
| 395 | </div> |
| 396 | |
| 397 | <p> |
| 398 | On Google Play, you can publish apps as free to download or priced. Free apps |
| 399 | can be downloaded by any Android user in Google Play. Paid apps can be |
| 400 | downloaded only by users who are in a country that supports paid downloads |
| 401 | and have registered a form of payment in Google Play, such as a credit card |
| 402 | or Direct Carrier Billing. |
| 403 | </p> |
| 404 | |
| 405 | <p> |
| 406 | Deciding whether you apps will be free or paid is important because, on |
| 407 | Google Play, <strong>free apps must remain free</strong>. |
| 408 | </p> |
| 409 | |
| 410 | <ul> |
| 411 | <li> |
| 412 | <p> |
| 413 | Once you publish an app as a free app, you cannot change it to being a |
| 414 | priced app. However, you can still sell <a href= |
| 415 | "{@docRoot}google/play/billing/billing_overview.html#products">in-app |
| 416 | products</a> and <a href= |
| 417 | "{@docRoot}google/play/billing/billing_subscriptions.html">subscriptions</a> |
| 418 | through Google Play's <a href= |
| 419 | "{@docRoot}google/play/billing/index.html">In-app Billing</a> service. |
| 420 | </p> |
| 421 | </li> |
| 422 | |
| 423 | <li> |
| 424 | <p> |
| 425 | If you publish your app as a priced app, you <em>can</em> change it at |
| 426 | any time to be a free app (<strong>but cannot then change it back to |
| 427 | priced</strong>). You can also sell in-app products and subscriptions. |
| 428 | </p> |
| 429 | </li> |
| 430 | </ul> |
| 431 | |
| 432 | <p> |
| 433 | If your app is be priced, or if you'll be selling in-app products, you need |
| 434 | <a href= |
| 435 | "https://developers.google.com/wallet/digital/training/getting-started/merchant-setup"> |
| 436 | set up a Google Wallet Merchant Account</a> before you can publish. |
| 437 | </p> |
| 438 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 439 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 440 | |
| 441 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 442 | "collection:distribute/toolsreference/launchchecklist/price" data-sortorder= |
| 443 | "-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" data-maxresults="6"> |
| 444 | </div> |
| 445 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 446 | <div class="headerLine"> |
| 447 | <h2 id="consider-billing"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 448 | 9. Consider using In-app Billing |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 449 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 450 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 451 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 452 | </div> |
| 453 | |
| 454 | <p> |
| 455 | Google Play <a href="{@docRoot}google/play/billing/index.html">In-app |
| 456 | Billing</a> lets you sell digital content in your applications. You can use |
| 457 | the service to sell a wide range of content, including downloadable content |
| 458 | such as media files or photos, and virtual content such as game levels or |
| 459 | potions. In-app Billing service lets you sell one-time purchases and |
| 460 | subscriptions from inside your app. This can help you to monetize the app |
| 461 | over its installed lifetime. |
| 462 | </p> |
| 463 | |
| 464 | <p> |
| 465 | If your are looking for more ways to monetize your app and build engagement, |
| 466 | you should consider In-app Billing or Instant Buy. These services have become |
| 467 | very popular with both users and developers. To use In-app Billing or Instant |
| 468 | Buy, you need to make changes to your app binary, so you will need to |
| 469 | complete and test your implementation before creating your release-ready APK. |
| 470 | </p> |
| 471 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 472 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 473 | |
| 474 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 475 | "collection:distribute/toolsreference/launchchecklist/purchasemethod" |
| 476 | data-sortorder="-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" |
| 477 | data-maxresults="6"> |
| 478 | </div> |
| 479 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 480 | <div class="headerLine"> |
| 481 | <h2 id="set-prices"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 482 | 10. Set Prices for your Products |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 483 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 484 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 485 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 486 | </div> |
| 487 | |
| 488 | <p> |
| 489 | If your apps is priced or you’ll sell in-app or physical products, Google |
| 490 | Play lets you set prices for your products in a variety of currencies, for |
| 491 | users in markets around the world. You can set prices individually in |
| 492 | different currencies, so you have the flexibility to adjust your price |
| 493 | according to market conditions and exchange rates. |
| 494 | </p> |
| 495 | |
| 496 | <p> |
| 497 | Before you publish, consider how you’ll price your products and what your |
| 498 | prices will be in various currencies. Later, you can set prices in all |
| 499 | available currencies through the Developer Console. |
| 500 | </p> |
| 501 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 502 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 503 | |
| 504 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 505 | "collection:distribute/toolsreference/launchchecklist/setprice" data-sortorder= |
| 506 | "-timestamp" data-cardsizes="9x3,9x3,9x3,9x3,9x3,9x3" data-maxresults="6"> |
| 507 | </div> |
| 508 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 509 | <div class="headerLine"> |
| 510 | <h2 id="start-localization"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 511 | 11. Start Localization |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 512 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 513 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 514 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 515 | </div> |
| 516 | |
| 517 | <p> |
| 518 | With your country targeting in mind, it's a good idea to assess your |
| 519 | localization needs, ensure your apps are internationalized, and start the |
| 520 | work of localizing well in advance of your target launch date. |
| 521 | </p> |
| 522 | |
| 523 | <p> |
| 524 | In addition to your application design, there are at least three aspects of |
| 525 | localization to consider: |
| 526 | </p> |
| 527 | |
| 528 | <ul> |
| 529 | <li> |
| 530 | <p> |
| 531 | Localizing the strings, images, and other resources in your apps. |
| 532 | </p> |
| 533 | </li> |
| 534 | |
| 535 | <li> |
| 536 | <p> |
| 537 | Localizing your apps’ store listing details on Google Play. |
| 538 | </p> |
| 539 | </li> |
| 540 | |
| 541 | <li> |
| 542 | <p> |
| 543 | Localizing the apps’ graphic assets, screenshots, and videos that |
| 544 | accompany your store listing. |
| 545 | </p> |
| 546 | </li> |
| 547 | </ul> |
| 548 | |
| 549 | <p> |
| 550 | See <a href= |
| 551 | "{@docRoot}distribute/tools/localization-checklist.html">Localization |
| 552 | Checklist</a> for key steps and considerations in the localization process. |
| 553 | </p> |
| 554 | |
| 555 | <p> |
| 556 | To localize your store listing, first create and finalize your app title, |
| 557 | description, and promotional text. Collect and send all of these for |
| 558 | localization. You can optionally translate the "Recent Changes" text for app |
| 559 | updates as well. Later you can add your localized listing details in the |
| 560 | Developer Console, or you can choose to let Google Play auto-translate your |
| 561 | listing details into the languages you support. |
| 562 | </p> |
| 563 | |
| 564 | <p> |
| 565 | A key part of making your app listing attractive to a global customer base is |
| 566 | creating localized versions of your promotional graphics, screenshots and |
| 567 | videos. For example, your app's feature graphic might include text that |
| 568 | should be translated, for maximum effectiveness. You can create different |
| 569 | versions of your promotional graphics for each language and upload them to |
| 570 | the Developer Console. If you offer a promotional video, you can create |
| 571 | localized versions of it and then add a link to the correct localized video |
| 572 | for each language you support. |
| 573 | </p> |
| 574 | |
| 575 | <p> |
| 576 | When your translations are complete, move them into your app resources as |
| 577 | needed and test that they are loaded properly. Save your app's translated |
| 578 | listing details for later, when you upload assets and configure the store |
| 579 | listing. |
| 580 | </p> |
| 581 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 582 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 583 | |
| 584 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 585 | "collection:distribute/toolsreference/launchchecklist/localization" |
| 586 | data-sortorder="-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" |
| 587 | data-maxresults="6"> |
| 588 | </div> |
| 589 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 590 | <div class="headerLine"> |
| 591 | <h2 id="prepare-graphics"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 592 | 12. Prepare Promotional Graphics, Screenshots, and Videos |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 593 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 594 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 595 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 596 | </div> |
| 597 | |
| 598 | <p> |
| 599 | When you publish on Google Play, you can supply a variety of high-quality |
| 600 | graphic assets to showcase your app or brand. After you publish, these appear |
| 601 | on your store listing page, search results, and elsewhere. These graphic |
| 602 | assets are key parts of a successful store listing page that attracts and |
| 603 | engages users, so you should consider having a professional produce them for |
| 604 | you. Screenshots and videos are also very important, because they show how |
| 605 | your apps look, how they’re used or played, and what makes them different. |
| 606 | </p> |
| 607 | |
| 608 | <p> |
| 609 | All of your graphic assets should be designed so that they are easy to see |
| 610 | and highlight your apps or brand in a colorful, interesting way. The assets |
| 611 | should reference the same logo and icon as users will find in the All Apps |
| 612 | launcher once they have downloaded the app. Your graphic assets should also |
| 613 | fit in well with the graphic assets of all the apps you publish, which will |
| 614 | be also be displayed to users on your store listing page. |
| 615 | </p> |
| 616 | |
| 617 | <p> |
| 618 | To help you market your apps more effectively to a global audience, Google |
| 619 | Play lets you create localized versions of your promotional graphics, |
| 620 | screenshots, and videos and upload them to the Developer Console. When a user |
| 621 | visits your app's store listing, Google Play displays the promotional |
| 622 | graphic, screenshots, and video that you've provided for the user's language. |
| 623 | </p> |
| 624 | |
| 625 | <p> |
| 626 | To localize your promotional graphics, you can translate any embedded text, |
| 627 | use different imagery or presentation, or change your marketing approach to |
| 628 | best address the needs of users in specific languages. For example, if your |
| 629 | feature or promotional graphic includes an embedded product name or tag line, |
| 630 | you can translate that text and add it to a localized version of the |
| 631 | promotional graphic. |
| 632 | </p> |
| 633 | |
| 634 | <p> |
| 635 | Because your localized graphic assets and videos are so important, you should |
| 636 | get started on creating and localizing them well in advance of your target |
| 637 | publishing date. |
| 638 | </p> |
| 639 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 640 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 641 | |
| 642 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 643 | "collection:distribute/toolsreference/launchchecklist/graphics" data-sortorder= |
| 644 | "-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" data-maxresults="6"> |
| 645 | </div> |
| 646 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 647 | <div class="headerLine"> |
| 648 | <h2 id="build-upload"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 649 | 13. Build and Upload the Release-ready APK |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 650 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 651 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 652 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 653 | </div> |
| 654 | |
| 655 | <p> |
| 656 | When you are satisfied that your apps meet your UI, compatibility, and |
| 657 | quality requirements, you can build the release-ready versions of the apps. |
| 658 | You upload the release-ready APKs to your Developer Console and distribute to |
| 659 | users. |
| 660 | </p> |
| 661 | |
| 662 | <p> |
| 663 | The process for preparing a release-ready APK is the same for all apps, |
| 664 | regardless of how they are distributed. Generally the process includes basic |
| 665 | code cleanup and optimization, building and signing with your release key, |
| 666 | and final testing. |
| 667 | </p> |
| 668 | |
| 669 | <p> |
| 670 | For complete details on how to create a release-ready version of your app, |
| 671 | read <a href="{@docRoot}tools/publishing/preparing.html">Preparing for |
| 672 | Release</a>. |
| 673 | </p> |
| 674 | |
| 675 | <p> |
| 676 | Once you have the release-ready APKs in hand, you can upload them to the |
| 677 | Developer Console. If necessary, you can replace an APK with a more recent |
| 678 | version before publishing. |
| 679 | </p> |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 680 | <!--<h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 681 | |
| 682 | <div class="resource-widget resource-flow-layout col-13" |
| 683 | data-query="collection:distribute/toolsreference/launchchecklist/build" |
| 684 | data-sortOrder="-timestamp" |
| 685 | data-cardSizes="9x3,9x3,6x3,9x3,9x3,9x3" |
| 686 | data-maxResults="6"></div>--> |
| 687 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 688 | <div class="headerLine"> |
| 689 | <h2 id="plan-beta"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 690 | 14. Plan a Beta Release |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 691 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 692 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 693 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 694 | </div> |
| 695 | |
| 696 | <div class="sidebox-wrapper" style="float:right;"> |
| 697 | <div class="sidebox"> |
| 698 | <h2> |
| 699 | Easy beta testing |
| 700 | </h2> |
| 701 | |
| 702 | <p> |
| 703 | Google Play lets you set up groups of alpha and beta testers, anywhere |
| 704 | around the world. Check out this powerful feature next time you sign in |
| 705 | to the Developer Console. |
| 706 | </p> |
| 707 | </div> |
| 708 | </div> |
| 709 | |
| 710 | <p> |
| 711 | Before launching your apps, it's always valuable to get real-world feedback |
| 712 | from users — even more so when you are launching new apps. It's highly |
| 713 | recommended that you distribute a pre-release version of your app to users |
| 714 | across your key markets and provide an easy means for them to provide |
| 715 | feedback and report bugs. |
| 716 | </p> |
| 717 | |
| 718 | <p> |
| 719 | Google Play can help you set up a beta program for your app. After you sign |
| 720 | in to your Developer Console and have upload your APKs, you can set up groups |
| 721 | of users for alpha and beta testing the apps. You can start with a small |
| 722 | group of alpha testers, then move to a larger group of beta testers. Once |
| 723 | users are added, they access your app's store listing and install the app. |
| 724 | <strong>Users on alpha or beta versions cannot leave reviews or |
| 725 | ratings</strong>, so there is <strong>no risk to your rating</strong> on |
| 726 | Google Play. You need to arrange a mechanism for any testing feedback to be |
| 727 | delivered - such as a Google Forum or Google+. |
| 728 | </p> |
| 729 | |
| 730 | <p> |
| 731 | The feedback you receive will help you adjust your UI, translations, and |
| 732 | store listing to ensure a great experience for users. |
| 733 | </p> |
| 734 | <!-- Related resources |
| 735 | |
| 736 | <table> |
| 737 | <tr> |
| 738 | <td>Beta-testing and Staged Rollouts |
| 739 | See how you can facilitate testing with Google Play.</td> |
| 740 | </tr> |
| 741 | </table> --> |
| 742 | |
| 743 | <div class="headerLine"> |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 744 | <h2 id="complete-details"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 745 | 15. Complete the Apps’ Store Listing |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 746 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 747 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 748 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 749 | </div> |
| 750 | |
| 751 | <p> |
| 752 | On Google Play, your apps’ product information is shown to users on their |
| 753 | store listing pages, the pages that users visit to learn more about your apps |
| 754 | and the pages from which they will decide to purchase or download your apps, |
| 755 | on their Android devices or on the web. |
| 756 | </p> |
| 757 | |
| 758 | <p> |
| 759 | Google Play gives you a variety of ways to promote your apps and engage with |
| 760 | users on your store listing pages, from colorful graphics, screenshots, and |
| 761 | videos to localized descriptions, release details, and links to your other |
| 762 | apps. As you prepare to publish your apps, make sure that you take advantage |
| 763 | of all that your product detail pages can offer, making your apps as |
| 764 | compelling as possible to users. |
| 765 | </p> |
| 766 | |
| 767 | <p> |
| 768 | You should begin planning your product pages in advance of your target launch |
| 769 | date, arranging for localized description, high-quality graphic assets, |
| 770 | screenshots and video, and so on. |
| 771 | </p> |
| 772 | |
| 773 | <p> |
| 774 | As you get near your target publishing date, you should become familiar with |
| 775 | all the fields, options, and assets associated with the store listing |
| 776 | configuration page in the Developer Console. As you collect the information |
| 777 | and assets for the page, make sure that you can enter or upload it to the |
| 778 | Developer Console, until the page is complete and ready for publishing. |
| 779 | </p> |
| 780 | |
| 781 | <p> |
| 782 | After you've set your apps’ geographic targeting in the Developer Console, |
| 783 | remember to add your localized store listing, promotional graphics, and so |
| 784 | on, for all of the languages that you support. |
| 785 | </p> |
| 786 | |
| 787 | <p> |
| 788 | If your app is targeting tablet devices, make sure to include at least one |
| 789 | screenshot of the app running on a tablet, and highlight your apps’ support |
| 790 | for tablets in the app description, release notes, promotional campaigns, and |
| 791 | elsewhere. |
| 792 | </p> |
| 793 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 794 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 795 | |
| 796 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 797 | "collection:distribute/toolsreference/launchchecklist/productdetails" |
| 798 | data-sortorder="-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" |
| 799 | data-maxresults="6"> |
| 800 | </div> |
| 801 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 802 | <div class="headerLine"> |
| 803 | <h2 id="use-badges"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 804 | 16. Use Google Play Badges and Links in your Promotional Campaigns |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 805 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 806 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 807 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 808 | </div> |
| 809 | |
| 810 | <p> |
| 811 | Google Play badges give you an officially branded way of promoting your apps |
| 812 | to Android users. Use the <a href= |
| 813 | "{@docRoot}distribute/tools/promote/badges.html">Google Play Badge |
| 814 | generator</a> to quickly create badges to link users to your products from |
| 815 | web pages, ads, reviews, and more. You can also use special <a href= |
| 816 | "{@docRoot}distribute/tools/promote/linking.html">link formats</a> to link |
| 817 | directly to your store listing page, to a list of your products, or to search |
| 818 | results. |
| 819 | </p> |
| 820 | |
| 821 | <p> |
| 822 | To help your apps get traction after launch, it's strongly recommended that |
| 823 | you support launch with a promotional campaign that announces your product |
| 824 | through many channels as possible, in as many countries as possible. For |
| 825 | example, you can promote a launch using ad placements, social network or blog |
| 826 | posts, video and other media, interviews and reviews, or any other channels |
| 827 | available. |
| 828 | </p> |
| 829 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 830 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 831 | |
| 832 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 833 | "collection:distribute/toolsreference/launchchecklist/badges" data-sortorder= |
| 834 | "-timestamp" data-cardsizes="9x3,9x3,6x3,9x3,9x3,9x3" data-maxresults="6"> |
| 835 | </div> |
| 836 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 837 | <div class="headerLine"> |
| 838 | <h2 id="final-checks"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 839 | 17. Final Checks and Publishing |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 840 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 841 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 842 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 843 | </div> |
| 844 | |
| 845 | <p> |
| 846 | When you think you’re ready to publish, sign in to the Developer Console and |
| 847 | take a few moments for a few final checks. |
| 848 | </p> |
| 849 | |
| 850 | <p> |
| 851 | Make sure that: |
| 852 | </p> |
| 853 | |
| 854 | <ul> |
| 855 | <li> |
| 856 | <p> |
| 857 | Your developer profile has the correct information and is linked to the |
| 858 | proper Google Wallet merchant account (if you’re selling products). |
| 859 | </p> |
| 860 | </li> |
| 861 | |
| 862 | <li> |
| 863 | <p> |
| 864 | You have the right version of the apps uploaded. |
| 865 | </p> |
| 866 | </li> |
| 867 | |
| 868 | <li> |
| 869 | <p> |
| 870 | All parts of your store listing are ready, including all graphic assets, |
| 871 | screenshots, video, localized descriptions, and so on. |
| 872 | </p> |
| 873 | </li> |
| 874 | |
| 875 | <li> |
| 876 | <p> |
| 877 | You have set your app's pricing to free or priced. |
| 878 | </p> |
| 879 | </li> |
| 880 | |
| 881 | <li> |
| 882 | <p> |
| 883 | You have set country (and carrier) targeting and priced your products (if |
| 884 | appropriate) in buyer currencies |
| 885 | </p> |
| 886 | </li> |
| 887 | |
| 888 | <li> |
| 889 | <p> |
| 890 | "Compatible devices" shows that your apps are reaching the devices that |
| 891 | you’re targeting. If not, you should check with your development team on |
| 892 | the apps’ requirements and filtering rules. |
| 893 | </p> |
| 894 | </li> |
| 895 | |
| 896 | <li> |
| 897 | <p> |
| 898 | You’ve provided the correct link to your website and the correct support |
| 899 | email address. |
| 900 | </p> |
| 901 | </li> |
| 902 | |
| 903 | <li> |
| 904 | <p> |
| 905 | Your apps don’t violate content policy guidelines. |
| 906 | </p> |
| 907 | </li> |
| 908 | |
| 909 | <li> |
| 910 | <p> |
| 911 | You’ve acknowledged that your apps meets the guidelines for Android |
| 912 | content on Google Play and also US export laws. |
| 913 | </p> |
| 914 | </li> |
| 915 | </ul> |
| 916 | |
| 917 | <p> |
| 918 | Your apps are now ready to publish! |
| 919 | </p> |
| 920 | |
| 921 | <p> |
| 922 | If you’re releasing an update, make sure to read the <a href= |
| 923 | "http://support.google.com/googleplay/android-developer/bin/answer.py?hl=en&answer=113476&topic=2365760&ctx=topic"> |
| 924 | requirements for publishing updates</a>. |
| 925 | </p> |
| 926 | |
| 927 | <p> |
| 928 | When you’re ready, click the <strong>Publish</strong> button in the Developer |
| 929 | Console. Within a few hours, your apps will become available to users and |
| 930 | your product page will appear in Google Play for browsing, searching, or |
| 931 | linking from your promotional campaigns. |
| 932 | </p> |
| 933 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 934 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 935 | |
| 936 | <div class="resource-widget resource-flow-layout col-13" data-query= |
| 937 | "collection:distribute/toolsreference/launchchecklist/finalchecks" |
| 938 | data-sortorder="-timestamp" data-cardsizes="6x3,6x3,6x3,9x3,9x3,9x3" |
| 939 | data-maxresults="6"> |
| 940 | </div> |
| 941 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 942 | <div class="headerLine"> |
| 943 | <h2 id="support-users"> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 944 | 18. Support Users after Launch |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 945 | </h2> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 946 | |
Scott Main | 2f33f97 | 2014-05-19 19:13:45 -0700 | [diff] [blame] | 947 | |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 948 | </div> |
| 949 | |
| 950 | <p> |
| 951 | After you publish apps or app updates, it's crucial for you to support your |
| 952 | customers. Prompt and courteous support can provide a better experience for |
| 953 | users that results in better ratings and more positive reviews for your |
| 954 | products. Users are likely to be more engaged with your app and recommend it |
| 955 | if you’re responsive to their needs and feedback. This is especially true |
| 956 | after publishing if you’re using a coordinated promotional campaign. |
| 957 | </p> |
| 958 | |
| 959 | <p> |
| 960 | There are a number of ways that you can keep in touch with users and offer |
| 961 | them support. The most fundamental is to provide your <em>support email |
| 962 | address</em> on your store listing pages. Beyond that, you can provide |
| 963 | support in any way you choose, such as a forum, mailing list, or a Google+ |
| 964 | page. The Google Play team provides user support for downloading, installing. |
| 965 | and payments issues, but issues that fall outside of these topics will be in |
| 966 | your domain. Examples of issues you can support include: feature requests, |
| 967 | questions about using the apps, and questions about compatibility settings. |
| 968 | </p> |
| 969 | |
| 970 | <p> |
| 971 | After publishing, plan to: |
| 972 | </p> |
| 973 | |
| 974 | <ul> |
| 975 | <li> |
| 976 | <p> |
| 977 | Check your ratings and reviews frequently on your apps’ store listing |
| 978 | pages. Watch for recurring themes that could signal bugs or other issues. |
| 979 | </p> |
| 980 | </li> |
| 981 | |
| 982 | <li> |
| 983 | <p> |
| 984 | Be mindful of new Android platform version launches, as compatibility |
| 985 | settings for your apps might need to be updated. |
| 986 | </p> |
| 987 | </li> |
| 988 | |
| 989 | <li> |
| 990 | <p> |
| 991 | Put a link to your support resources on your website and set up any other |
| 992 | support such as forums. |
| 993 | </p> |
| 994 | </li> |
| 995 | |
| 996 | <li> |
| 997 | <p> |
| 998 | Provide an appropriate support email address on your store listing pages |
| 999 | and respond to users when they take the time to email you. |
| 1000 | </p> |
| 1001 | </li> |
| 1002 | |
| 1003 | <li> |
| 1004 | <p> |
| 1005 | Beyond the automatic refund window offered by Google Play, be generous |
| 1006 | with your own refund policy, as satisfied users will be more likely to |
| 1007 | purchase in the future. |
| 1008 | </p> |
| 1009 | </li> |
| 1010 | |
| 1011 | <li> |
| 1012 | <p> |
| 1013 | Acknowledge and fix issues in your apps. It helps to be transparent and |
| 1014 | list known issues on your store listing pages proactively. |
| 1015 | </p> |
| 1016 | </li> |
| 1017 | |
| 1018 | <li> |
| 1019 | <p> |
| 1020 | Publish updates as frequently as you’re able, without sacrificing quality |
| 1021 | or annoying users with too-frequent updates. |
| 1022 | </p> |
| 1023 | </li> |
| 1024 | |
| 1025 | <li> |
| 1026 | <p> |
| 1027 | With each update, make sure to provide a summary of what's changed. You |
| 1028 | can enter this information in the Developer Console. Users will read it |
| 1029 | and appreciate that you are serious about improving the quality of your |
| 1030 | apps. |
| 1031 | </p> |
| 1032 | </li> |
| 1033 | </ul> |
| 1034 | </ul> |
| 1035 | |
Dirk Dougherty | ccd1e9e | 2014-06-01 21:29:17 -0700 | [diff] [blame] | 1036 | <h3 class="rel-resources clearfloat">Related resources</h3> |
Dirk Dougherty | 3506ac8 | 2014-02-21 11:15:52 -0800 | [diff] [blame] | 1037 | |
| 1038 | <div class="resource-widget resource-flow-layout col-13" |
| 1039 | data-query="collection:distribute/toolsreference/launchchecklist/afterlaunch" |
| 1040 | data-sortOrder="-timestamp" |
| 1041 | data-cardSizes="9x3,9x3,9x3,9x3,9x3,9x3" |
| 1042 | data-maxResults="6"></div> |