FirefoxMobile-SmartTabs: Difference between revisions

Line 20:

[[File:TabWireframes-ProposedAlpha.png‎]]

Most of the ideas combined:Better rendering, redesigned close button, favicon, smart image crop.

The favicon was included though few people remembered logos in the [[#Study]]. This was done because the favicon is often a good color-clue which means it includes the typical colors of the page it represents (though not always, e.g. [www.mozilla.com mozilla])

If a page is well known (the most user did only know few pages from the set) it is more likely that they "learned" the favicon and can use it as efficient retrieval clue.

==Ideas for Improvement==

===Make Closing ~~Botton~~ Less ~~Obstrusive~~===

===Make Closing Button Less Obtrusive===

(Discussion of the wireframes is in the same order: from top to bottom.)

[[File:MozillaMobile-SmallerCloseMoveClose.png | right | Relocate Button Wireframe]]

Line 34:

Line 38:

*Contra:

**The target area has probably to move down a bit too; needs testing on a touchscreen-device.

**One Problem that could occur is that people will probably be more likely to tap below an item (they still see it) than to tap above it (it covers even more than usually). The ~~availiable~~ target area could become too small because of that.

**One Problem that could occur is that people will probably be more likely to tap below an item (they still see it) than to tap above it (it covers even more than usually). The available target area could become too small because of that.

'''Move button to the right edge'''

Line 48:

Line 52:

[[File:MozillaMobile_pageCrop.png | right ]]

===Smarter Page Crop===

Concept: Choose a better crop of the page as thumbnail. ~~Acually~~ it already works pretty well, since mainly the upper left corner is present due to the small screen of the mobile devices. In my tests a 480px height crop ~~seemd~~ to be decent (the height is more important, since distinctive visual features are often located on the left side)

Concept: Choose a better crop of the page as thumbnail. Actually it already works pretty well, since mainly the upper left corner is present due to the small screen of the mobile devices. In my tests a 480px height crop seemed to be decent (the height is more important, since distinctive visual features are often located on the left side)

*Pro: Choosing a more representative part of the page means better recognition and more ~~differenciation~~ between similar pages.

*Pro: Choosing a more representative part of the page means better recognition and more differentiation between similar pages.

*Contra: ---

Line 90:

Line 94:

==Study 1: What do people recall about webpages==

==Study==

'''What do people recall about webpages'''

Conducted by Bastian Bügler and Jan Dittrich

===Goal===

@@ Line 20: / Line 20: @@
 [[File:TabWireframes-ProposedAlpha.png‎]]
 Most of the ideas combined:Better rendering, redesigned close button, favicon, smart image crop.
+The favicon was included though few people remembered logos in the [[#Study]]. This was done because the favicon is often a good color-clue which means it includes the typical colors of the page it represents (though not always, e.g. [www.mozilla.com mozilla])
+If a page is well known (the most user did only know few pages from the set) it is more likely that they "learned" the favicon and can use it as efficient retrieval clue.
 ==Ideas for Improvement==
-===Make Closing Botton Less Obstrusive===
+===Make Closing Button Less Obtrusive===
 (Discussion of the wireframes is in the same order: from top to bottom.)
 [[File:MozillaMobile-SmallerCloseMoveClose.png | right | Relocate Button Wireframe]]
@@ Line 34: / Line 38: @@
 *Contra:
 **The target area has probably to move down a bit too; needs testing on a touchscreen-device.
-**One Problem that could occur is that people will probably be more likely to tap below an item (they still see it) than to tap above it (it covers even more than usually). The availiable target area could become too small because of that.
+**One Problem that could occur is that people will probably be more likely to tap below an item (they still see it) than to tap above it (it covers even more than usually). The available target area could become too small because of that.
 '''Move button to the right edge'''
@@ Line 48: / Line 52: @@
 [[File:MozillaMobile_pageCrop.png | right ]]
 ===Smarter Page Crop===
-Concept: Choose a better crop of the page as thumbnail. Acually it already works pretty well, since mainly the upper left corner is present due to the small screen of the mobile devices.  In my tests a 480px height crop seemd to be decent (the height is more important, since distinctive visual features are often located on the left side)
+Concept: Choose a better crop of the page as thumbnail. Actually it already works pretty well, since mainly the upper left corner is present due to the small screen of the mobile devices.  In my tests a 480px height crop seemed to be decent (the height is more important, since distinctive visual features are often located on the left side)
-*Pro: Choosing a more representative part of the page means better recognition and more differenciation between similar pages.
+*Pro: Choosing a more representative part of the page means better recognition and more differentiation between similar pages.
 *Contra: ---
@@ Line 90: / Line 94: @@
-==Study 1: What do people recall about webpages==
+==Study==
+'''What do people recall about webpages'''
 Conducted by Bastian Bügler and Jan Dittrich
 ===Goal===