Priorities: show an
action, or put it in
overflow menu?
Slide 26
Slide 26 text
No :hover.
Slide 27
Slide 27 text
Visible controls,
succinct
explanations.
Slide 28
Slide 28 text
Finger-friendly
tap targets.
Slide 29
Slide 29 text
Limited maximum
number of items per
screen - even less
with keyboard.
Slide 30
Slide 30 text
Obstruction of view.
Slide 31
Slide 31 text
By hand or keyboard.
Slide 32
Slide 32 text
Easy, fast inputs.
Slide 33
Slide 33 text
Not everything can fit
into one screen, but
everything can be
easy to understand.
Slide 34
Slide 34 text
OS-specific design.
Slide 35
Slide 35 text
No content
Slide 36
Slide 36 text
Helvetica Roboto
Slide 37
Slide 37 text
Helvetica
Avenir
Roboto
Slide 38
Slide 38 text
No content
Slide 39
Slide 39 text
Mobile design patterns.
Slide 40
Slide 40 text
Chat bubbles from
sides, input field in
the bottom, above
the keyboard.
Slide 41
Slide 41 text
Assumption about little
computer literacy.
Slide 42
Slide 42 text
Screen sizes.
Slide 43
Slide 43 text
Delight vs Features.
Slide 44
Slide 44 text
Little space
Branding through UI
Few actions per screen
Visible UI elements
Large UI elements
Obstruction of view
OS-specific design
Mobile design patterns
Friendly to new users
Perfectly fitting the screen
Delightful UI execution