Fennec/Features/disc: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 39: Line 39:


=== '''First-run Concepts'''  ===
=== '''First-run Concepts'''  ===


'''Idea #1:'''  
'''Idea #1:'''  
Line 70: Line 71:
This idea is basically the same as #3, except we show the sidebar coming out of the same time. The advantage here is that it is much quicker, however it illustrates a state of the why they can never actually happened.  
This idea is basically the same as #3, except we show the sidebar coming out of the same time. The advantage here is that it is much quicker, however it illustrates a state of the why they can never actually happened.  


 
<br>


'''''UX Recommendation: Idea #3'''''  
'''''UX Recommendation: Idea #3'''''  

Revision as of 20:17, 25 April 2011

Feature Status ETA Owner
Better first-run / Browser discoverability Concept 2011-07-01 Thomas Arend

Summary

Guide users on first run. Help them discover and understand features like side panels, awesome screen, sync, bookmarks, gestures, etc.

Team

UX: Brian Dils, Madhava Enros

Release Requirements

Next Steps

Open Issues

Related Bugs & Dependencies

Designs

There are several different concepts we can explore for first-run discoverability, as well as a few other ideas that might aid discoverability while the users are in product.

First-run Concepts

Idea #1:

http://www.youtube.com/watch?v=1Ph3s2Zu2Xo

The idea here would be to show the user a walk-through video with a dummy hand. This would be the most failsafe idea because we would show users exactly how to operate the UI. The negative here, is that it is very heavy-handed and assumes that our users don't know how to operate a touchscreen.


Idea #2:

http://www.youtube.com/watch?v=Jem7CgbM034

Essentially the same as idea #1, except we wouldn't show the dummy hand.


Idea #3:

http://www.youtube.com/watch?v=49Yh3UcoPS4

The idea here would be to take out any extraneous elements of the tutorial, such as the hands and/or notes. This idea is necessary because the notes are going to be hard to localize.


Idea #4:

http://www.youtube.com/watch?v=xmxQw_RExbo

This idea is basically the same as #3, except we show the sidebar coming out of the same time. The advantage here is that it is much quicker, however it illustrates a state of the why they can never actually happened.


UX Recommendation: Idea #3


Additional Concepts


Translucent Sidebars:

http://www.youtube.com/watch?v=NzXPju5nW6o

One of the reasons the sidebars are so hard to find is because they are pinned all the way to the side of the webpage. In addition to discoverability, this is also a problem because the user has to move away from the spot in the page they're currently looking at just to get to the sidebars. The idea here is that an "accelerator gesture", such as a double finger swipe, will bring a sidebar out in a translucent state. This would not conflict with the way the sidebars usually act. As you can see from the video, as the user swipes to the side, the translucency goes away.


New tab animation:

http://www.youtube.com/watch?v=n9XrI_DIEbQ

Another discoverability problem that we have is that users don't know where their tabs are. We could add "new tab" to the android menu. When the users opens a new tab from the android menu, we would show this interstitial animation that would message to the user where their new tab resides.

Test Plans

Goals/Use Cases

Non-Goals

Other Documentation

Legend (remove if you like)

  Healthy: feature is progressing as expected.
  Blocked: feature is currently blocked.
  At Risk: feature is at risk of missing its targeted release.
ETA Estimated date for completion of the current feature task. Overall ETA for the feature is the product release date.