User Interfaces, Web Design, and UX

Transcript

1. 1.

   Interfaces Web design user experience

2. 2.

   I’m Adi @adi_dahiya on the interwebs I design & build

   web things
3. 3.

   What is good design? Mash of intuition & visual science

   Collection of hacks
4. 4.

   Design for hackers What goes into building a web app?

   happens when we go mobile? is user experience, anyway?
5. 5.

   A crash course in visual design

6. 6.

   Consciously design with white space

7. 7.

   Solve common white space problems with margin & padding @PennApps!

   Philadelphia, PA! 2013s.pennapps.com !     @PennApps! Philadelphia, PA! 2013s.pennapps.com !
8. 8.

   Exploit the visual shortcuts & cues that humans perceive

9. 9.

   None
10. 10.

    PLEASE JUST ALIGN ALL THE THINGS

11. 11.

    VISUAL HIERARCHY dictates your content

12. 12.

    It’s really just all about boxes within boxes

13. 13.

    Related elements go together (duh.) The most important elements get

    emphasized @PennApps! 792 ! !56! followers !following !
14. 14.

    None
15. 15.

    Owned by the logo (site) Global actions

16. 16.

    Owned by the activity stream (dashboard- specific)

17. 17.

    Owned by a user (artlog)

18. 18.

    because the post owns the box! These are post-specific actions

19. 19.

    You should (quite literally) outline your UI elements Dashboard page

    •  Header –  Logo –  Main navigation •  Dashboard •  Search •  Profile •  Sidebar –  Profile card –  Quick links •  Social stream …
20. 20.

    A NOTE ON COLOR

21. 21.

    Color is great for highlighting content, evoking emotion, & serving

    expectations
22. 22.

    But it’s easy to get carried away… too much variation

    is distracting & harmful
23. 23.

    Add color later Start with grayscale

24. 24.

    GOOD TYPE IS ALL YOU NEED

25. 25.

    Web Design is 95% Typography – Oliver Reichenstein, Information Architects

26. 26.

    None
27. 27.

    None
28. 28.

    X-height affects apparent size space efficiency visual impact

29. 29.

    None
30. 30.

    None
31. 31.

    None
32. 32.

    Establish a type hierarchy

33. 33.

    Use sensible measure Lorem ipsum dolor sit amet, consectetur adipiscing

    elit. Nunc aliquam nisl eget felis cursus vel pellentesque diam consequat. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Aliquam erat volutpat. Mauris justo dolor, commodo eu fringilla at, venenatis sed urna. Aliquam risus nibh, fringilla ut fermentum id, tempus id tellus. In hac habitasse platea dictumst. Donec et rutrum metus. Quisque tempor, turpis ut dignissim pharetra, risus erat semper neque, non blandit dolor massa in ante. Aliquam erat volutpat. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis egestas. Praesent nunc urna, lacinia at ultricies at, imperdiet sed enim. Ut semper, urna non eleifend molestie, est mi pretium ipsum, sed sodales nunc leo quis augue. Nullam nec leo ac purus porttitor sagittis sit amet vel lectus. Quisque et nisl elit. Nulla hendrerit bibendum hendrerit. Sed egestas ultricies purus, nec eleifend ligula eleifend
34. 34.

    Use sensible measure Lorem ipsum dolor sit amet, consectetur adipiscing

    elit. Nunc aliquam nisl eget felis cursus vel pellentesque diam consequat. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Aliquam erat volutpat. Mauris justo dolor, commodo eu fringilla at, venenatis sed urna. Aliquam risus nibh, fringilla ut fermentum id, tempus id tellus. In hac habitasse platea dictumst. Donec et rutrum metus. Quisque tempor, turpis ut dignissim pharetra, risus erat semper neque, non blandit dolor massa in ante. Aliquam erat volutpat. Pellentesque habitant morbi tristique senectus et netus et malesuada fames ac turpis
35. 35.

    What makes an interface 10 common UI/UX heuristics

36. 36.

    1.  Visibility of system status The system should always keep

    users informed about what is going on, through appropriate feedback within reasonable time.
37. 37.

    2.  Match between system & the real world The system

    should speak the users’ language, with words, phrases and concepts familiar to the user, rather than system-oriented terms. Follow real-world conventions, making information appear in a natural and logical order.
38. 38.

    None
39. 39.

    3.  USER CONTROL & FREEDOM Users often choose system functions

    by mistake and will need a clearly marked "emergency exit" to leave the unwanted state without having to go through an extended dialogue. Support undo and redo.
40. 40.

    4.  Consistency & standards Users should not have to wonder

    whether different words, situations, or actions mean the same thing. Follow platform conventions.
41. 41.

    5.  Error prevention Even better than good error messages is

    a careful design which prevents a problem from occurring in the first place. Either eliminate error prone conditions or check for them and present users with a confirmation option before they commit to the action.
42. 42.

    6.  Recognition rather than recall Minimize the user's memory load

    by making objects, actions, and options visible. The user should not have to remember information from one part of the dialogue to another. Instructions for use of the system should be visible or easily retrievable whenever appropriate.
43. 43.

    7.  Flexibility & efficiency of use Accelerators (unseen by the

    novice user) may often speed up the interaction for the expert user such that the system can cater to both inexperienced and experienced users. Allow users to tailor frequent actions.
44. 44.

    8.  Aesthetic & minimal design Dialogues should not contain information

    which is irrelevant or rarely needed. Every extra unit of information in a dialogue competes with the relevant units of information and diminishes their relative visibility.
45. 45.

    9.  Help users recognize, diagnose, and recover from errors Error

    messages should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
46. 46.

    None
47. 47.

    10.  Help & documentation Even though it is better if

    the system can be used without documentation, it may be necessary to provide help and documentation. Any such information should be easy to search, focused on the user's task, list concrete steps to be carried out, and not be too large.
48. 48.

    Wait a sec… wtf is ux?

49. 49.

    User experience Interactions Flows Tasks Value extracted

50. 50.

    None
51. 51.

    None
52. 52.

    None
53. 53.

    None
54. 54.

    Now that you mention mobile…

55. 55.

    None
56. 56.

    Decide what’s important, optimize for touch

57. 57.

    Where to go from here Getting started, getting inspired, and

    hacking design
58. 58.

    There are some awesome DESIGN Resources Here’s a sweet Kippt

    list I made of design-related links & resources https://kippt.com/adidahiya/design
59. 59.

    And you, too, can learn design! Study good design. Steal

    everything. Do side projects. Just practice.
60. 60.

    thanks! @adi_dahiya adi.dahiya14@gmail.com