7. Where to start?
Usage scenario
Setting
Device vs Device Categories
(Form Factors)
8. "The user selects from a
selection of analog lms,
lenses and effects and takes
photographs that look old
school"
?
9. Hipstamatic
"The user selects from a
selection of analog lms,
lenses and effects and takes
photographs that look old
school"
10. "The user is running wearing a
tag-equipped shoe and his run
gets recorded to allow him to
map it, track his progress and
compare it to others
?
performances"
11. Nike+
"The user is running wearing a
tag-equipped shoe and his run
gets recorded to allow him to
map it, track his progress and
compare it to others
performances"
12. "Based on links and content
shared by friends on social
networks the user gets
compiled an easy to use e-
magazine that allows to
browse and read the content
?
in a convenient way"
13. Flipboard
"Based on links and content
shared by friends on social
networks the user gets
compiled an easy to use e-
magazine that allows to
browse and read the content
in a convenient way"
32. Device Cheat Sheet
Orientation Accelerometer Proximity
Landscape Tilt User holds phone next to ear
Portrait Rotate
Bottom Up Shake Camera
Upside Down Custom motion gestures Live Image
It can change! Orientation to gravity Still Image
Colour Detection
Touch-Gestures Location (GPS) Shape Detection
Pan, Pinch, Swipe or custom User’s location
Avoid similar gestures Movement Sound Input
Up to 11 simultaneous touches Current speed Volume
(iPad)
Precision of approx. 2m Frequency
Particular Sounds/Noise
Editor's Notes
\n
\n
\n
\n
\n
\n
\n
\n
\n
Define your usage scenarios and make sure that these apply to your design. If it doesn’t apply anymore you either got the usage scenario wrong or your design doesn’t work.\n\nDo you recognise them all?\n
Define your usage scenarios and make sure that these apply to your design. If it doesn’t apply anymore you either got the usage scenario wrong or your design doesn’t work.\n\nDo you recognise them all?\n
Define your usage scenarios and make sure that these apply to your design. If it doesn’t apply anymore you either got the usage scenario wrong or your design doesn’t work.\n\nDo you recognise them all?\n
\n
\n
\n
\n
\n
\n
Location – Why is it important? \n\nIt tells you about the situation the user finds himself in. \nAre there potentially other people around? \nLocations can tell you about the likelihood of network conditions – WiFi, cellular or even no signal at all\nOutside? Think about what happens if it’s raining? User wouldn't pull the device out of his pocket. \nFurthermore consider if the your design needs to work with multiple or changing locations.\n\nOfficeprobably WiFi, people are around\nHomeprobably WiFi\nParkonly cellular (streaming video really a good idea?)\nPlaneexpect no signal at all\nTrainprobably bad signal\nBusonly cellular\n
Usage time tells you about the attention span you can expect from the user. \n\nThis gives you valuable information about the possible level of complexity you can implement in your design.\nIf you need to cover a broader range of usage time make sure that you add more complex functionality in a way that doesn't interfere if users don't want to get into that level of complexity.\n\nPhoneusage time from seconds to minutes\nNO splash screen (!), launch quickly\nNO intros - you shouldn’t do intros anyway\nget to the point\nTabletanything between seconds and minutes, maybe an hour or two\nLaptopfrom minutes up to a full working day\nDesktoplikely hours, full working day\n
Different light conditions tell you whether you should go for a high contrast colour palette, a bright interface or a dark one\n\nIt also allows you to estimate the level of reflection you're dealing with or how visible fingerprints will appear on screen. \nBear in mind that light conditions could also change over time.\n\nA music tool or entertainment app that is supposed to work at night should probably feature a dark interface\n\nReally easy to test, just test images of colours on the devices.\n
Posture – It tells you a lot of things.\n\nIs the user is on the go or resting? Can one or two hands be used to operate the device.\nWhat physical activity will feel natural – think of hand or arm movement. It could also be the user's belly hiding the bottom bit of the display, or even accidentally touch the buttons :)\n\n
Besides the setting there are device features and characteristics, too. Consider how you can make use of them as you might have limited screen estate and things like sensors can help you to add non-visual elements to your interface. Combining these things with a graphical interface allows \n\n
\n
\n
\n
\n
\n
\n
\n
Visual indicators\nshow activity, spinning wheel\n\n\nSound feedback\nVibration if something has happened\n
Porsche and Volkswagen are effectively the same company. The two cars a even built on the same technology platform.\n\nWhat’s the difference between the two cars?\n\nIgnition keys in Porsches are always on the other side! Porsche drivers would be upset if it would be in the place of any other car.\n\nThat’s the same with different software platforms.\n\n
Porsche and Volkswagen are effectively the same company. The two cars a even built on the same technology platform.\n\nWhat’s the difference between the two cars?\n\nIgnition keys in Porsches are always on the other side! Porsche drivers would be upset if it would be in the place of any other car.\n\nThat’s the same with different software platforms.\n\n
Porsche and Volkswagen are effectively the same company. The two cars a even built on the same technology platform.\n\nWhat’s the difference between the two cars?\n\nIgnition keys in Porsches are always on the other side! Porsche drivers would be upset if it would be in the place of any other car.\n\nThat’s the same with different software platforms.\n\n
Porsche and Volkswagen are effectively the same company. The two cars a even built on the same technology platform.\n\nWhat’s the difference between the two cars?\n\nIgnition keys in Porsches are always on the other side! Porsche drivers would be upset if it would be in the place of any other car.\n\nThat’s the same with different software platforms.\n\n
Porsche and Volkswagen are effectively the same company. The two cars a even built on the same technology platform.\n\nWhat’s the difference between the two cars?\n\nIgnition keys in Porsches are always on the other side! Porsche drivers would be upset if it would be in the place of any other car.\n\nThat’s the same with different software platforms.\n\n
Porsche and Volkswagen are effectively the same company. The two cars a even built on the same technology platform.\n\nWhat’s the difference between the two cars?\n\nIgnition keys in Porsches are always on the other side! Porsche drivers would be upset if it would be in the place of any other car.\n\nThat’s the same with different software platforms.\n\n
This is exactly the reason why things tend to work slightly different in iOS and Android.\n\nBack button, iOS always top left, Android devices always have a physical back button. Hence there is no need to implement one on screen.\n
Same for menus\n\nThere is a physical menu button on all Android devices, unlike iOS devices. Hence you need to come up with a different solution.\n\nAnother nice overview can be found at\nhttp://johnnyholland.org/2010/09/06/android-iphone-app-design-is-it-twice-the-work/\n\nFurthermore have a look at user interface or human interface guidelines (HIG) of the platform you’re targeting.\nhttp://www.theuxbookmark.com/2010/08/interaction-design/a-monster-list-of-ui-guidelines-style-guides\n
