Marketplace/Basecamp: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
= Revised Marketplace Basecamp Requirements (7/18/12) = | |||
= Revised Marketplace Basecamp Requirements ( | |||
== Supported Use Cases == | == Supported Use Cases == | ||
* | * B2G user can browse, search, and install free apps from the Marketplace in Portuguese | ||
* | * App developers can submit and manage their apps for review and listing in the Marketplace | ||
* | * Marketplace staff can monitor and manage the content of the site | ||
* | * App developers can integrate payment providers of their choosing without involving the Marketplace | ||
* | * B2G user can make an in-app purchase using his Telefonica account | ||
* | * B2G user can make an up-front purchase of an app using her Telefonica account | ||
== Basecamp Requirements == | == Basecamp Requirements == | ||
=== Consumer-facing Requirements === | === Consumer-facing Requirements === | ||
* | * Consumer Marketplace pages available and optimized for B2G device resolution (320x480) and performance, including: | ||
** Homepage/landing page with locally featured apps | ** Homepage/landing page with locally featured apps | ||
** Categories and app browse view | ** Categories and app browse view | ||
** App search by name, description, and author | ** App search by name, description, and author | ||
** App details page including screenshots, user-contributed ratings and reviews | ** App details page including screenshots, user-contributed ratings and reviews | ||
* | * Free app installation supported on B2G devices for logged-in users | ||
* | * Minimal data consumption to load Marketplace resources | ||
* | * Marketplace has graceful offline experience | ||
* | * Localization of Marketplace strings into Portuguese, Spanish, and English | ||
* | * B2G user can make an in-app purchase by paying with his Telefonica account | ||
* | * B2G user can make an up-front purchase by paying with her Telefonica account | ||
* | * User can request refund of purchased apps and in-app items (when permitted) | ||
* | * Apps requiring plugins unsupported on B2G are appropriately flagged | ||
* | * Auto-login with Telefonica-generated opaque identifier | ||
* Regional stores and creation of Brazil store | |||
* Games in the Brazil store must have and display government rating | |||
=== Developer-facing Requirements === | === Developer-facing Requirements === | ||
* | * App submission tool and process for listing in the Marketplace | ||
* | * App management tools for developers to: | ||
** Edit their listing, including modifying metadata and adding translations | ** Edit their listing, including modifying metadata and adding translations | ||
** Upload media (screenshots and videos) | ** Upload media (screenshots and videos) | ||
** Grant access to others | ** Grant access to others | ||
* | * Daily statistics and reports on app installs and sales | ||
* | * App developers can integrate payment providers of their choosing without involving the Marketplace | ||
* | * App developers can become Telefonica/BlueVia merchants easily during app submission to the Marketplace | ||
* | * App developers can collect in-app payments from B2G users paying through Telefonica | ||
* | * App developers can set up-front pricing in Reals and receive funds from users paying through Telefonica | ||
* | * App developers can verify purchase receipts issued by the Marketplace for paid app downloads | ||
* | * Appropriate security measures in place to store payment related keys and tokens, if collected | ||
* Support for packaged apps | |||
=== Mozilla Requirements === | === Mozilla Requirements === | ||
* | * User account and app management tools available to Marketplace staff for support and administration | ||
* | * High availability service infrastructure according to SLA to be determined ([[Marketplace/SLA|previous draft]]) | ||
* | * Review process and tools to enforce quality, security, performance, and other standards | ||
* Telefonica B2G Marketplace can be customized and monitored as needed | |||
* | |||
Revision as of 07:32, 18 July 2012
Revised Marketplace Basecamp Requirements (7/18/12)
Supported Use Cases
- B2G user can browse, search, and install free apps from the Marketplace in Portuguese
- App developers can submit and manage their apps for review and listing in the Marketplace
- Marketplace staff can monitor and manage the content of the site
- App developers can integrate payment providers of their choosing without involving the Marketplace
- B2G user can make an in-app purchase using his Telefonica account
- B2G user can make an up-front purchase of an app using her Telefonica account
Basecamp Requirements
Consumer-facing Requirements
- Consumer Marketplace pages available and optimized for B2G device resolution (320x480) and performance, including:
- Homepage/landing page with locally featured apps
- Categories and app browse view
- App search by name, description, and author
- App details page including screenshots, user-contributed ratings and reviews
- Free app installation supported on B2G devices for logged-in users
- Minimal data consumption to load Marketplace resources
- Marketplace has graceful offline experience
- Localization of Marketplace strings into Portuguese, Spanish, and English
- B2G user can make an in-app purchase by paying with his Telefonica account
- B2G user can make an up-front purchase by paying with her Telefonica account
- User can request refund of purchased apps and in-app items (when permitted)
- Apps requiring plugins unsupported on B2G are appropriately flagged
- Auto-login with Telefonica-generated opaque identifier
- Regional stores and creation of Brazil store
- Games in the Brazil store must have and display government rating
Developer-facing Requirements
- App submission tool and process for listing in the Marketplace
- App management tools for developers to:
- Edit their listing, including modifying metadata and adding translations
- Upload media (screenshots and videos)
- Grant access to others
- Daily statistics and reports on app installs and sales
- App developers can integrate payment providers of their choosing without involving the Marketplace
- App developers can become Telefonica/BlueVia merchants easily during app submission to the Marketplace
- App developers can collect in-app payments from B2G users paying through Telefonica
- App developers can set up-front pricing in Reals and receive funds from users paying through Telefonica
- App developers can verify purchase receipts issued by the Marketplace for paid app downloads
- Appropriate security measures in place to store payment related keys and tokens, if collected
- Support for packaged apps
Mozilla Requirements
- User account and app management tools available to Marketplace staff for support and administration
- High availability service infrastructure according to SLA to be determined (previous draft)
- Review process and tools to enforce quality, security, performance, and other standards
- Telefonica B2G Marketplace can be customized and monitored as needed