The Design Of Everyday APIs

The Design Of Everyday APIs

Well-designed APIs are a joy to use; poorly-designed APIs are cumbersome, confusing and frustrating, just like everyday things. During this session Arnaud Lauret, the API Handyman, makes a parallel between everyday things design and API design to expose simple but fundamentals design principles.
Is using knobs is better than using buttons? API design is more than REST vs GraphQL vs gRPC vs whatever existing or yet to come API style. Great design can be achieved using any type of API. Would you buy a Kitchen Radar 3000? Are you able to use any washing machine instantly without reading user manual? Why QWERTY layout was invented? Like everyday things, APIs must have a clear purpose, must be used easily by anyone and are constrained by their environment.

Ba9efb844dce84e8b0c7d0f98535895d?s=128

Arnaud Lauret API Handyman

September 25, 2018
Tweet

Transcript

  1. 2.
  2. 3.
  3. 5.
  4. 6.
  5. 7.
  6. 8.
  7. 9.
  8. 10.

    if <power> is high turn magnetron on wait for <duration>

    turn magnetron off else if <power> is medium cycle = 7s else if <power> is low cycle = 11s else if <power> is thaw cycle = 13s end if for <duration> turn magnetron on wait for <cycle> turn magnetron off wait for <cycle> end for end if heat food at <power> for <duration>
  9. 11.
  10. 13.
  11. 14.
  12. 15.
  13. 19.
  14. 20.
  15. 21.
  16. 22.
  17. 23.
  18. 24.
  19. 25.
  20. 29.
  21. 30.
  22. 31.
  23. 32.
  24. 36.

    G A 16 16 16 16 16 16 16 16

    Prevent errors Aggregate
  25. 37.
  26. 38.
  27. 42.
  28. 43.
  29. 48.
  30. 49.
  31. 50.
  32. 54.
  33. 55.
  34. 56.
  35. 60.
  36. 61.
  37. 65.
  38. 66.
  39. 67.