Firefox OS: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(page)
(delete page)
Line 2: Line 2:
=Firefox OS Design Principles=
=Firefox OS Design Principles=


[[Connected Devices]]


# '''We will build phones and connected devices that people want to buy because of the experience, not simply the price.'''
# '''We will build phones and connected devices that people want to buy because of the experience, not simply the price.'''

Revision as of 19:01, 19 February 2016

Fxos.png

Firefox OS Design Principles

  1. We will build phones and connected devices that people want to buy because of the experience, not simply the price.
  2. We will focus on depth first vs. breadth first. Our goal will be to on achieve real meaningful success and significant traction within our target market segments. We won’t allow ourselves to be distracted, and we won’t expand to new segments until significant traction is demonstrated. (It’s important that we establish a beachhead to build from, and that we’re following through all the way from delivering the initial product to achieving real market success and end-user delight and advocacy.)
  3. We will build products that feel like Mozilla. We must define, build and own the product experience to ensure it delivers upon our brand promise and principles. This is critical to ensure that we’re building product expertise and that we’re able to deliver ever more value to our end-users and activate other distribution partnerships to reach even more people.
  4. We will deliver compelling content and app experiences that exceed consumer expectations. We will continue to invest in Web platform capabilities and programs to incentivize developers to build for the Web. And to bridge this app gap between user expectations and the readiness of the ecosystem, we will explore implementing limited Android app compatibility for key apps, within a framework that keeps our long-term focus on the Web as the platform across desktop, mobile and connected devices. This mirrors our earlier strategy with Firefox in the face of Internet Explorer market dominance, and we believe this is a necessary step to the web flourishing as a mobile ecosystem.
  5. We will ensure that when you buy a Firefox OS-powered phone you’re joining our global community. Empowering people with technology, know-how and opportunity is key to our success, and we must provide product experiences that invite users into our community from enabling people to hack and customize their phone experience to providing local engagement for support, education and more.
  6. We will ensure that the products we build are timely, technically excellent and high quality. In order for our products to be great and loved by people they be available when and where they expect them, and they must meet or exceed their expectations in terms of performance and reliability, at all price points. We must aim to build products that we’re proud of.

These principles come out of discussions with many of you and the learnings from the v3 iteration process, as well as our understanding of the industry. We want to spend some time reviewing these together and then declare them part of our official working plan. We can use these to align our strategy and approach with the Mozilla mission and to evaluate product opportunities.

Firefox OS Functional Team Information

Everything you need to know about the functional teams working on Firefox OS is here (Meeting times, Leadership teams, and Individual Backlogs)

Firefox OS Release Management & Triage

Tracking Features and Blocking Bugs across all FXOS functional teams

Release Management

Triage

Firefox OS Development Process and Release Lifecycle

Firefox OS UX

Firefox OS Sprint Status

1.4 Sprint Schedule - Firefox OS/devlifecycle#1.4_Release_Calendar Calendar View

Start End
Firefox 1 2/3 2/14
Firefox 2 2/17 2/28
Firefox 3 3/3 3/14
Firefox 4 3/17 3/28
Firefox 5 3/31 4/11
Firefox 6 4/14 4/25


--Ahmedalkabir 09:52, 26 February 2014 (PST)

Sprint Tracking

Real-time dashboard view of each functional team's progress sprint-to-sprint. You are able to see all current open user stories and bugs in current sprint. (Dashboards are queried directly from bugzilla and pull based on target milestone and team product components and/or whiteboard tags)

Firefox OS Product Management

Product Backlog

User stories, acceptance criteria, assumptions, and dependencies for all FXOS functional teams are maintained in the backlog below. (listed by tab)

Firefox OS Security Team

More information on the team page.

Other Resources

other references, very useful catch all category for existing links and text when cleaning up existing project pages

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox_OS&oldid=1117862"