Kilimanjaro/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.

The Product proposal below outlines the requirements for the first step on the way to Kilimanjaro -- a 'Basecamp' - that focuses on delivering a full 'Web as the Platform' experience via the Boot to Gecko product.

Please do not edit without talking to Asa/Chris/Dan/Ragavan. Please post feedback/comments to the dev-planning list. Thanks!

Background - The Web is the Platform

The background and context for this project is described on the Kilimanjaro project page.

The Basecamp Milestone

The Basecamp milestone is the first step on the path to Kilimanjaro. It consists of the must-have features and services to launch the first B2G device in Brazil. It consists of:

• A B2G device to be deployed by Telefonica in Brazil, developed in conjunction with Qualcomm and an OEM partner.
• A set of built in apps that are highly relevant in Brazil and solves use cases for the target market there
• An app ecosystem in Brazil that includes high-quality, must-have apps for that market
• Identity integration with the network operator
• App marketplace with tight billing integration with the network operator (under discussion)

This "basecamp" release is aimed at ensuring a successful first roll-out of the "Web as the Platform." It doesn't mean that work on other things stops entirely. But it does mean that we prioritize making our first B2G deployment in Brazil a success. Notably, as an example, the basecamp milestone would not require an Android app runtime, nor would it require a global rollout of the app marketplace. We should continue to move these initiatives forward, but we don't have to go to final release, or go global, until we're ready.

High level set of requirements for Basecamp

• A B2G device to be deployed by Telefonica in Brazil, developed in conjunction with Qualcomm and an OEM partner
• B2G phone experience (UX), Gaia version 1, delivered with a core set of applications that ship with the device to consumers
• A viable, open, standards-based mobile web apps ecosystem and marketplace
• A set of at least 50 popular, high-quality and compelling mobile web apps for Brazil available in the marketplace
• An apps marketplace with identity and billing integration with the network operator (under discussion)

Basecamp Target Audiences and Example User Scenarios

Value Proposition

• Users:
  • Feature phone consumers today who want to experience/purchase a cost-effective full-featured smartphone
• Developers:
  • Major social/content/gaming/productivity/etc. providers relevant in Brazil that want to extend their reach on Mobile devices
• Carriers and OEMs:
  • Creates new opportunities to expand operator's customer base and revenue channels (i.e. Partners can customize value-add services/pre-bundle content and apps)

Web Developers

Meta: bug TBD

Claire works for a top content provider in Brazil as a developer and is introduced to HTML5 and wants to create an app for Mozilla's new 'Boot to Gecko' device. She visits MDN where she finds docs and tools that helps her get started. After building her app, she lists it in the Mozilla Marketplace for $0.99. The Marketplace lets her manage her application, reviews, and customer relationships.

B2G Phone Early Adopters

Meta: bug 746481

Sofia just purchased a B2G mobile phone from her local carrier store. She sets up her phone which includes creating a identity account. She imports contacts from her old phone via her previous SIM card. Her new phone has all of the basic apps she considers requirements for a smartphone as well as a Marketplace app where she can find additional relevant apps for someone who lives in Brazil.

Sofia has been using her phone for 3 months and experiences problems like:

• Her phone crashes a lot.
• Sofia needs help but doesn't know who to contact.

Sofia contacts Telefonica customer service as a first step and because it's a 'tier 2' problem, Mozilla will provide Telefonica with step by step instructions to help resolve her problems.

Basecamp Detailed Requirements and Priorities

1. P1: B2G software stack ready for device to launch in the Brazil market
2. P1: All content needs to be localized content in English (US), Spanish (LatAm) and Portuguese (Brazil)
3. P1: Mozilla to build and operate a Brazil-targeted App Marketplace that offers:
   1. App Marketplace needs to target a B2G phone resolution (320x480)
   2. Featured and most popular apps
   3. App reviews
   4. App categories: Content, Productivity, Games (at risk for Brazil), Social
   5. Developer lifecycle/management capabilities
      1. Account creation
      2. Submission
      3. Edit/Delete/Payment management
   6. Blocklist for Marketplace and non-Marketplace apps (need to evaluate)
4. P1: B2G user will have the ability to create a Telefonica account
5. P1: The Telefonica accounts system implements the Persona identity provider protocol
6. P1: The ability to sign into application using:
   1. Persona ID, Google ID, Facebook ID, Twitter ID, Brazil-specific IDs, Marketplace bug 763377
   2. This requirement gives B2G the ability to support in-app purchases
7. P1: Gaia Settings app is a touch-point for creating/managing the user's Telefonica ID
8. P1: Apps Marketplace with billing integration with the network operator (under discussion)
   1. Applications in the Brazil-targeted Marketplace will offer users the ability to pay for apps with their carrier's account
   2. This would apply to featured apps in Brazil
9. P1: Business development efforts for the Brazil app developers
   1. Secure at least 50 high-quality and compelling tier 1&2 apps for the Brazil marketplace by launch[1]
   2. Prioritized category of applications to target:
      1. Social
      2. Content (Sports, Music, etc.)
      3. Games (at risk)
      4. Productivity
10. P1: B2G front-end experience, Gaia version 1 - core set of default applications:
    1. Phone/System apps:
       1. Dialer
       2. Contacts
       3. SMS/Messaging
       4. Settings
    2. Media apps:
       1. Camera
       2. Photo Gallery
       3. Video Player
       4. Music Player
       5. FM Radio
    3. Productivity:
       1. Email
       2. Calendar
       3. Clock/Alarm
       4. Browser
       5. App Marketplace
    4. Note: We will also pre-install some 3rd party apps decided by Mozilla/partner

Specific tasks/bugs we are tracking

1. P1: Offline capabilities (improve appcache support/semantics, implement IndexedDB improvements, platform support for default offline behavior) (bug 747904)
2. P1: Layout compatibility - webkit (bug 747123)
3. P1: H.264/AAC & mp3 (bug 748351)
4. P1: Orientation Lock (bug 673922)
5. P1: Finish multi-touch (bug 747910)
6. P1: Hardware accelerated Canvas or WebGL (Mobile only) (bug 749721)
7. P1: Security and Permissions model for Apps on B2G
8. P1: Mozilla Marketplace SLAs
9. P1: Customer Support process defined and agreed on

[1]: There is a target launch date, but is internal information and will be provided to the appropriate teams working on Kilimanjaro.