Mobile/ARMv6
Product Goals
• Empower communities who depend upon their mobile devices to access the internet on ARMv6 phones
• Introduce support for a new platform in order to increase market share
• Current goal is to ship in Fx16
Market Requirements
Feature page: https://wiki.mozilla.org/ARMv6_support_-_phase_1
Getting down to 600 MHz, 256 MB RAM, 240x240 resolution doubles our addressable market from 40% to 81% of all Android devices.
Quality Metrics
• Stability:
• Performance:
• UX:
• Usability:
• Minimum System Requirements
Mobile Eng
• Where are we today?
• What's next?
UX
- Prepare new set of graphic assets for low density displays (ETA mid-september)
- bug 716403 Enable scrolling title bar, to maximize the amount of viewable web content on screen
- Revisit tabs UI to optimize for small screen heights (could include opening the tabs tray wider, or scrolling thumbnails horizontally, etc)
- Checking behaviours on devices with hardware keyboards -- does the interaction feel right?
- Awesomebar / search suggest
- Find in Page
- Form input / navigation
---
- What other data do we need in order to understand what the UX requirements are or do we know this information already?
- It would help us to see a list of any other UX regressions that have been found to date that have not been mentioned above.
QA
Where are we today?
• We have a good baseline in terms of variety testing and an initial bug hunt. However, need to clarity on the quality goals
• Initial Compat Testing
What's next?
• Expand breadth of test plan based upon defined quality targets & crowd sourcing testing
• bug 779410 - Retrofit Web Compat Testing Tool for ARMV6
• Blockers?
Community
• Building MTD
• Outreach via other developer sites
• What else?
A-Team
• Where are we today?
• What's next?