Open rubinahaddad opened 10 years ago
A. Please indicate which devices, browsers, and operating systems were tested (Desktop/Mobile/Tablet): Laptop: ASUS Windows 8, Chrome 32.0.1700.72 , Firefox 26. iPhone iOS7, Safari (latest). Nexus 7, Android 4.2.1 on Chrome 31.0.1650.59 and Firefox 26.0.1
B. Provide status feedback
C. Match real world conventions YES
D. Apply standards and ensure consistency
E. Help users recognize, prevent and recover from errors Laptop: YES iPhone/tablet: NO once I started scrolling within the twitter box (unintentionally), it's difficult to determine how to get out of that and go back to scrolling only the page.
F. Design for human interaction Laptop: yes iphone/tablet: larger thumbs would have a hard time with the scroll bars, see #3 in first section above.
a. Is the layout intuitive? YES
b. Are the interactions intuitive? YES
G. Keep it simple
IPad, 4th gen., iOS 6.1.3: Safari, Chrome v. 31. Screen resolution 2048 x 1536 px. Reviewed in both landscape and portrait orientation.
Blackberry Curve 9360, OS 7.1, default browser. Screen resolution 480 x 360 px. Landscape orientation only.
Device | OS | Browsers |
---|---|---|
Laptop (24 inch Monitor) | Windows 8.1 | IE 11.0.3 |
Laptop (24 inch Monitor) | Windows 8.1 | FF 27.0.1 |
Laptop (24 inch Monitor) | Windows 8.1 | Chrome 33.0.1750.146 m |
If you know how it all works, yes. My issue is not with the implementation, but with the original design.
Yes
Yes
Yes
The twitter "filer" (top left) is not intuitive as to its purpose. Expand/Collapse behaviour is a bit unusual, but not really a problem. Launching a new page to send a new tweet is unexpected.
Yes
Not exactly. The Embedded Timeline on the Twitter site has “Tweet to …” at the bottom, where we have “Tweet …” I think “Tweet to …” is clearer.
Yes
N/A
Mostly. The scroll bar doesn’t scale correctly on some browsers.
N/A
N/A
N/A
I have issues with the original design, but the embedding seems fine.
I have issues with the original design, but the embedding seems fine.
Yes
N/A
Yes
Yes
Yes
http://wet-boew.github.io/v4.0-ci/demos/twitter/twitter-en.html April 15, 2014
Device | OS | Browsers |
---|---|---|
Laptop: ASUS | Windows 8 | Chrome 32.0.1700.72 |
Laptop: ASUS | Windows 8 | Firefox 26. |
iPhone | iOS7 | Safari (latest) |
IPad, 4th gen | iOS 6.1.3: | Safari, |
IPad, 4th gen | iOS 6.1.3: | Chrome v. 31. Screen resolution 2048 x 1536 px. Reviewed in both landscape and portrait orientation. |
Blackberry Curve 9360 | OS 7.1, | Default browser. Screen resolution 480 x 360 px. Landscape orientation only. |
Nexus 7 | Android 4.2.1 | Chrome 31.0.1650.59 |
Nexus 7 | Android 4.2.1 | Firefox 26.0.1 |
Laptop (24 inch Monitor) | Windows 8.1 | IE 11.0.3 |
Laptop (24 inch Monitor) | Windows 8.1 | FF 27.0.1 |
Laptop (24 inch Monitor) | Windows 8.1 | Chrome 33.0.1750.146 m |
The embedded Timeline seems like an effective embedding of the Twitter Timeline widget – warts and all. Most of the issues reviewers raised were all with the original code. That does not make them less important, however. Nevertheless, it makes no sense for us to reinvent Twitter’s wheel. To do so would only confuse Twitter users
The issues and suggestions below focus on small tweaks that we can make using the API, that do not significantly interfere with the Twitter interaction style.
Please perform a heuristic review of the following component: Twitter embedded timeline example.
Performing a heuristic evaluation