Upgrade to Pro — share decks privately, control downloads, hide ads and more …

A User-First Approach to APIs - WordCamp Philly 2015

A User-First Approach to APIs - WordCamp Philly 2015

Helen Hou-Sandi

June 13, 2015
Tweet

More Decks by Helen Hou-Sandi

Other Decks in Technology

Transcript

  1. A User-First
    Approach to APIs
    Helen Hou-Sandí · WordCamp Philly 2015
    @helenhousandi

    View Slide

  2. @helenhousandi ·#wcphilly
    What’s a user?

    View Slide

  3. @helenhousandi ·#wcphilly
    What’s an API?

    View Slide

  4. @helenhousandi ·#wcphilly
    UI UX

    View Slide

  5. @helenhousandi ·#wcphilly
    DUX UX

    View Slide

  6. @helenhousandi ·#wcphilly
    APIs should not
    encourage bad UX.

    View Slide

  7. @helenhousandi ·#wcphilly
    APIs should not
    encourage bad UX.

    View Slide

  8. @helenhousandi ·#wcphilly
    APIs should encourage
    and enable good UX.

    View Slide

  9. @helenhousandi ·#wcphilly
    Security as
    user experience.

    View Slide

  10. @helenhousandi ·#wcphilly

    View Slide

  11. @helenhousandi ·#wcphilly
    So let’s rewrite the
    Settings API!

    View Slide

  12. @helenhousandi ·#wcphilly
    Good experiences
    need to be
    consistent experiences.

    View Slide

  13. @helenhousandi ·#wcphilly
    Admin Pattern Library

    View Slide

  14. @helenhousandi ·#wcphilly
    Fields API (?!)

    View Slide

  15. View Slide

  16. View Slide

  17. View Slide

  18. View Slide

  19. View Slide

  20. View Slide

  21. View Slide

  22. @helenhousandi ·#wcphilly
    Fields API.

    View Slide

  23. @helenhousandi ·#wcphilly
    Data is not generic.

    View Slide

  24. @helenhousandi ·#wcphilly
    The future of
    (fields in)
    WordPress.

    View Slide

  25. @helenhousandi ·#wcphilly
    &
    Q A

    View Slide