Evaluating Technology

Evaluating Technology

We work with technology every day. And every day it seems like there's more and more technology to understand: graphic design tools, build tools, frameworks and libraries, not to mention new HTML, CSS and JavaScript features landing in browsers. How should we best choose which technologies to invest our time in? When we decide to weigh up the technology choices that confront us, what are the best criteria for doing that? This talk will help you evaluate tools and technologies in a way that best benefits the people who use the websites that we are designing and developing. Let's take a look at some of the hottest new web technologies like service workers and web components. Together we will dig beneath the hype to find out whether they will really change life on the web for the better.

5ad82c5ba0264363974af89deb743c20?s=128

Jeremy Keith

April 04, 2017
Tweet

Transcript

  1. EVALUATING TECHNOLOGY

  2. None
  3. A C G T

  4. specialisation ubiquity cooperation

  5. None
  6. We shape our tools and thereafter our tools shape us.”

    “ —John Culkin
  7. specialisation ubiquity cooperation

  8. None
  9. None
  10. Chindōgu

  11. Chindōgu

  12. Chindōgu

  13. Chindōgu

  14. Chindōgu

  15. Chindōgu

  16. Chindōgu

  17. hardware software human

  18. None
  19. None
  20. hardware software human

  21. WWW

  22. computers internet electricity WWW industrialisation

  23. HTTP WWW URLs HTML

  24. None
  25. Humans are allergic to change.” “ —Grace Hopper

  26. HTTP WWW URLs HTML SGML DNS TCP/IP

  27. SGML <body> <title> <p> <h1> <h2> <h3> <ol> <li> <ul>

    <dl> <dt> <dd>
  28. HTML <article> <section> <main> <aside> <figure> <footer> <header>

  29. HTML <canvas> <video> <datalist> <audio> <picture>

  30. HTML 5 document conformance requirements should be designed so that

    web content can degrade gracefully in older or less capable user agents, even when making use of new elements, attributes, APIs and content models.” “ —HTML Design Principles
  31. principles.adactio.com

  32. principles goals patterns

  33. HTML <canvas> <video> <datalist> <audio> <picture>

  34. How well does it work?

  35. How well does it fail?

  36. None
  37. None
  38. None
  39. service workers

  40. None
  41. How well does it work?

  42. None
  43. How well does it fail?

  44. web components shadow DOM custom elements

  45. HTML <canvas> <video> <datalist> <audio> <picture>

  46. <mega-menu> <slippy-map> <off-canvas> <image-gallery> <modal-lightbox>

  47. <mega-menu> <link rel="import" href="mega-menu.html"> HTML CSS JS

  48. How well does it work?

  49. None
  50. How well does it fail?

  51. <image-gallery> <img src="…" alt="…"> <img src="…" alt="…"> <img src="…" alt="…">

    </image-gallery>
  52. <image-gallery> </image-gallery>

  53. <body> <shop-app> </shop-app> <script>…</script> </body> shop.polymer-project.org

  54. service workers web components

  55. ajax responsive web design progressive web app the extensible web

  56. service worker manifest file progressive web app HTTPS + +

    =
  57. None
  58. None
  59. None
  60. Who benefits?

  61. developers users

  62. sass less git gulp npm jQuery bootstrap angular react ember

  63. What are the assumptions?

  64. Software, like all technologies, is inherently political. Code inevitably reflects

    the choices, biases and desires of its creators.” “ —Jamais Cascio
  65. None
  66. The street finds its own uses for things.” “ —William

    Gibson Burning Chrome
  67. None
  68. Technology is neither good nor bad; nor is it neutral.”

    “ —Melvin Kranzberg
  69. None
  70. None
  71. What Technology Wants The Inevitable

  72. amish The Amish have the undeserved reputation of being luddites,

    of people who refuse to employ new technology. The Amish are steadily adopting technology — at their pace. They are slow geeks.” “ —Kevin Kelly -ish
  73. None
  74. How well does it work? How well does it fail?

    Who benefits? What are the assumptions?
  75. None
  76. Thank you