Firefox OS/Haida: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
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.)

Revision as of 15:12, 10 April 2014

Overview

Haida is a program that aims to deliver a distinct user experience for Firefox OS based on the DNA of Mozilla and the Web. The program encompasses concepts and features that span multiple aspects of the OS and will span a number of software releases.

The features Haida will introduce are:

  • Edge gesture based navigation
  • Browser integration into system
  • Universal search & navigation
  • Replaceable homescreen
  • Visual design refresh
  • Updated systems tray and notifications
  • Updated homescreen
  • New content model (bookmarks, etc)

Haida Phase 1

Phase 1 will deliver the foundation for most of the Haida capabilities including the following:

Visual Design Refresh

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)

  • Implementation of visual refresh underway and on track for common UI elements, email, calendar, clock, dialer, messaging, contacts, camera and lockscreen
  • Some elements were included as part of 1.4

Product Risks (updated April 10, 2014)

  • Coordination of delivery for visual refresh across entire product within one release may pose a challenge

Expected Release Target: 2.0 (updated April 10, 2014)

References

Updated Homescreen

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)

  • UX and engineering working to complete the first prototype in time user testing at the end of April in San Francisco
  • Evaluation of scrolling options and transition options to move between three and four column layouts ongoing
  • Platform scrolling improvements to improve vertical scrolling usability being explored

Product Risks (updated April 10, 2014)

  • Performance on lower end hardware hinders ability to use rich animations in transitions
  • Tradeoff between continuous scrolling and ability to find icons in the grid could be significant
  • Larger icon size likely requires modification to UX guidelines for third party apps and evangelizing existing partners to provide higher resolution icons

Expected Release Target: 2.0 (updated April 10, 2014)

References (updated April 10, 2014)

Replaceable Homescreen

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

Edge Gestures Between Open Content

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

Expected Release Target: 2.0 (updated April 10, 2014)

References

Browser Integration into System

Why is there a Firefox browser inside a Firefox phone? Why do we say "websites" go one place, while "apps" go another, when they're both just HTML/CSS/JavaScript? We felt strongly that there must be a more elegant, harmonious approach. So, in phase 1 of Haida we are unifying. 1) apps and sites are equal 2) search and browsing live in the system

Universal Search & Navigation

With the new search and navigation bar, I can get to my favorites, type in a URL, or discover a new app, from everywhere. The search bar lives at the top of the screen, and I just tap or swipe to open it. Think of it as the unification of the Awesome Bar from the browser and the adaptive app search from the homescreen. And because Firefox OS uses web apps, when I find what I want, even if it’s a new app, it opens right away. I don't need to install anything. Everything is instant and web-like.

Updated Settings Tray and Notifications

With the introduction of universal search and navigation, accessible using a download swipe from the top of the screen, notifications will shift to the bottom of the screen. Also, a new Settings Tray centralizes power user features in one place, helping keep the rest of the UI clean.

Haida Phase 2

Phase 2 will expand on the foundation laid in Phase 1, focusing on the following:

Updated Systems Tray and Notifications Part 2

Social notifications, like email and SMS, will be separated from system notifications, such as OS/app updates, with the latter being placed into the Systems Tray.

Extension of Customization Framework

We are an open platform. We win when people build cool stuff. The replaceable homescreen capabilities are planned to be productized such that users can swap out their device experience. We also plan to extend this to the Lockscreen.

Haida Phase 3

Edge Gestures within Apps

The paradigm of edge gestures to switch between open apps will be extended to navigation within apps. For example, if I open the Email app, click on a particular email and then on a link, I will now be viewing a webpage. Swiping from the left takes me back to the particular email I was on. Swiping back again takes me back to the email list view.

New Content Model

With the classic web approach I find something, I load it, and I enjoy it. It's low friction and easy. There’s no need to “install”. By comparison, other operating systems are quite complex, because they treat web apps differently from their native apps. With Firefox OS, I shouldn't need to install apps. If I find an app in the Marketplace that sounds cool, I should be able to tap on it, and it loads. No icon on the home app to worry about. It's instant gratification, without the maintenance. This is the direction we are heading in with Haida phase 3.

Theme Marketplace

Much as the Firefox browser has always upheld user choice over experience, we plan to enable designers and developers to create alternate home/lock screen experiences for Firefox OS and make them available for user download.

Misc. Related Improvements

  • Building Blocks
  • Performance

UX Roadmap/ Specs

In addition, please refer to the UX team's breakdown of features, which is meant to be a matching pair to the technical roadmap above: https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0At7p7w52w1tOdC1rQzRJdHUyMWROVTZTZ1dNQ2NoLXc&usp=sharing#gid=0

Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=Firefox_OS/Haida&oldid=963074"