Fennec/NativeUI/MinSysReqs
Jump to navigation
Jump to search
bug 742701 Define minimum system requirements
bug 747534 Minimize user confusion around minimum supported version change
The Below Requirements Capture 89% of the ARMv7 market
QA recommended Hardware Requirements
NOTE: 2.2 and 384 MB RAM represents 1% of our market share
- ARMv7
- Minimum CPU Frequency: ~800Mhz GHz
- Minimum RAM: ~512MB
- Storage Requirements: (As of 04/23, a clean profile sits at ~16MB on internal storage).
- Resolution: 480 (w) x 320 (h)
Android Minimum Version
- We are dropping 2.0, 2.1 support; we start at 2.2 (product approved)
Top 5 Devices Downloaded (XUL)
- Samsung Galaxy S2 (475,090
- Samsung Galaxy S (146,790)
- HTC Desire HD (144,507)
- Asus EeePad Transformer (130,630)
- Samsung Galaxy Tab 10.1 (118,927)
Top 5 Devices Downloaded (Beta)
- Samsung Galaxy S2 (16,599)
- Asus EeePad Transformer (9,667)
- Acer Picasso (6,264)
- Samsung Galaxy Tab (5,701)
- HTC Desire HD (5,669)
Open Questions
- Do the phones at the minimum end of the spectrum provide a user experience that is within an acceptable range of our mid to high phones?
- If not, what is our threshold for cutting back?
- Answer(s): Startup measurements
- More testing
- Need testing on Motorola Charm and Motorola Flip Out to see if 600Mhz is acceptable
- Need testing on Samsung Continuum to see if 336Mb is acceptable
Managing the User Experience
- (Scale to Market Share; focus on existing users)
- Option 1: Document in beta/release blog, Release Notes, Work with Sumo [Minimum Solution]
- Option 2: Push an auto-update to existing users and add a snippet to About:Home with a statement for existing users-? [Maximum Solution]
- Option 3: Google Play: Update the Description in Auto Updates for existing users
- Option4: Keep unsupported hardware users on v10 ESR
Phones that we'll be cutting out
- 2.1 devices