diff options
| author | Dirk Dougherty <ddougherty@google.com> | 2013-06-18 10:35:42 -0700 |
|---|---|---|
| committer | Dirk Dougherty <ddougherty@google.com> | 2013-07-31 00:49:43 +0000 |
| commit | a9dcc3345918dbb289503d76cab6c40cee673b2c (patch) | |
| tree | 311e177274c6c1e8398e8d785602e152ef9bce7d /docs | |
| parent | e827b0d752c36df8bd5613a5cf5346865b0f5468 (diff) | |
| download | frameworks_base-a9dcc3345918dbb289503d76cab6c40cee673b2c.zip frameworks_base-a9dcc3345918dbb289503d76cab6c40cee673b2c.tar.gz frameworks_base-a9dcc3345918dbb289503d76cab6c40cee673b2c.tar.bz2 | |
Doc change: edits to purchase status api docs.
Change-Id: I96e8c9d47e90fe2bc9d3dd449524686a094c7041
(cherry picked from commit cd9a1a8fe98bd29e3f52b8a04e8106e89b431d64)
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/html/google/play/billing/gp-purchase-status-api.jd | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/docs/html/google/play/billing/gp-purchase-status-api.jd b/docs/html/google/play/billing/gp-purchase-status-api.jd index d6b251e..c5b8461 100644 --- a/docs/html/google/play/billing/gp-purchase-status-api.jd +++ b/docs/html/google/play/billing/gp-purchase-status-api.jd @@ -118,13 +118,13 @@ Purchase Status API. For security reasons, the app should not normally attempt t the purchase itself using the Purchase Status API.</p> <p>If the backend server determines that the purchase is valid, it notifies the -app and grant access to the content. For improved performance, the backend servers -should store the purchase details and order status in a local database, updated a +app and grants access to the content. For improved performance, the backend servers +should store the purchase details and order status in a local database, updated at intervals or as-needed.</p> -<p>Keep in mind that users will want to be able to use your app at any time, including +<p>Keep in mind that users will want the ability to use your app at any time, including when there may be no network connection available. Make sure that your approach to -purchase verification takes account of the offline use-case.</p> +purchase verification accounts for the offline use-case.</p> <h2 id="practices">Using the API Efficiently</h2> @@ -154,7 +154,7 @@ minimize your access using the techniques below. </p> query each day to check the status of expiring subscriptions, then update the database. Note that: <ul> - <li>Your servers should not query all subscriptions every day</li> + <li>Your servers should not query all subscriptions every day.</li> <li>Your servers should never query subscription status dynamically, based on individual requests from your Android application.</li> </ul> @@ -162,5 +162,6 @@ minimize your access using the techniques below. </p> </ul> <p>By following those general guidelines, your implementation will offer the -best possible performance for users and minimize use of the Google Play Android -Developer API.</p> +best possible performance for users and minimize use of the <a +href="https://developers.google.com/android-publisher/v1_1/">Google Play Android +Developer API</a>.</p> |