Merge "docs: Removed obsolete screenshot of Play Store purchase flow. Bug: 9846095" into klp-docs

This commit is contained in:
quddusc
2014-01-16 16:03:06 +00:00
committed by Android (Google) Code Review
2 changed files with 1 additions and 9 deletions

View File

@@ -153,8 +153,7 @@ number of in-app items.</p>
</li>
<li><strong>Description</strong>
<p>The description is a long descriptor for the item. For example, "Instantly puts creatures to
sleep. Does not work on angry elves." Every item must have a description. The description is
visible to users during checkout. Descriptions can be up to 80 characters in length.</p>
sleep. Does not work on angry elves." Every item must have a description. Descriptions can be up to 80 characters in length.</p>
</li>
<li><strong>Price</strong>
<p>You must provide a default price in your home currency. You can also provide prices in other

View File

@@ -130,13 +130,6 @@ Google Play sends your application the purchase details, such as the order
number, the order date and time, and the price paid. At no point does your
application have to handle any financial transactions; that role is provided by
Google Play.</p>
<img src="{@docRoot}images/in-app-billing/v3/iab_v3_checkout_flow.png" height="382" id="figure1" />
<p class="img-caption">
<strong>Figure 1.</strong> Applications initiate In-app Billing requests
through their own UI (first screen). Google Play responds to the request by
providing the checkout user interface (middle screen). When checkout is
complete, the application resumes.
</p>
<h2 id="samples">Sample Application</h2>
<p>To help you integrate In-app Billing into your application, the Android SDK