Designing in the Future

72635a06781143410d1ef4a25bf164ae?s=47 Mattijs Bliek
October 06, 2014

Designing in the Future

This talk is about how our process of designing for the web has evolved over time. It takes a look at what tools are needed in the current landscape and how tools can grow along with us.

72635a06781143410d1ef4a25bf164ae?s=128

Mattijs Bliek

October 06, 2014
Tweet

Transcript

  1. Designing in the Future @mattijsbliek

  2. Designer & developer @grrr_nl

  3. Grrr Full service agency

  4. Disclaimer #1 !

  5. This talk is not actually about Designing in the Future

    Disclaimer #1
  6. Disclaimer #2 !

  7. I really don’t know what I’m doing Disclaimer #2

  8. I have a problem

  9. I have a problem with tools

  10. 1. Design process then and now 2. Tools 3. The

    designer of the future
  11. 1. Design process, then and now

  12. Short evolution of the web

  13. 1991

  14. 1993

  15. 1996 Cascading Style Sheets, level 1 W3C Recommendation 17 Dec

    1996
  16. 1998

  17. http://216.139.218.247/sites/marines/

  18. https://web.archive.org/web/20020831071812/http://www.tolerance.org/

  19. None
  20. None
  21. None
  22. HTML, CSS, JavaScript Open standards

  23. Process

  24. strategy content design development

  25. None
  26. None
  27. This is incredibly inefficient!

  28. None
  29. strategy content development design design

  30. Responsive web design

  31. None
  32. None
  33. Pixel perfect design is out

  34. design strategy content development

  35. None
  36. development strategy content design

  37. None
  38. None
  39. Further possibilities

  40. design development strategy content

  41. design development strategy content

  42. design development strategy content design development strategy content design development

    strategy content
  43. 2. Tools

  44. None
  45. What do we need?

  46. What do we need? 1. Fast way to try out

    visual ideas
  47. What do we need? 1. Fast way to try out

    visual ideas 2. Fluid designs
  48. What do we need? 1. Fast way to try out

    visual ideas 2. Fluid designs 3. The ability to display time
  49. What do we need? 1. Fast way to try out

    visual ideas 2. Fluid designs 3. The ability to display time 4. Developer friendliness
  50. What do we need? 1. Fast way to try out

    visual ideas 2. Fluid designs 3. The ability to display time 4. Developer friendliness 5. ???
  51. None
  52. None
  53. None
  54. youtube.com/watch?v=Q8TXgCzxEnw

  55. Why do we need single tool for this?

  56. None
  57. Adobe After Effects

  58. Apple Keynote

  59. Facebook Origami

  60. FramerJS

  61. Use each tool where it fits best

  62. 3. The designer of the future

  63. Credits: http://www.w3.org/History/19921103-hypertext/hypertext/WWW/TheProject.html http://info.cern.ch/NextBrowser1.html http://www.flickr.com/photos/10247381@N02/10414036226 https://www.flickr.com/photos/nasa_goddard/8380692070 http://www.changefactory.com.au/our-thinking/articles/ineffective-and-inefficient-call-centres/ http://www.markboulton.co.uk/journal/a-richer-canvas http://next.theguardian.com/blog/container-model-blended-content/ Thanks for

    listening