577
edits
Mobile/UI/Designs/TouchScreen/TouchBar: Difference between revisions
→The Url/Search Bar
| Line 11: | Line 11: | ||
[[Image:Touchbar Not Open.jpg]] | [[Image:Touchbar Not Open.jpg]] | ||
The URL/Search bar is considered to be the very top of every page. Like on the iPhone, it scrolls with the page, and thus can be scrolled out of view. To get to it, the user either scrolls to the top of the page or uses the touch | The URL/Search bar is considered to be the very top of every page. Like on the iPhone, it scrolls with the page, and thus can be scrolled out of view. To get to it, the user either scrolls to the top of the page or uses the touch corners along the top of the display once the url bar has scrolled out of view. | ||
[[Image:Touchbar Only Corners.jpg]] | |||
Because the location of the url/search bar is part of the page, the interface retains a sense of physicality -- the user always knows where to find it because of the consistency of physical objects. However, on long pages, it is time consuming to scroll to the top of the page. Automating the scroll is a solution, but it fails a bit because that mechanisms throws away user's current location. | |||
The bar borrows from [[Mobile/UI/Designs/TouchScreen/Proposal8|Madhava's Proposal8]] in that when a url is entered, the button reads "go"; and when a non-url is entered, the button reads "search". Similarly, the bar borrows from [[Mobile/UI/Designs/TouchScreen/Proposal8|Proposal8]] in that because typed characters are at a premium, the url bar should do it's best to be awesome-like and start giving results (based on frequency/recency of visits) even before typing has occurred. | The bar borrows from [[Mobile/UI/Designs/TouchScreen/Proposal8|Madhava's Proposal8]] in that when a url is entered, the button reads "go"; and when a non-url is entered, the button reads "search". Similarly, the bar borrows from [[Mobile/UI/Designs/TouchScreen/Proposal8|Proposal8]] in that because typed characters are at a premium, the url bar should do it's best to be awesome-like and start giving results (based on frequency/recency of visits) even before typing has occurred. | ||