diff options
Diffstat (limited to 'docs/html/guide/publishing')
| -rw-r--r-- | docs/html/guide/publishing/app-signing.jd | 10 | ||||
| -rw-r--r-- | docs/html/guide/publishing/preparing.jd | 45 | ||||
| -rw-r--r-- | docs/html/guide/publishing/publishing.jd | 256 | ||||
| -rwxr-xr-x | docs/html/guide/publishing/publishing_overview.jd | 51 | ||||
| -rw-r--r-- | docs/html/guide/publishing/versioning.jd | 2 |
5 files changed, 181 insertions, 183 deletions
diff --git a/docs/html/guide/publishing/app-signing.jd b/docs/html/guide/publishing/app-signing.jd index 9abcdf7..e86ec30 100644 --- a/docs/html/guide/publishing/app-signing.jd +++ b/docs/html/guide/publishing/app-signing.jd @@ -82,7 +82,7 @@ run it or debug it on an emulator or device.</p> use to build your application. There are two build modes: <em>debug mode</em> and <em>release mode</em>. You use debug mode when you are developing and testing your application. You use release mode when you want to build a release version of your application that you can -distribute directly to users or publish on an application marketplace such as Android Market.</p> +distribute directly to users or publish on an application marketplace such as Google Play.</p> <p>When you build in <em>debug mode</em> the Android SDK build tools use the Keytool utility (included in the JDK) to create a debug key. Because the SDK build tools created the debug key, @@ -158,10 +158,10 @@ you should ensure that your key's validity period exceeds the expected lifespan of <em>all versions of all of the applications</em>, including dependent applications that may be added to the suite in the future. </li> -<li>If you plan to publish your application(s) on Android Market, the +<li>If you plan to publish your application(s) on Google Play, the key you use to sign the application(s) must have a validity period -ending after 22 October 2033. The Market server enforces this requirement -to ensure that users can seamlessly upgrade Market applications when +ending after 22 October 2033. Google Play enforces this requirement +to ensure that users can seamlessly upgrade applications when new versions are available. </li> </ul> @@ -292,7 +292,7 @@ key is one that:</p> with the application</li> <li>Has a validity period that exceeds the expected lifespan of the application or application suite. A validity period of more than 25 years is recommended. -<p>If you plan to publish your application(s) on Android Market, note that a +<p>If you plan to publish your application(s) on Google Play, note that a validity period ending after 22 October 2033 is a requirement. You can not upload an application if it is signed with a key whose validity expires before that date. </p></li> diff --git a/docs/html/guide/publishing/preparing.jd b/docs/html/guide/publishing/preparing.jd index c355479..fe56352 100644 --- a/docs/html/guide/publishing/preparing.jd +++ b/docs/html/guide/publishing/preparing.jd @@ -22,7 +22,7 @@ page.title=Preparing for Release <ol> <li><a href="{@docRoot}guide/publishing/publishing_overview.html">Publishing Overview</a></li> <li><a href="{@docRoot}guide/publishing/app-signing.html">Signing Your Applications</a></li> - <li><a href="{@docRoot}guide/publishing/publishing.html">Publishing on Android Market</a></li> + <li><a href="{@docRoot}guide/publishing/publishing.html">Publishing on Google Play</a></li> </ol> </div> </div> @@ -39,13 +39,13 @@ similar to the debug build process and can be done using JDK and Android SDK too tasks serve as a final check, ensuring that your application performs as expected under real-world conditions. When you are finished preparing your application for release you have a signed <code>.apk</code> file, which you can distribute directly to users or distribute through an -application marketplace such as Android Market.</p> +application marketplace such as Google Play.</p> <p>This document summarizes the main tasks you need to perform to prepare your application for release. The tasks that are described in this document apply to all Android applications regardless -how they are released or distributed to users. If you are releasing your application through Android -Market, you should also read <a href="{@docRoot}guide/publishing/publishing.html">Publishing on -Android Market</a> to be sure your release-ready application satisfies all Android Market +how they are released or distributed to users. If you are releasing your application through Google +Play, you should also read <a href="{@docRoot}guide/publishing/publishing.html">Publishing on +Google Play</a> to be sure your release-ready application satisfies all Google Play requirements.</p> <p class="note"><strong>Note:</strong> As a best practice, your application should meet all of your @@ -89,9 +89,9 @@ line.</p> <p>To prepare your application for release you typically perform five main tasks (see figure 2). Each main task may include one or more smaller tasks depending on how you are releasing your -application. For example, if you are releasing your application through Android Market you may want +application. For example, if you are releasing your application through Google Play you may want to add special filtering rules to your manifest while you are configuring your application for -release. Similarly, to meet Android Market publishing guidelines you may have to prepare screenshots +release. Similarly, to meet Google Play publishing guidelines you may have to prepare screenshots and create promotional text while you are gathering materials for release.</p> <p>You usually perform the tasks listed in figure 2 after you have throroughly debugged and tested @@ -137,9 +137,9 @@ key</a>.</p> href="{@docRoot}guide/practices/ui_guidelines/icon_design_launcher.html">icon guidelines</a>. Your application's icon helps users identify your application on a device's Home screen and in the Launcher window. It also appears in Manage Applications, My Downloads, and -elsewhere. In addition, publishing services such as Android Market display your icon to users.</p> +elsewhere. In addition, publishing services such as Google Play display your icon to users.</p> -<p class="note"><strong>Note:</strong> If you are releasing your application on Android Market, you +<p class="note"><strong>Note:</strong> If you are releasing your application on Google Play, you need to create a high resolution version of your icon. See <a href="https://www.google.com/support/androidmarket/developer/bin/answer.py?answer=1078870">Graphic @@ -154,7 +154,7 @@ with your application.</p> <h4>Miscellaneous Materials</h4> <p>You might also have to prepare promotional and marketing materials to publicize your application. -For example, if you are releasing your application on Android Market you will need to prepare some +For example, if you are releasing your application on Google Play you will need to prepare some promotional text and you will need to create screenshots of your application. For more information, see <a href="https://www.google.com/support/androidmarket/developer/bin/answer.py?answer=1078870"> @@ -242,11 +242,11 @@ tasks:</p> </ul> <p>There are several additional manifest elements that you can set if you are releasing your -application on Android Market. For example, the <code>android:minSdkVersion</code> and +application on Google Play. For example, the <code>android:minSdkVersion</code> and <code>android:targetSdkVersion</code> attributes, which are located in the <a href="{@docRoot}guide/topics/manifest/uses-sdk-element.html"> <uses-sdk></a> element. For more -information about these and other Android Market settings, see <a -href="{@docRoot}/guide//appendix/market-filters.html">Market Filters</a>.</p> +information about these and other Google Play settings, see <a +href="{@docRoot}/guide//appendix/market-filters.html">Filters on Google Play</a>.</p> <h4>Address compatibility issues</h4> @@ -283,16 +283,15 @@ doing the following:</p> <p>If your application accesses remote servers or services, make sure you are using the production URL or path for the server or service and not a test URL or path.</p> -<h4>Implement Licensing (if you are releasing on Android Market)</h4> +<h4>Implement Licensing (if you are releasing on Google Play)</h4> -<p>If you are releasing a paid application through Android Market, consider adding support for -Android Market Licensing. Licensing lets you control access to your application based on whether the -current user has purchased it. Using Android Market Licensing is optional even if you are -releasing your app through Android Market.</p> +<p>If you are releasing a paid application through Google Play, consider adding support for +Google Play Licensing. Licensing lets you control access to your application based on whether the +current user has purchased it. Using Google Play Licensing is optional even if you are +releasing your app through Google Play.</p> -<p>For more information about Android Market Licensing Service and how to use it in your -application, see <a href="{@docRoot}guide/market/licensing/index.html">Application -Licensing</a>.</p> +<p>For more information about Google Play Licensing Service and how to use it in your +application, see <a href="{@docRoot}guide/market/licensing.html">Application Licensing</a>.</p> <h2 id="publishing-build">Building Your Application for Release</h2> @@ -353,7 +352,7 @@ a summary of common Android situations that you should consider when you are tes done testing and you are satisfied that the release version of your application behaves correctly, you can release your application to users. For more information, see <a href="{@docRoot}guide/publishing/publishing_overview.html#publishing-release">Releasing Your -Application to Users</a>. If you are publishing your application on Android Market, see -<a href="{@docRoot}guide/publishing/publishing.html">Publishing on Android Market</a>.</p> +Application to Users</a>. If you are publishing your application on Google Play, see +<a href="{@docRoot}guide/publishing/publishing.html">Publishing on Google Play</a>.</p> diff --git a/docs/html/guide/publishing/publishing.jd b/docs/html/guide/publishing/publishing.jd index 27a87f9..952e602 100644 --- a/docs/html/guide/publishing/publishing.jd +++ b/docs/html/guide/publishing/publishing.jd @@ -1,4 +1,4 @@ -page.title=Publishing on Android Market +page.title=Publishing on Google Play @jd:body <div id="qv-wrapper"> @@ -7,25 +7,25 @@ page.title=Publishing on Android Market <h2>Quickview</h2> <ul> -<li>Learn how to publish and update apps on Android Market.</li> -<li>Find out how to create links to apps that are published on Android Market.</li> -<li>Learn about Android Market features.</li> +<li>Learn how to publish and update apps on Google Play.</li> +<li>Find out how to create links to apps that are published on Google Play.</li> +<li>Learn about Google Play features.</li> </ul> <h2>In this document</h2> <ol> -<li><a href="#overview">About Android Market</a> -<li><A href="#marketpublish">Publishing Apps on Android Market</a></li> -<li><a href="#marketupgrade">Publishing Updates on Android Market</a></li> -<li><a href="#marketLicensing">Using Android Market Licensing Service</a></li> -<li><a href="#marketinappbilling">Using Android Market In-app Billing</a></li> -<li><a href="#marketintent">Linking to Your Apps on Android Market</a> +<li><a href="#overview">About Google Play</a> +<li><A href="#marketpublish">Publishing Apps on Google Play</a></li> +<li><a href="#marketupgrade">Publishing Updates on Google Play</a></li> +<li><a href="#marketLicensing">Using Google Play Licensing Service</a></li> +<li><a href="#marketinappbilling">Using Google Play In-app Billing</a></li> +<li><a href="#marketintent">Linking to Your Apps on Google Play</a> <ol> <li><a href="#OpeningDetails">Opening an app's details page</a></li> <li><a href="#PerformingSearch">Performing a search</a></li> - <li><a href="#BuildaButton">Build an Android Market button</a></li> + <li><a href="#BuildaButton">Build a Google Play button</a></li> <li><a href="#UriSummary">Summary of URI formats</a></li> </ol> </li> @@ -41,9 +41,9 @@ page.title=Publishing on Android Market <div id="qv-extra"> <img id="rule" src="{@docRoot}assets/images/grad-rule-qv.png"> <div id="qv-sub-rule"> - <img src="{@docRoot}assets/images/icon_market.jpg" style="float:left;margin:0;padding:0 5px;"> - <h2 style="color:#669999;">Already know about Android Market and want to get started?</h2> - <p>Go to <a href="http://market.android.com/publish">Android Market</a>, create a developer + <img src="{@docRoot}assets/images/icon_play.png" style="float:left;margin:0;padding:0 5px;"> + <h2 style="color:#669999;">Already know about Google Play and want to get started?</h2> + <p>Go to <a href="http://play.google.com/apps/publish">Google Play</a>, create a developer account, and upload your application. For more information about required assets, listing details, and publishing options, see <a href="http://market.android.com/support/bin/answer.py?answer=113469">Upload @@ -55,78 +55,78 @@ Applications</a>.</p> </div> <p>One of the most effective ways to get your application into users' hands is to -publish it on an application marketplace like Android Market. Publishing on Android Market is a +publish it on an application marketplace like Google Play. Publishing on Google Play is a straightforward process that you can do in just a few simple steps—register, configure, upload, and publish. Registration takes only a few minutes and needs to be done only once. -The configuration and publishing steps can all be done through the Android Market Developer Console -after you register as an Android Market developer.</p> +The configuration and publishing steps can all be done through the Google Play Android Developer Console +after you register as a Google Play developer.</p> -<p>To start publishing on Android Market, first read this topic and then go to the <a -href="https://market.android.com/publish/signup">Android Market publisher site</a> and register as -an Android Market developer.</p> +<p>To start publishing on Google Play, first read this topic and then go to the <a +href="https://play.google.com/apps/publish">Google Play Android Developer Console</a> and register as +a Google Play developer.</p> -<h2 id="overview">About Android Market</h2> +<h2 id="overview">About Google Play</h2> -<p>Android Market is a robust publishing platform that helps you publicize, sell, and distribute +<p>Google Play is a robust publishing platform that helps you publicize, sell, and distribute your Android applications to users around the world. When you release your applications through -Android Market you have access to a suite of developer tools that let you analyze your sales, +Google Play you have access to a suite of developer tools that let you analyze your sales, identify market trends, and control who your applications are being distributed to. You also have access to several revenue-enhancing features, such as <a href="{@docRoot}guide/market/billing/index.html">in-app billing</a> and <a href="{@docRoot}guide/market/licensing/index.html">application licensing</a>.</p> -<p>Before you can publish applications on Android Market, you need to <a -href="http://market.android.com/publish">register</a> as an Android Market developer. During the +<p>Before you can publish applications on Google Play, you need to <a +href="http://play.google.com/apps/publish">register</a> as a Google Play developer. During the registration process you will need to create a developer profile, pay a registration fee, and agree -to the <a href="http://www.android.com/us/developer-distribution-agreement.html">Android Market -Developer Distribution Agreement</a>. After you register you can access the Android Market Developer +to the <a href="http://www.android.com/us/developer-distribution-agreement.html">Google Play +Developer Distribution Agreement</a>. After you register you can access the Developer Console, where you can upload applications, configure publishing options, and monitor publishing data. If you want to sell your applications or use the in-app billing feature, you will also need to set up a Google Checkout merchant account. For more information about the registration process, see <a href="https://support.google.com/androidmarket/developer/bin/answer.py?hl=en&answer=113468"> Developer Registration</a>.</p> -<h2 id="marketpublish">Publishing Apps on Android Market</h2> +<h2 id="marketpublish">Publishing Apps on Google Play</h2> -<p>Publishing your application on Android Market is a simple process that involves three basic +<p>Publishing your application on Google Play is a simple process that involves three basic tasks (see figure 1):</p> <ul> <li>Creating various graphical assets that -accompany your app on Android Market.</li> - <li>Using the Android Market <a -href="http://market.android.com/publish">Developer Console</a> to configure publishing options, -specify listing details, and upload your app and graphical assets to Android Market.</li> +accompany your app on Google Play.</li> + <li>Using the Google Play <a +href="http://play.google.com/apps/publish">Developer Console</a> to configure publishing options, +specify listing details, and upload your app and graphical assets to Google Play.</li> <li>Reviewing your publishing settings and changing the release status of your app from Unpublished to Published.</li> </ul> <img src="{@docRoot}images/publishing/publishing_android_market.png" - alt="Shows the three steps that are required to publish on Android Market" + alt="Shows the three steps that are required to publish on Google Play" height="168" id="figure1" /> <p class="img-caption"> - <strong>Figure 1.</strong> To publish apps on Android Market you must first <a + <strong>Figure 1.</strong> To publish apps on Google Play you must first <a href="{@docRoot}guide/publishing/preparing.html">prepare your app for release</a> and then perform three simple tasks. </p> <p class="caution"><strong>Important:</strong> You must <a href="{@docRoot}guide/publishing/preparing.html">prepare your application for release</a> before you -can publish it on Android Market. When you prepare your application for release you configure it for +can publish it on Google Play. When you prepare your application for release you configure it for release and build it in release mode. Building in release mode signs your application's {@code .apk} -file with your private release key. You cannot publish an application on Android Market unless it is +file with your private release key. You cannot publish an application on Google Play unless it is signed with your own private release key.</p> <h3>Preparing promotional materials</h3> -<p>To fully leverage the marketing and publicity capabilities of Android Market, you need to create -several graphical assets that accompany your app on Android Market, such as screenshots, videos, +<p>To fully leverage the marketing and publicity capabilities of Google Play, you need to create +several graphical assets that accompany your app on Google Play, such as screenshots, videos, promotional graphics, and promotional text. At a minimum you must provide two screenshots of your application and a high resolution application icon. The screenshots are displayed on the details -page for your application in Android Market, and the high resolution application icon is displayed -in various locations throughout Android Market. The high resolution icon does not replace the +page for your application on Google Play, and the high resolution application icon is displayed +in various locations throughout Google Play. The high resolution icon does not replace the launcher icon for your application, rather, it serves as a supplemental icon and should look the same as your launcher icon. Promotional video, graphics, and text are optional, although we strongly recommended that you prepare these for your @@ -136,8 +136,8 @@ Assets for your Application</a>.</p> <h3>Configuring options and uploading assets</h3> -<p>Android Market lets you target your application to a worldwide pool of users and devices. To -reach these users you can use the Android Market Developer Console to configure various publishing +<p>Google Play lets you target your application to a worldwide pool of users and devices. To +reach these users you can use the Developer Console to configure various publishing options and listing details for your app. For example, you can choose the <a href="http://support.google.com/androidmarket/developer/bin/answer.py?hl=en&answer=138294&topic= 2365624&ctx=topic">countries</a> you want to reach, the listing languages you want to use, and the @@ -155,11 +155,11 @@ href="http://grendel.sea.corp.google.com:48014/guide/market/billing/billing_admi app.</p> <p>When you are finished setting publishing options and listing details, you can upload your assets -and your application to Android Market. You can also upload your application as a draft +and your application to Google Play. You can also upload your application as a draft (unpublished) application, which lets you do final testing before you publish it for final release.</p> -<p>To learn more about Android Market publishing settings, see the following resources:</p> +<p>To learn more about Google Play publishing settings, see the following resources:</p> <ul> <li><a @@ -181,20 +181,20 @@ pricing, payouts, and exchange rates work.</li> <p>When you are satisfied that your publishing settings are correctly configured and your uploaded application is ready to be released to the public, you can simply click <strong>Publish</strong> in the Developer Console to make your app available for download -around the world. Keep in mind, it can take several hours for your app to appear on Android -Market after you click <strong>Publish</strong> in the Developer Console.</p> +around the world. Keep in mind, it can take several hours for your app to appear on Google +Play after you click <strong>Publish</strong> in the Developer Console.</p> <h3>Controlling Distribution to Devices</h3> <p>If your application targets different device configurations, you can control which Android-powered -devices have access to your application on Android Market by -using Android Market filters. Filtering compares device configurations that you declare in your +devices have access to your application on Google Play by +using Google Play filters. Filtering compares device configurations that you declare in your app's manifest file to the configuration defined by a device. For example, if you declare the camera -filter in your manifest, only those devices that have a camera will see your app on Android -Market. Filters must be configured in your application's manifest file when you are <a +filter in your manifest, only those devices that have a camera will see your app on Google +Play. Filters must be configured in your application's manifest file when you are <a href="{@docRoot}guide/publishing/preparing.html">preparing your app for release</a> (that is, before -you upload your app to Android Market). For more information, see <a -href="{@docRoot}guide/appendix/market-filters.html">Market Filters</a>.</p> +you upload your app to Google Play). For more information, see <a +href="{@docRoot}guide/appendix/market-filters.html">Filters on Google Play</a>.</p> <p>You can also use the multiple APK feature to distribute different {@code .apk} files under the same application listing and the same package name; however, you should use this option only as a last @@ -205,17 +205,17 @@ few cases, however, a single APK is unable to support all device configurations, resources make the APK file too big (greater than 50MB) or other technical challenges prevent a single APK from working on all devices. Although we encourage you to develop and publish a single APK that supports as many device configurations as possible, doing so is sometimes -not possible. To help you publish your application for as many devices as possible, Android Market -allows you to publish multiple APKs under the same application listing. Android Market then supplies +not possible. To help you publish your application for as many devices as possible, Google Play +allows you to publish multiple APKs under the same application listing. Google Play then supplies each APK to the appropriate devices based on configuration support you've declared in the manifest file of each APK. To use this feature, you need to build your separate {@code .apk} files when you are <a href="{@docRoot}guide/publishing/preparing.html">preparing your app for release</a> (that is, before -you upload your app to Android Market). For more information, see <a +you upload your app to Google Play). For more information, see <a href="{@docRoot}guide/market/publishing/multiple-apks.html">Multiple APK Support</a>.</p> -<h2 id="marketupgrade">Publishing Updates on Android Market</h2> +<h2 id="marketupgrade">Publishing Updates on Google Play</h2> -<p>At any time after publishing an application on Android Market, you can upload +<p>At any time after publishing an application on Google Play, you can upload and publish an update to the same application package. When you publish an update to an application, users who have already installed the application may receive a notification that an update is @@ -228,49 +228,49 @@ attributes in the <a href="{@docRoot}guide/topics/manifest/manifest-element.html"><code><manifest></code></a> element of the manifest file. Also, the package name must be the same as the existing version and the {@code .apk} file must be signed with the same private key. If the package name and signing -certificate do <em>not</em> match those of the existing version, Market will +certificate do <em>not</em> match those of the existing version, Google Play will consider it a new application, publish it as such, and will not offer it to existing users as an update.</p> -<p>If you plan to publish your application on Android Market, you must make sure - that it meets the requirements listed below, which are enforced by the Market - server when you upload the application.</p> +<p>If you plan to publish your application on Google Play, you must make sure + that it meets the requirements listed below, which are enforced by Google Play + when you upload the application.</p> -<h2 id="marketLicensing">Using Android Market Licensing Service</h2> +<h2 id="marketLicensing">Using Google Play Licensing Service</h2> -<p>Android Market offers a licensing service that lets you enforce licensing -policies for paid applications that you publish through Android Market. With -Android Market Licensing, your applications can query Android Market at runtime +<p>Google Play offers a licensing service that lets you enforce licensing +policies for paid applications that you publish through Google Play. With +Google Play Licensing, your applications can query Google Play at runtime to obtain the licensing status for the current user, then allow or disallow further use of the application as appropriate. Using the service, you can apply a flexible licensing policy on an application-by-application basis—each application can enforce its licensing status in the way most appropriate for it. </p> -<p>Any application that you publish through Android Market can use the Android -Market Licensing Service. The service uses no dedicated framework APIs, so you can +<p>Any application that you publish through Google Play can use the Google +Play Licensing Service. The service uses no dedicated framework APIs, so you can add licensing to any application that uses a minimum API Level of 3 or higher.</p> -<p>For complete information about Android Market Licensing Service and how to +<p>For complete information about Google Play Licensing Service and how to use it in your application, read <a href="{@docRoot}guide/market/licensing/index.html">Application Licensing</a>.</p> -<h2 id="marketinappbilling">Using Android Market In-app Billing</h2> +<h2 id="marketinappbilling">Using Google Play In-app Billing</h2> -<p><a href="{@docRoot}guide/market/billing/billing_overview.html">Android Market In-app Billing</a> -is an Android Market service that lets you sell digital content in your applications. You can use +<p><a href="{@docRoot}guide/market/billing/billing_overview.html">Google Play In-app Billing</a> +is a Google Play service that lets you sell digital content in your applications. You can use the service to sell a wide range of content, including downloadable content such as media files or photos, and virtual content such as game levels or potions.</p> -<p>When you use Android Market's in-app billing service to sell an item, Android Market handles all +<p>When you use Google Play's in-app billing service to sell an item, Google Play handles all billing details so your application never has to directly process any financial transactions. -Android Market uses the same checkout service that is used for application purchases, so your users +Google Play uses the same checkout service that is used for application purchases, so your users experience a consistent and familiar purchase flow (see figure 1). Also, the transaction fee for in-app purchases is the same as the transaction fee for application purchases (30%).</p> -<p>Any application that you publish through Android Market can implement in-app billing. No special -account or registration is required other than an Android Market publisher account and a Google +<p>Any application that you publish through Google Play can implement in-app billing. No special +account or registration is required other than a Google Play publisher account and a Google Checkout Merchant account. Also, because the service uses no dedicated framework APIs, you can add in-app billing to any application that uses a minimum API level of 4 or higher.</p> @@ -282,53 +282,53 @@ also contains examples of the database, user interface, and business logic you m implement in-app billing. For more information about the in-app billing feature, see the <a href="{@docRoot}guide/market/billing/index.html">In-app Billing documentation</a>.</p> -<h2 id="marketintent">Linking to Your Apps on Android Market</h2> +<h2 id="marketintent">Linking to Your Apps on Google Play</h2> -<p>To help users discover your published applications, you can use two special Android Market URIs +<p>To help users discover your published applications, you can use two special Google Play URIs that direct users to your application's details page or perform a search for all of your published -applications in Android Market. You can use these URIs to create a button in your application or a +applications on Google Play. You can use these URIs to create a button in your application or a link on a web page that:</p> <ul> - <li>Opens your application's details page in the Android Market application or web site.</li> - <li>Searches for all your published applications in the Android Market application or web + <li>Opens your application's details page in the Google Play application or web site.</li> + <li>Searches for all your published applications in the Google Play application or web site.</li> </ul> -<p>You can launch the Android Market application or web site in the following ways:</p> +<p>You can launch the Google Play application or web site in the following ways:</p> <ul> <li>Initiate an {@link android.content.Intent} from your application that launches the -Android Market application on the user's device.</li> - <li>Provide a link on a web page that opens the Android Market web site (but will also -open the Android Market application if clicked from a device).</li> +Google Play application on the user's device.</li> + <li>Provide a link on a web page that opens the Google Play web site (but will also +open the Google Play application if clicked from a device).</li> </ul> <p>In both cases, whether you want to initiate the action from your application or from a web page, the URIs are quite similar. The only difference is the URI prefix.</p> -<p>To open the Android Market application from your application, the prefix for the intent's data +<p>To open the Google Play application from your application, the prefix for the intent's data URI is:</p> <p style="margin-left:2em"><code>market://</code></p> -<p>To open Android Market from your web site, the prefix for the link URI is:</p> +<p>To open Google Play store from your web site, the prefix for the link URI is:</p> -<p style="margin-left:2em"><code>http://market.android.com/</code></p> +<p style="margin-left:2em"><code>http://play.google.com/store/</code></p> <p>The following sections describe how to create a complete URI for each action.</p> -<p class="note"><strong>Note:</strong> If you create a link to open Android Market from your web -site and the user selects it from an Android-powered device, the device's Market application will -resolve the link so the user can use the Market application instead of opening the web -site. As such, you should always use {@code http://market.android.com/} URIs when creating a link on +<p class="note"><strong>Note:</strong> If you create a link to open Google Play from your web +site and the user selects it from an Android-powered device, the device's Google Play application will +resolve the link so the user can use the Google Play application on the device instead of opening the web +site. As such, you should always use {@code http://play.google.com/store/...} URIs when creating a link on a web page. When pointing to your apps from within your Android app, use the -{@code market://} URIs in an intent, so that the Market application always opens.</p> +{@code market://} URIs in an intent, so that the Google Play application always opens.</p> <h3 id="OpeningDetails">Opening an app's details page</h3> <p>As described above, you can open the details page for a specific application either on the -Android Market application or the Android Market web site. The details page allows the user to see +Google Play application or the Google Play web site. The details page allows the user to see the application description, screenshots, reviews and more, and choose to install it.</p> <p>The format for the URI that opens the details page is:</p> @@ -344,14 +344,14 @@ package}</a> attribute of the <a href="{@docRoot}guide/topics/manifest/manifest- <h4>Opening the app details page from your Android app</h4> -<p>To open the Android Market details page from your application, +<p>To open the Google Play details page from your application, create an intent with the {@link android.content.Intent#ACTION_VIEW} action and include a data URI in this format:</p> <p style="margin-left:2em"><code>market://details?id=<package_name></code></p> <p>For example, here's how you can create an intent and open an application's details page in -Android Market:</p> +Google Play:</p> <pre> Intent intent = new Intent(Intent.ACTION_VIEW); @@ -359,7 +359,7 @@ intent.setData(Uri.parse("market://details?id=com.android.example")); startActivity(intent); </pre> -<p>This will open the Android Market application on the device to view the {@code +<p>This will open the Google Play application on the device to view the {@code com.android.example} application.</p> @@ -369,32 +369,32 @@ com.android.example} application.</p> format:</p> <p style="margin-left:2em"> - <code>http://market.android.com/details?id=<package_name></code> + <code>http://play.google.com/store/details?id=<package_name></code> </p> -<p>For example, here's a link that opens an application's details page on Android Market:</p> +<p>For example, here's a link that opens an application's details page on Google Play:</p> <pre> -<a href="http://market.android.com/details?id=com.android.example">App Link</a> +<a href="http://play.google.com/store/details?id=com.android.example">App Link</a> </pre> -<p>When clicked from a desktop web browser, this opens the Android Market web site to view the +<p>When clicked from a desktop web browser, this opens the Google Play web site to view the {@code com.android.example} application. When clicked from an Android-powered device, users are -given the option to use either their web browser or the Android Market application to view the +given the option to use either their web browser or the Google Play application to view the application.</p> <h3 id="PerformingSearch">Performing a search</h3> -<p>To initiate a search in Android Market, the format for the URI is:</p> +<p>To initiate a search on Google Play, the format for the URI is:</p> <p style="margin-left:2em"> <code><URI_prefix><b>search?q=</b><query></code> </p> -<p>The <code><query></code> is a placeholder for the search query to execute in Android -Market. The query can be a raw text string or you can include a parameter that performs a search +<p>The <code><query></code> is a placeholder for the search query to execute in Google +Play. The query can be a raw text string or you can include a parameter that performs a search based on the publisher name:</p> <ul> @@ -410,14 +410,14 @@ by the publisher name: <h4>Searching from your Android app</h4> -<p>To initiate a search on Android Market from your application, create an intent with the +<p>To initiate a search on Google Play from your application, create an intent with the {@link android.content.Intent#ACTION_VIEW} action and include a data URI in this format:</p> <p style="margin-left:2em"><code>market://search?q=<query></code></p> <p>The query may include the {@code pub:} parameter described above.</p> -<p>For example, here's how you can initiate a search in the Android Market application, based on the +<p>For example, here's how you can initiate a search in the Google Play application, based on the publisher name:</p> <pre> @@ -426,43 +426,43 @@ intent.setData(Uri.parse("market://search?q=pub:Your Publisher Name")); startActivity(intent); </pre> -<p>This opens the Android Market application to perform the search. The search result shows all +<p>This opens the Google Play application to perform the search. The search result shows all applications published by the publisher that are compatible with the current device.</p> <h4>Searching from a web site</h4> -<p>To initiate a search on Android Market from your web site, create a link with a URI in this +<p>To initiate a search on Google Play from your web site, create a link with a URI in this format:</p> <p style="margin-left:2em"> - <code>http://market.android.com/search?q=<query></code> + <code>http://play.google.com/store/search?q=<query></code> </p> <p>The query may include the {@code pub:} parameter described above.</p> -<p>For example, here's a link that initiates a search on Android Market, based on the +<p>For example, here's a link that initiates a search on Google Play, based on the publisher name:</p> <pre> -<a href="http://market.android.com/search?q=pub:Your Publisher Name">Search Link</a> +<a href="http://play.google.com/store/search?q=pub:Your Publisher Name">Search Link</a> </pre> -<p>When clicked from a desktop web browser, this opens the Android Market web site and performs the +<p>When clicked from a desktop web browser, this opens the Google Play web site and performs the search. When clicked from an Android-powered device, users are given the option to use either their -web browser or the Android Market application to perform the search.</p> +web browser or the Google Play application to perform the search.</p> -<h3 id="BuildaButton">Build an Android Market button</h3> +<h3 id="BuildaButton">Build a Google Play button</h3> -<p>Use the following form to generate an "Available in Android Market" button that you can use on +<p>Use the following form to generate an "Available on Google Play" button that you can use on your web site. Input either your application's package name or publisher name and the button will -take users to Android Market to either view your application's information or view a list of -your published apps. If users click the button while on an Android-powered device, the Android -Market application will respond to show users your application(s).</p> +take users to Google Play to either view your application's information or view a list of +your published apps. If users click the button while on an Android-powered device, the Google +Play application will respond to show users your application(s).</p> -<p>This form offers four versions of the official "Available in Android Market" button at +<p>This form offers four versions of the official "Available on Google Play" button at recommended sizes. If you want to create a different size, you can download an EPS file for the button images from the <a href="http://www.android.com/branding.html">Android Brand Guidelines</a>.</p> @@ -507,18 +507,18 @@ div.button-row input { // variables for creating 'try it out' demo button var imagePath = "http://www.android.com/images/brand/" -var linkStart = "<a href=\"http://market.android.com/"; +var linkStart = "<a href=\"http://play.google.com/store/"; var imageStart = "\">\n" + " <img src=\"" + imagePath; var imageEnd = ".png\"\n" - + " alt=\"Available in Android Market\" />\n</a>"; + + " alt=\"Available on Google Play\" />\n</a>"; // variables for creating code snippet -var linkStartCode = "<a href=\"http://market.android.com/"; +var linkStartCode = "<a href=\"http://play.google.com/store/"; var imageStartCode = "\">\n" + " <img src=\"" + imagePath; var imageEndCode = ".png\"\n" - + " alt=\"Available in Android Market\" />\n</a>"; + + " alt=\"Available on Google Play\" />\n</a>"; /** Generate the HTML snippet and demo based on form values */ function buildButton(form) { @@ -658,7 +658,7 @@ style="font-family:monospace;background-color:#efefef;padding:5px;display:none;m <h3 id="UriSummary">Summary of URI formats</h3> -<p>The table below provides a summary of the URIs currently supported by the Android Market (both on +<p>The table below provides a summary of the URIs currently supported by the Google Play (both on the web and in the Android application), as discussed in the previous sections.</p> <table> @@ -670,19 +670,19 @@ the web and in the Android application), as discussed in the previous sections.< <tr> <td>Display the details screen for a specific application</td> -<td><code>http://market.android.com/details?id=<package_name></code> +<td><code>http://play.google.com/store/details?id=<package_name></code> <td><code>market://details?id=<package_name></code></td> </tr> <tr> <td>Search for applications using a general string query.</td> -<td><code>http://market.android.com/search?q=<query></code></td> +<td><code>http://play.google.com/store/search?q=<query></code></td> <td><code>market://search?q=<query></code></td> </tr> <tr> <td>Search for applications by publisher name</td> -<td><nobr><code>http://market.android.com/search?q=pub:<publisher_name></code></nobr></td> +<td><nobr><code>http://play.google.com/store/search?q=pub:<publisher_name></code></nobr></td> <td><nobr><code>market://search?q=pub:<publisher_name></code></nobr></td> </tr> diff --git a/docs/html/guide/publishing/publishing_overview.jd b/docs/html/guide/publishing/publishing_overview.jd index c94d201..6fb77e1 100755 --- a/docs/html/guide/publishing/publishing_overview.jd +++ b/docs/html/guide/publishing/publishing_overview.jd @@ -14,7 +14,7 @@ page.title=Publishing Overview <li><a href="#publishing-prepare">Preparing Your Application for Release</a></li> <li><a href="#publishing-release">Releasing Your Application to Users</a> <ol> - <li><a href="#publishing-market">Releasing on Android Market</a></li> + <li><a href="#publishing-market">Releasing on Google Play</a></li> <li><a href="#publishing-website">Releasing on your own website</a></li> <li><a href="#publishing-email">Releasing through email</a></li> </ol> @@ -23,7 +23,7 @@ page.title=Publishing Overview <ol> <li><a href="{@docRoot}guide/publishing/preparing.html">Preparing for Release</a></li> - <li><a href="{@docRoot}guide/publishing/publishing.html">Publishing on Android Market</a></li> + <li><a href="{@docRoot}guide/publishing/publishing.html">Publishing on Google Play</a></li> </ol> </div> </div> @@ -42,7 +42,7 @@ publish an Android application you perform two main tasks:</p> </li> </ul> -<p>Usually, you release your application through an application marketplace, such as Android Market. +<p>Usually, you release your application through an application marketplace, such as Google Play. However, you can also release applications by sending them directly to users or by letting users download them from your own website.</p> @@ -73,7 +73,7 @@ tasks:</p> <code>android:versionCode</code> and <code>android:versionName</code> attributes, which are located in the <a href="{@docRoot}guide/topics/manifest/manifest-element.html"><manifest></a> - element. You may also have to configure several other settings to meet Android Market + element. You may also have to configure several other settings to meet Google Play requirements or accomodate whatever method you're using to release your application.</p> </li> <li>Building and signing a release version of your application. @@ -114,28 +114,27 @@ application.</p> <h2 id="publishing-release">Releasing Your Application to Users</h2> <p>You can release your Android applications several ways. Usually, you release applications -through an application marketplace, such as Android Market, but you can also release applications -on your own website or by sending an application directly to a user. Android Market is the +through an application marketplace, such as Google Play, but you can also release applications +on your own website or by sending an application directly to a user. Google Play is the recommended marketplace for Android applications and is particularly useful if you want to distribute your applications to a large global audience. The other two release methods—server distribution and email distribution—are useful if you are releasing an application to a small group of users (for example, a work group in an enterprise environment), or if you do not want to make your application available to the general public.</p> -<h3 id="publishing-market">Releasing Your Applications on Android Market</h3> +<h3 id="publishing-market">Releasing Your Applications on Google Play</h3> -<p>Android Market is a robust publishing platform that helps you publicize, sell, and distribute +<p>Google Play is a robust publishing platform that helps you publicize, sell, and distribute your Android applications to users around the world. When you release your applications through -Android Market you have access to a suite of developer tools that let you analyze your sales, +Google Play you have access to a suite of developer tools that let you analyze your sales, identify market trends, and control who your applications are being distributed to. You also have access to several revenue-enhancing features that are not available anywhere else, such as <a href="{@docRoot}guide/market/billing/index.html">in-app billing</a> and <a -href="{@docRoot}guide/market/licensing/index.html">application licensing</a>. This rich array of -tools -and features, coupled with numerous end-user community features, makes Android Market the premier +href="{@docRoot}guide/market/licensing.html">application licensing</a>. This rich array of tools +and features, coupled with numerous end-user community features, makes Google Play the premier marketplace for selling and buying Android applications.</p> -<p>Releasing your application on Android Market is a simple process that involves three basic +<p>Releasing your application on Google Play is a simple process that involves three basic steps:</p> <div class="figure" style="width:275px"> @@ -144,19 +143,19 @@ marketplace for selling and buying Android applications.</p> to be installed" /> <p class="img-caption"> <strong>Figure 2.</strong> The <strong>Unknown sources</strong> setting lets you install - applications that are not published on Android Market . + applications that are not published on Google Play . </p> </div> <ul> <li>Preparing promotional materials. - <p>To fully leverage the marketing and publicity capabilities of Android Market, you need to + <p>To fully leverage the marketing and publicity capabilities of Google Play, you need to create promotional materials for your application, such as screenshots, videos, graphics, and promotional text.</p> </li> <li>Configuring options and uploading assets. - <p>Android Market lets you target your application to a worldwide pool of users and devices. - By configuring various Android Market settings, you can choose the countries you want to + <p>Google Play lets you target your application to a worldwide pool of users and devices. + By configuring various Google Play settings, you can choose the countries you want to reach, the listing languages you want to use, and the price you want to charge in each country. You can also configure listing details such as the application type, category, and content rating. When you are done configuring options you can upload your promotional materials @@ -170,21 +169,21 @@ marketplace for selling and buying Android applications.</p> </li> </ul> -<p>For information about Android Market, see <a -href="{@docRoot}guide/publishing/publishing.html#market">Publishing on Android Market</a>. This -topic provides an introduction to Android Market features and provides a step-by-step guide for -distributing your applications on Android Market.</p> +<p>For information about Google Play, see <a +href="{@docRoot}guide/publishing/publishing.html#market">Publishing on Google Play</a>. This +topic provides an introduction to Google Play features and provides a step-by-step guide for +distributing your applications on Google Play.</p> <h3 id="publishing-website">Releasing your application on your own website</h3> -<p>If you do not want to release your application on an application marketplace like Android Market, +<p>If you do not want to release your application on an application marketplace like Google Play, you can release your application by making it available for download on your own website or server. To do this, you must first prepare your application for release (that is, you must build it for release and sign it). Then all you need to do is host the release-ready application on your website and provide a download link for the application. When users browse to your website with their Android-powered devices and download your application, the Android system will automatically start installing the application on the device. However, the installation process will start automatically -only if the user has configured their device to allow the installation of non-Android Market +only if the user has configured their device to allow the installation of non-Google Play applications.</p> <div class="figure" style="width:275px"> @@ -198,7 +197,7 @@ applications.</p> </div> <p>By default, Android-powered devices allow users to install applications only if the applications -have been downloaded from Android Market. To allow the installation of applications from other +have been downloaded from Google Play. To allow the installation of applications from other sources, users need to enable the <strong>Unknown sources</strong> setting on their devices, and they need to make this configuration change before they download your application to their device (see figure 2).</p> @@ -209,7 +208,7 @@ applications from unknown sources.</p> <p>Although it is relatively easy to release your application on your own website, it can be inefficient and cumbersome. For example, if you want to monetize your application you will have to process and track all financial transactions yourself and you will not be able to use -Android Market's in-app billing feature to sell in-app products. In addition, you will not be +Google Play's in-app billing feature to sell in-app products. In addition, you will not be able to use the licensing feature to help prevent unauthorized installation and use of your application.</p> @@ -223,7 +222,7 @@ button in the email message (see figure 3). Users can install your application b button.</p> <p class="note"><strong>Note:</strong> The <strong>Install Now</strong> button appears only if a -user has configured their device to allow the installation of non-Android Market applications and +user has configured their device to allow the installation of non-Google Play applications and they open your email with the native Gmail application.</p> <p>Releasing applications through email is convenient if you are sending your application to diff --git a/docs/html/guide/publishing/versioning.jd b/docs/html/guide/publishing/versioning.jd index 79ebf96..da57e3e 100644 --- a/docs/html/guide/publishing/versioning.jd +++ b/docs/html/guide/publishing/versioning.jd @@ -25,7 +25,7 @@ page.title=Versioning Your Applications <ol> <li><a href="{@docRoot}guide/publishing/preparing.html">Preparing to Publish Your Application</a></li> -<li><a href="{@docRoot}guide/publishing/publishing.html#market">Publishing On Android Market</a></li> +<li><a href="{@docRoot}guide/publishing/publishing.html#market">Publishing On Google Play</a></li> <li><a href="{@docRoot}guide/topics/manifest/manifest-intro.html">The AndroidManifest.xml File</a></li> </ol> |