$30 off During Our Annual Pro Sale. View Details »

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.

Jeremy Keith

April 04, 2017
Tweet

More Decks by Jeremy Keith

Other Decks in Technology

Transcript

  1. EVALUATING
    TECHNOLOGY

    View Slide

  2. View Slide

  3. A
    C
    G
    T

    View Slide

  4. specialisation
    ubiquity
    cooperation

    View Slide

  5. View Slide

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

    —John Culkin

    View Slide

  7. specialisation
    ubiquity
    cooperation

    View Slide

  8. View Slide

  9. View Slide

  10. Chindōgu

    View Slide

  11. Chindōgu

    View Slide

  12. Chindōgu

    View Slide

  13. Chindōgu

    View Slide

  14. Chindōgu

    View Slide

  15. Chindōgu

    View Slide

  16. Chindōgu

    View Slide

  17. hardware
    software
    human

    View Slide

  18. View Slide

  19. View Slide

  20. hardware
    software
    human

    View Slide

  21. WWW

    View Slide

  22. computers
    internet
    electricity
    WWW
    industrialisation

    View Slide

  23. HTTP
    WWW
    URLs HTML

    View Slide

  24. View Slide

  25. Humans are allergic to change.”

    —Grace Hopper

    View Slide

  26. HTTP
    WWW
    URLs HTML
    SGML
    DNS
    TCP/IP

    View Slide

  27. SGML









    View Slide

  28. HTML







    View Slide

  29. HTML





    View Slide

  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

    View Slide

  31. principles.adactio.com

    View Slide

  32. principles
    goals
    patterns

    View Slide

  33. HTML





    View Slide

  34. How well does it work?

    View Slide

  35. How well does it fail?

    View Slide

  36. View Slide

  37. View Slide

  38. View Slide

  39. service workers

    View Slide

  40. View Slide

  41. How well does it work?

    View Slide

  42. View Slide

  43. How well does it fail?

    View Slide

  44. web components
    shadow DOM
    custom elements

    View Slide

  45. HTML





    View Slide






  46. View Slide


  47. href="mega-menu.html">
    HTML
    CSS
    JS

    View Slide

  48. How well does it work?

    View Slide

  49. View Slide

  50. How well does it fail?

    View Slide






  51. View Slide



  52. View Slide






  53. shop.polymer-project.org

    View Slide

  54. service workers
    web components

    View Slide

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

    View Slide

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

    View Slide

  57. View Slide

  58. View Slide

  59. View Slide

  60. Who benefits?

    View Slide

  61. developers users

    View Slide

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

    View Slide

  63. What are the assumptions?

    View Slide

  64. Software, like all technologies, is inherently
    political. Code inevitably reflects the choices,
    biases and desires of its creators.”

    —Jamais Cascio

    View Slide

  65. View Slide

  66. The street finds its own uses for things.”

    —William Gibson
    Burning Chrome

    View Slide

  67. View Slide

  68. Technology is neither good nor bad;
    nor is it neutral.”

    —Melvin Kranzberg

    View Slide

  69. View Slide

  70. View Slide

  71. What Technology Wants
    The Inevitable

    View Slide

  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

    View Slide

  73. View Slide

  74. How well does it work?
    How well does it fail?
    Who benefits?
    What are the assumptions?

    View Slide

  75. View Slide

  76. Thank you

    View Slide