Firefox OS/Haida: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 16: Line 16:


==Visual Design Refresh==
==Visual Design Refresh==
The darkness and visual complexity of the original Firefox OS is being replaced by a spacious experience.  Visual clutter is reduced by removing or softening spacial divisions.  There is more breathing room, more consistent alignment. Calls to action are more obvious. The focus is drawn to content and to words.  
'''What is it?''' The darkness and visual complexity of the original Firefox OS is being replaced by a spacious experience.  Visual clutter is reduced by removing or softening spacial divisions.  There is more breathing room, more consistent alignment. Calls to action are more obvious. The focus is drawn to content and to words.  


'''Current State''' (updated April 10, 2014)
'''Current State''' (updated April 10, 2014)
Line 33: Line 33:


==Updated Homescreen==
==Updated Homescreen==
A refreshed homescreen concept centered around vertical scrolling to act as a counterbalance for edge gesture app switching as well as big, beautiful iconography.
'''What is it?''' A refreshed homescreen concept centered around vertical scrolling to act as a counterbalance for edge gesture app switching as well as big, beautiful iconography.


'''Current State''' (updated April 10, 2014)
'''Current State''' (updated April 10, 2014)
Line 52: Line 52:


==Replaceable Homescreen==
==Replaceable Homescreen==
We are an open platform. We win when people build cool stuff. Our goal is to build the best core experience and performance that we can, and then make it easy for partners and users to take Firefox OS and adapt it to their needs.
'''What is it?''' We are an open platform. We win when people build cool stuff. Our goal is to build the best core experience and performance that we can, and then make it easy for partners and users to take Firefox OS and adapt it to their needs.


'''Current State''' (updated April 10, 2014)
*Prototype complete
*Updated homescreen (see above) will make use of replaceable homescreen functionality
*Some underlying API work needs to be done to enable homescreen apps to be privileged instead of being certified (for future third party homescreen support)
*Shipping both updated homescreen and classic homescreen using framework in discussion (allowing users to choose homescreen)
'''Product Risks''' (updated April 10, 2014)
*Shipping two Mozilla homescreens may needlessly devote QA/engineering resources to maintain both homescreens, putting other features at risk
*Offering two homescreens with differing grid layouts may require operators to define each separately - extra administrative overhead
'''Expected Release Target: 2.0''' (updated April 10, 2014)
'''References'''
Replaceable Homescreen Status: {{bug|898330}} '''COMPLETE'''
Replaceable Homescreen Status: {{bug|898330}} '''COMPLETE'''


==Edge Gestures Between Open Content==
==Edge Gestures Between Open Content==
On other mobile platforms, apps are like sealed containers. It’s hard to move between them without going home. That doesn’t feel very fluid to us. So we’re creating a new system that uses edge gestures to move through open apps and sites seamlessly. Swiping from the left or right edges of the screen, I can open an email, respond to a new notification, go back to a previous page while browsing, or multi task between two open apps. And I can quickly swipe from the top to see all my open windows. This new system feels more like the best of the web: connected and fluid.
'''What is it?''' It is a new method of interaction that uses edge gestures to move through open apps and sites seamlessly. Swiping from the left or right edges of the screen, I can open an email, respond to a new notification, go back to a previous page while browsing, or multi task between two open apps.
 
'''Current State''' (updated April 10, 2014)
*Working well currently but are disabled behind a developer option
*A number of updates will be made visuals/animations, particularly for changing orientation
*User testing is expected at the end of April in San Francisco
 
'''Product Risks''' (updated April 10, 2014)
*Since the system will automatically close apps when memory is low, swiping back to closed apps needs thorough testing on a variety of hardware
*Interference with navigation on third party apps (particularly games) may be uncovered during testing, requiring tweaks to swiping sensitivity


*Edge Gestures Status: https://wiki.mozilla.org/FirefoxOS/systemsfe#App_Edge_Gestures
'''Expected Release Target: 2.0''' (updated April 10, 2014)
*Edge Gestures meta bug: {{bug|918792}}  
 
'''References'''
*Edge Gestures Status: https://wiki.mozilla.org/FirefoxOS/systemsfe/epm#App_Edge_Gestures_.28Sheets.29
*Edge Gestures meta bug: {{bug|991849}}  
*Edge Gestures UX spec: https://mozilla.box.com/s/cxsuctcrdsm4aou5983u (updated Oct 11)
*Edge Gestures UX spec: https://mozilla.box.com/s/cxsuctcrdsm4aou5983u (updated Oct 11)
*Drawer concept (Edge gesture prerequisite): https://mozilla.box.com/s/10ab2eoqoabvx6dhh82v (updated Oct 23 - Does not render properly in box.com viewer. Please download the file to view it.)
*Drawer concept (Edge gesture prerequisite): https://mozilla.box.com/s/10ab2eoqoabvx6dhh82v (updated Oct 23 - Does not render properly in box.com viewer. Please download the file to view it.)
Confirmed users
222

edits