diff options
Diffstat (limited to 'docs/html/guide/market/licensing/overview.jd')
| -rw-r--r-- | docs/html/guide/market/licensing/overview.jd | 66 |
1 files changed, 33 insertions, 33 deletions
diff --git a/docs/html/guide/market/licensing/overview.jd b/docs/html/guide/market/licensing/overview.jd index 3576e26..05a3a40 100644 --- a/docs/html/guide/market/licensing/overview.jd +++ b/docs/html/guide/market/licensing/overview.jd @@ -9,9 +9,9 @@ parent.link=index.html <h2>Quickview</h2> <ul> - <li>Licensing allows you to verify your app was purchased from Android Market</li> + <li>Licensing allows you to verify your app was purchased from Google Play</li> <li>Your app maintains control of how it enforces its licensing status</li> - <li>The service is free for all developers who publish on Android Market</li> + <li>The service is free for all developers who publish on Google Play</li> </ul> <h2>In this document</h2> @@ -26,19 +26,19 @@ parent.link=index.html </div> -<p>Android Market Licensing is a network-based service that lets an application query a trusted -Android Market licensing server to determine whether the application is licensed to the current -device user. The licensing service is based on the capability of the Android Market licensing server -to determine whether a given user is licensed to use a given application. Android Market considers a +<p>Google Play Licensing is a network-based service that lets an application query a trusted +Google Play licensing server to determine whether the application is licensed to the current +device user. The licensing service is based on the capability of the Google Play licensing server +to determine whether a given user is licensed to use a given application. Google Play considers a user to be licensed if the user is a recorded purchaser of the application.</p> <p>The request starts when your application makes a request to a service hosted by -the Android Market client application. The Android Market application then sends a request to -the licensing server and receives the result. The Android Market application sends +the Google Play client application. The Google Play application then sends a request to +the licensing server and receives the result. The Google Play application sends the result to your application, which can allow or disallow further use of the application as needed.</p> -<p class="note"><strong>Note:</strong> If a paid application has been uploaded to Android Market but +<p class="note"><strong>Note:</strong> If a paid application has been uploaded to Google Play but saved only as a draft application (the app is unpublished), the licensing server considers all users to be licensed users of the application (because it's not even possible to purchase the app). This exception is necessary in order for you to perform testing of your licensing @@ -48,39 +48,39 @@ implementation.</p> <div class="figure" style="width:469px"> <img src="{@docRoot}images/licensing_arch.png" alt=""/> <p class="img-caption"><strong>Figure 1.</strong> Your application initiates a -license check through the License Verification Library and the Android Market -client, which handles communication with the Market server.</p> +license check through the License Verification Library and the Google Play +client, which handles communication with the Google Play server.</p> </div> <p>To properly identify the user and determine the license status, the licensing server requires -information about the application and user—your application and the Android Market client work -together to assemble the information and the Android Market client passes it to the server. </p> +information about the application and user—your application and the Google Play client work +together to assemble the information and the Google Play client passes it to the server. </p> <p>To help you add licensing to your application, the Android SDK provides a downloadable set of -library sources that you can include in your application project: the "Google Market Billing +library sources that you can include in your application project: the "Google Market Licensing package." The License Verification Library (LVL) is a library you can add to your application that -handles all of the licensing-related communication with the Android Market licensing service. With +handles all of the licensing-related communication with the Google Play licensing service. With the LVL added to your application, your application can determine its licensing status for the current user by simply calling a method and implementing a callback that receives the status response.</p> <p>Your application does not query the licensing server -directly, but instead calls the Android Market client over remote IPC to +directly, but instead calls the Google Play client over remote IPC to initiate a license request. In the license request:</p> <ul> <li>Your application provides: its package name, a nonce that is later used to validate any response from the server, and a callback over which the response can be returned asynchronously.</li> -<li>The Android Market client collects the necessary information about the user and the device, +<li>The Google Play client collects the necessary information about the user and the device, such as the device's primary Google account username, IMSI, and other information. It then sends the license check request to the server on behalf of your application.</li> -<li>The Android Market server evaluates the request using all available information, attempting +<li>The Google Play server evaluates the request using all available information, attempting to establish the user's identity to a sufficient level of confidence. The server then checks the user identity against purchase records for your application and -returns a license response, which the Android Market client returns to your +returns a license response, which the Google Play client returns to your application over the IPC callback.</li> </ul> @@ -97,7 +97,7 @@ network connections or use any licensing related APIs in the Android platform.</ <h2 id="Secure">License Responses are Secure</h2> <p>To ensure the integrity of each license query, the server signs the license -response data using an RSA key pair that is shared exclusively between the Android Market +response data using an RSA key pair that is shared exclusively between the Google Play server and you.</p> <p>The licensing service generates a single licensing key pair for each @@ -120,7 +120,7 @@ tampered with or that are spoofed.</p> which includes the License Verification Library (LVL). The LVL greatly simplifies the process of adding licensing to your application and helps ensure a more secure, robust implementation for your application. The LVL provides internal classes that handle most of the standard operations of a -license query, such as contacting the Android Market client to initiate a license request and +license query, such as contacting the Google Play client to initiate a license request and verifying and validating the responses. It also exposes interfaces that let you easily plug in your custom code for defining licensing policy and managing access as needed by your application. The key LVL interfaces are: </p> @@ -179,17 +179,17 @@ physical device.</p> <h2 id="Reqs">Requirements and Limitations</h2> -<p>Android Market Licensing is designed to let you apply license controls to -applications that you publish through Android Market. The service is not +<p>Google Play Licensing is designed to let you apply license controls to +applications that you publish through Google Play. The service is not designed to let you control access to applications that are not published -through Android Market or that are run on devices that do not offer the Android -Market client. </p> +through Google Play or that are run on devices that do not offer the Google +Play client. </p> <p>Here are some points to keep in mind as you implement licensing in your application: </p> <ul> -<li>An application can use the service only if the Android Market client is +<li>An application can use the service only if the Google Play client is installed on its host device and the device is running Android 1.5 (API level 3) or higher.</li> <li>To complete a license check, the licensing server must be accessible over @@ -202,7 +202,7 @@ handling of the license are factors are up to you. By following the best practices in the following documents, you can help ensure that your implementation will be secure.</li> <li>Adding licensing to an application does not affect the way the application -functions when run on a device that does not offer Android Market.</li> +functions when run on a device that does not offer Google Play.</li> <li>You can implement licensing controls for a free app, but only if you're using the service to provide <a href="{@docRoot}guide/market/expansion-files.html">APK expansion files</a>.</li> @@ -212,20 +212,20 @@ href="{@docRoot}guide/market/expansion-files.html">APK expansion files</a>.</li> <h2 id="CopyProtection">Replacement for Copy Protection</h2> -<p>Android Market Licensing is a flexible, secure mechanism for controlling +<p>Google Play Licensing is a flexible, secure mechanism for controlling access to your applications. It effectively replaces the Copy Protection -mechanism offered on Android Market and gives you wider distribution +mechanism offered on Google Play and gives you wider distribution potential for your applications. </p> <ul> -<li>A limitation of the legacy Copy Protection mechanism on Android Market is +<li>A limitation of the legacy Copy Protection mechanism on Google Play is that applications using it can be installed only on compatible devices that provide a secure internal storage environment. For example, a copy-protected -application cannot be downloaded from Market to a device that provides root +application cannot be downloaded from Google Play to a device that provides root access, and the application cannot be installed to a device's SD card. </li> -<li>With Android Market licensing, you can move to a license-based model in +<li>With Google Play licensing, you can move to a license-based model in which access is not bound to the characteristics of the host device, but to your -publisher account on Android Market and the licensing policy that you define. +publisher account on Google Play and the licensing policy that you define. Your application can be installed and controlled on any compatible device on any storage, including SD card.</li> </ul> |