Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Responsive principles

2,017 views

Published on

Presented at Float Mobile eLearning Symposium, at Chicago TechWeek, on 25 July 2012.

Buzzwords and trends in design, development and process hold much weight in our industries, and foster much arguing and staking out of opposite positions. But more of these are in fundamental agreement than is generally acknowledged, and merging approaches, much like collaborating with a varied team, can yield the most useful results.Steven will discuss the underlying principles of responsive & fluid design, progressive enhancement, adaptive design, device detection, multi-platform design, cross-platform development processes, and mobile device capabilities. He will present one possible unifying theory of how you can not just develop the shiniest iOS app, but design the best experience for your users, on every screen and with every interaction.

Published in: Technology, Education
  • Be the first to comment

Responsive principles

  1. 1. ResponsivePrinciplesMore than designing for size@shoobe01 #float2012 1
  2. 2. Learn by typing, talking,and sharing. 2
  3. 3. Select a platformfirst, right? 3
  4. 4. Lies, damned lies,and statistics. 4
  5. 5. You are screwingyourself. 5
  6. 6. Fragmentationis great. 6
  7. 7. Design for everyplatform, and everyscreen. 7
  8. 8. Design responsively,right? 8
  9. 9. Responsive designisn’t new. 9
  10. 10. But that’s okay. 10
  11. 11. Device detection andserver-side software. 11
  12. 12. RESS isn’t new, either. 12
  13. 13. But it’s a convenientacronym. 13
  14. 14. 14
  15. 15. Design beyond pixels. 15
  16. 16. Percent? Em?Point, pica,mm, inch,twip. 16
  17. 17. Design for the real world. 17
  18. 18. 18
  19. 19. 19
  20. 20. 20
  21. 21. 21
  22. 22. 22
  23. 23. Respond to morethan scale. 23
  24. 24. 24
  25. 25. Principles >Patterns >Templates >Pages 25
  26. 26. Features != pages 26
  27. 27. 27
  28. 28. Design for every screen. 28
  29. 29. Then design foreach screen. 29
  30. 30. Enhance for eachplatform. 30
  31. 31. Stick to your principles. 31
  32. 32. Design to makedecisions. 32
  33. 33. Products,not platforms. 33
  34. 34. Customers,not users. 34
  35. 35. Is it still any good? 35
  36. 36. Is it still the rightthing to make? 36
  37. 37. Then change yourprinciples. 37
  38. 38. Execute for every screen. 38
  39. 39. Data and services first. 39
  40. 40. Build for the future. 40
  41. 41. Layers and planning. 41
  42. 42. Do everything once. 42
  43. 43. Platform teams shouldborrow and cheat. 43
  44. 44. Yes. 44
  45. 45. 45
  46. 46. Don’t copy thatlast chart. 46
  47. 47. Actually, don’t copyanything I’ve done. 47
  48. 48. Principles >Patterns >Templates 48
  49. 49. Principles >Practices >Tactics 49
  50. 50. Responsive,native,physical,buildable,extensible. 50
  51. 51. Steven Hoobersteven@4ourth.com+1 816 210 0455@shoobe01shoobe01 on:www.4ourth.com 51

×