SUBMITTING IN-APP CONTENT TO THE VDC PORTAL

***This page has been removed from the VDC due to the Verizon Apps shutdown. Feel free to browse our other development areasdevicesAPIs and Tools.***

VERIZON APPS SUNSET

***NOTE: Effective November 1st, 2012, the VDC no longer accepts new Verizon App submissions. Additionally, beginning December 2012, final billing to customers for all existing Subscriptions and In-App Purchase apps will occur, and all paid Subscriptions and In-App Purchase API apps will be removed from the catalog on November 1st, 2012. Customers will receive a final full month of use & access, before Verizon Apps begins its complete shutdown in January 2013.

For additional details, please review the Verizon Apps Notice and Verizon Apps Transition Timeline.***

SUBMITTING IN-APP CONTENT TO THE VDC PORTAL

If you have not submitted In-App content before (via other applications), you'll be presented with a click through In-App addendum that you need to review and initial.

This addendum is visible in the developers “My Account”->“Contracts” section within the VDC for review and acceptance.

SUBMITTING IN-APP CONTENT TO EXISTING APPLICATIONS

Currently Verizon is not permitting developers to upgrade existing applications that are in Verizon Apps with In-App functionality.  This feature is currently being worked on will be delivered shortly; check back in this section of the In-App Purchase SDK on the portal for updates.

SUBMITTING IN-APP CONTENT TO A NEW APPLICATION

When submitting a new application the first screen in the VDC portal will present the question “Does the app support In-App purchases?”  You must select ‘Yes’ to this question in order to allow submission of In-App content later in the process flow.  Refer to the screenshot below:

3

Developers are required to submit their apps following the Subscriptions flow as described in the page "Submitting Subscriptions Content to the VDC Portal.  If you want to offer In-App items you are not forced to use Subscriptions in your code (checking licenses at application startup) however the coding process is simple and it is a suggested practice.  If you’re unfamiliar with Subscriptions coding recommendations, refer to the Subscriptions coding guidelines on this site for more detail. 

The final screen presented during the submission process asks whether you want to submit In-App content now, refer below:

In-APP_End_Submission

If you elect to submit the content now, move straight to the contentType explanation and submission instructions below.  Otherwise you can return to your list of apps in the portal and select the “Manage In-App Items” button, refer below:

MANAGE_IN_APP

Note that adding In-App items will work at the “parent” level, in other words, In-App items will apply across all devices that are under that parent.  Developers will not have to submit In-App content for each individual device. 

In order to simplify submission and management of In-App content, developers are permitted to submit one generic piece of content per ContentType below and specify a min-max price range for that ContentType.  Thus, one submission in the VDC portal can potentially cover all of an app’s In-App content items.  Currently, the ContentType subset includes:

  • Virtual good - Games
  • Virtual good - Applications
  • eBooks
  • eMagazine  
  • eNewspapers
  • Wallpapers

It is critical that developers offer the appropriate contentType in their app – an item that is sold within a game should be submitted as a ‘Virtual Good – Games’ contentType not as an ‘eBook’, ‘eMagazine’, ‘eNewspaper’, or ‘wallpaper’.  An app that offers purchasable books should submit their In-App content Type as ‘eBook’ and not as a Virtual Good – Game, Virtual Good – Applications, etc. 

Failure to submit In-App content appropriately might result in rejection of your app, delays in publication, or getting pulled from the store retroactively.

Additional ContentTypes planned for the future may include music, video, and others.   One ContentType can have multiple priceType offerings;  PriceType is the value returned from our server when calling In-App methods.  The mapping between the price option you see in the portal and what is returned from the backend is below:

VDC Portal Pricing Option         Price Type                               
Per Download First Download
Recurring Downloads Unlimited Downloads
Time Based Subscription Per Period
Monthly Subscription Subscription

Let’s use the example of a game developer adding In-App content to illustrate how the setup works.  The developer wants to offer a set of weapons in their game that should be charged for each download and might range in price from $1.99 - $9.99.  Additionally, the developer wants to offer new levels ranging from $1.99 – $5.99 that are monthly recurring Subscription pricing.  In order to submit these through the portal the developer would:

  •  Submit one In-App Content Type, Virtual Good (Game), that has multiple price options:
    • Per download price range $1.99-9.99
    •  Subscription price range $1.99-$5.99

 

This single submission of content type and price range can cover any in-app items developers wish to offer.

 

Matching between In-App purchases by the end user and what is held in the VDC portal database should be performed programmatically in the app and is up to the developer to enforce.  If you are offering multiple contentTypes that have different ranges in price it becomes much more important to match the contentTypes, grab their min/max price ranges, and ensure that what you’re displaying falls into the price range that is submitted to the portal.  Remember that upon purchase, the app must specify what the end user purchased (name, amount, and SKU) for that ContentType/Pricetype offering.  Refer to Section 6.2 for specifics.

Once developers have determined the content types and price ranges for their offerings, they can submit these to the VDC portal, refer to the screenshot below.

2