NativePlan
Summary
Firefox for Android (fennec) is arguably the most feature-rich browser available in the market however, slow startup responsiveness and performance have not been speedy enough for successful market adoption nor to generate amount customer love Firefox is accustomed to.
The advent of a prototype built with single-process architecture with the front-end written in Java creates new possibilities for Mozilla to make a faster, more responsive browser. There was a meeting in Toronto during the mobile workweek to plan what is needed to ship this new mobile browser to market.
Attendees: Damon Sicore, Mark Crandon, Jay Sullivan, Jonathan Nightingale, Mark Finkle, Doug Turner, Brad Lassey, Madhava Enros, Clint Talbert, Christian Legnitto, Jaclyn Fu, Grace Jimenez, Sheila Mooney, Martin Best, Erin Lancaster.
Decisions Made
Schedule
- Dec 2011: Feature Complete
- Jan 30 2012: Beta
- Feb 27 2012: Public Announcement at Mobile World Congress
- March 30 2012: Final Release
Ship Criteria
Tent Poles
- Security: maintain parity with the currently shipping version of Firefox Mobile
- Stability: achieve parity with the currently shipping version of Firefox Mobile. Ratio of number ADUs to number of weeks to be specified before 10/31/11.
- Performance: Raw Start should not exceed 200ms. Warm start with page load should stay within 10% of built-in browser, and we should be faster than Opera.
- Memory Usage will stay conservative so that the browser is kept alive and supports swapping/round tripping from browser to apps.
- Responsiveness: Scrolling Panning, Zooming, and Frame Rate should meet or exceed customer expectations when compared to other mobile browsers. Numeric metrics and hardware targets to be determined prior to 10/31/11.
- Features and Design: Deliver all features with P1 and P2 priority and be opportunistic about improving Ux and UI design but not at the expense of performance and responsiveness.
Features
P1
P2
