Mobile/UI/Designs/TouchScreen/Proposal8: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 32: Line 32:




The idea behind showing frecency results immediately below the URL field is an attempt to give users some awesomebar-style benefit without having to type. Part of what makes the awesomebar powerful is that, with a keyboard, typing is the fastest way for a user to quickly narrow the field of what suggestions are appropriate.  On a mobile device, typing is not as easy, so there's value to offering our best guesses as to what the user is looking for before they need to type at all.
Showing frecency results immediately below the URL field is an attempt to give users some awesomebar-style benefit without having to type. Part of what makes the awesomebar powerful is that, with a keyboard, typing is the fastest way for a user to quickly narrow the field of what suggestions are appropriate.  On a mobile device, typing is not as easy, so there's value to offering our best guesses as to what the user is looking for before they need to type at all.


(We could, alternatively, try using a list of most visited sites rather than the frequency <i>and</i> recency set).
(We could, alternatively, try using a list of most visited sites rather than the frequency <i>and</i> recency set).
Line 53: Line 53:


===Bookmarking===
===Bookmarking===
Bookmarking works mostly the same way that it does in Firefox 3, but with a layout more adapted to this UI model:


http://people.mozilla.com/~madhava/files/mobile/radial2/r2_bookmarking2.png
http://people.mozilla.com/~madhava/files/mobile/radial2/r2_bookmarking2.png


Bookmarking works mostly the same way that it does in Firefox 3.




Line 62: Line 64:


http://people.mozilla.com/~madhava/files/mobile/radial2/r2_openbookmarks.png
http://people.mozilla.com/~madhava/files/mobile/radial2/r2_openbookmarks.png


'''mockups to come'''
'''mockups to come'''


==Tabs==
==Tabs==
Confirmed users
1,492

edits

Navigation menu