Marketplace/Basecamp

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

Revised Marketplace Basecamp Requirements (6/22/12)

Supported Use Cases

• [P1] B2G user can browse, search, and install free apps from the Marketplace in Portuguese
• [P1] App developers can submit and manage their apps for review and listing in the Marketplace
• [P1] Marketplace staff can monitor and manage the content of the site
• [P1] App developers can integrate payment providers of their choosing without involving the Marketplace
• [P2] B2G user can make an in-app purchase using his Telefonica account
• [P3] B2G user can make an up-front purchase of an app using her Telefonica account

Basecamp Requirements

Consumer-facing Requirements

• [P1] 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
• [P1] User account system with verified email address
• [P1] Free app installation supported on B2G devices for logged-in users
• [P1] Minimal data consumption to load Marketplace resources
• [P1] Localization of Marketplace strings and top local apps into Portuguese, Spanish, and English
• [P2] B2G user can make an in-app purchase by paying with his Telefonica account
• [P3] B2G user can make an up-front purchase by paying with her Telefonica account

Developer-facing Requirements

• [P1] App submission tool and process for listing in the Marketplace
• [P1] App management tools for developers to:
  • Edit their listing, including modifying metadata and adding translations
  • Upload media (screenshots and videos)
  • Grant access to others
• [P1] Daily statistics and reports on app installs
• [P1] App developers can integrate payment providers of their choosing without involving the Marketplace
• [P2] App developers can become Telefonica/BlueVia merchants easily during app submission to the Marketplace
• [P2] App developers can collect in-app payments from B2G users paying through Telefonica
• [P3] App developers can set up-front pricing in Reals and receive funds from users paying through Telefonica
• [P3] App developers can verify purchase receipts issued by the Marketplace for paid app downloads
• [P3] Appropriate security measures in place to store payment related keys and tokens, if collected

Mozilla Requirements

• [P1] User account and app management tools available to Marketplace staff for support and administration
• [P1] High availability service infrastructure according to SLA to be determined (previous draft)
• [P1] Review process and tools to enforce quality, security, performance, and other standards

Desktop/Android requirements that impact Basecamp

("what features are required for desktop/Android Marketplace that impact Basecamp implementation but are not required for Basecamp?")

• [P1] Regional stores exist for all supported countries to control appropriate distribution and consumption of app listings in the Marketplace
• [P1] Users can set an optional Purchase PIN required for every purchase to enhance security
• [P1] Global payments system for credit cards and carrier billing that minimizes developer effort and obligations
• [P2] Content ratings system for classification of age-appropriateness of apps