Home | History | Annotate | Download | only in play

Lines Matching full:your

37 and app-management tasks. You can use this API to integrate your publishing
38 operations with your release-management process.</p>
41 continue to manage your apps directly using the Google Play Developer Console.
49 <li>Uploading and releasing new versions of your app</li>
50 <li>Editing your app Google Play Store listings, including localized text and
52 <li>Managing your in-app product catalog, your products purchase status and your
57 <p>The Google Play Developer API lets you focus on designing and developing your
58 app, while spending less time and effort managing your releases, even as you
96 Developer Console. However, this API lets you integrate your app and listing
97 update process with your existing tools, which will be very useful for some
104 <p>The API allows you to manage your app's catalog of in-app products and
137 Play Developer Console</a>. The API can only be managed by the owner of your
158 and commit changes to your Google Play apps. Once your update is ready to go,
188 request a higher daily quota for your application, we highly recommend that you
189 minimize your access using these techniques: </p>
194 even less frequently than that.) Every update costs your users time and
197 with your app, go ahead and fix it.)</li>
199 purchase, your app can pass the purchase token and other details to your backend
201 <li><em>Cache purchase details on your servers</em> &mdash; To the extent possible,
202 cache the purchase details for in-app products and subscriptions on your backend
203 servers. If your app contacts your backend servers at runtime to verify purchase
204 validity, your server can verify the purchase based on the cached details, to
207 <li><em>Store subscription expiry on your servers</em> &mdash; Your servers should
211 <li><em>Query for subscription status only at expiration</em> &mdash; Once your
214 reaching or has passed the expiration date. Typically, your servers would run a batch
218 <li>Your servers should not query all subscriptions every day.</li>
219 <li>Your servers should never query subscription status dynamically, based on
220 individual requests from your Android application.</li>
225 <p>By following those general guidelines, your implementation will offer the
235 <p>If you need to request a higher limit for your application, use the "Request