diff --git a/get_started.html b/get_started.html index 7f16be8..f26566f 100644 --- a/get_started.html +++ b/get_started.html @@ -1,18 +1,18 @@ {{+bindTo:partials.standard_store_article}} + +

Tutorial: Licensing API

+

Important: - Chrome will be removing support for Chrome Apps on Windows, Mac, and - Linux. Chrome OS will continue to support Chrome Apps. Additionally, - Chrome and the Web Store will continue to support extensions on all - platforms. - - Read the announcement and learn more about - - migrating your app. + Hosted Apps are no longer supported. + For payment information refer to + One-Time Payments, + + In-App Payments with Payments Merchant Account and the Chrome Web Store API + and + Monetizing Your Chrome Web Store Item.

-

Tutorial: Licensing API

-

This tutorial walks you through creating an app that uses the Chrome Web Store Licensing API. diff --git a/overview.html b/overview.html index 3cccfa6..470b7ce 100644 --- a/overview.html +++ b/overview.html @@ -171,15 +171,6 @@

Charging for your app

  • Custom payment solution
  • -

    -Note: -Although packaged apps and extensions -can use Chrome Web Store Payments, -it's difficult for them to use the Licensing API securely. -Themes have no executable code, -so they can't use the Licensing API. -

    -

    Providing some functionality for free

    @@ -288,16 +279,6 @@

    Uploading and publishing your item

    For details, see Publishing Your App.

    -

    -Note: -Before you publish your first app, -you must pay a $5 developer signup fee. -If you used the Chrome Developer Dashboard before {{ grandfatherdate }}—to -publish an extension, for example—you -don't need to pay the fee. -

    - -

    Back to top

    Protecting your item from unauthorized use

    @@ -319,55 +300,6 @@

    Protecting your item from unauthorized use

    being served by the Chrome Web Store.

    - -

    Using the Licensing API to check for payment

    - -

    -The Chrome Web Store Licensing API lets you find out -whether the current user has paid for your item -using Chrome Web Store Payments. -To use the Licensing API, -you need two IDs and an OAuth access token: -

    - -
    -
    App ID
    -
    - The Chrome Developer Dashboard generates this ID - the first time you upload the app. - You can get it from the Chrome Developer Dashboard's - page for your item. -
    - -
    User ID
    -
    - Your app needs to get a Google Account identity for the user, - using OpenID. -
    - -
    OAuth access token
    -
    - After you upload your app, - you can ask the Chrome Developer Dashboard - to generate an OAuth access token and secret. -
    -
    - -

    -Once you have these items, -you can make requests to the license server -using OAuth and the Licensing API. -The license server tells you whether the user has access to this item, -and whether a free trial is in effect. -Rather than query the server repeatedly, -you should cache the response. -

    - -

    -For detailed instructions on using the Licensing API, see -Checking for Payment. -

    -

    Encouraging payment

    @@ -400,29 +332,10 @@

    Encouraging payment

    What next?

    -Here are some choices for where to go next: +Publish your first item in the Chrome Web Store by following the +Getting Started Tutorial.

    -
    -
    Tutorial: Getting Started
    -
    Publish your first item in the Chrome Web Store. -
    - -
    Checking for Payment
    -
    Learn how to use the Licensing API to - check whether the user has paid for your item. -
    - -
    Tutorial: Licensing API
    -
    Write an app that uses the Licensing API. -
    - -
    Samples
    -
    Find samples in multiple languages of apps - that use the Licensing API. -
    - -

    If you just want to write your item, @@ -430,10 +343,9 @@

    What next?

    Back to top