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

Design of Everyday Swift

Sponsored · Your Podcast. Everywhere. Effortlessly. Share. Educate. Inspire. Entertain. You do you. We'll handle the rest. →

Design of Everyday Swift

How can we apply the ideas from "The Design of Everyday Things" to the design of our Swift code?

From Try! Swift (Tokyo) - Mar 3, 2016

Avatar for Rachel Bobbins

Rachel Bobbins

March 03, 2016

More Decks by Rachel Bobbins

Other Decks in Programming

Transcript

  1. :( • Goal • Plan • Specify • Perform •

    Perceive • Interpret • Compare • New Goal
  2. • Goal • Plan • Specify • Perform • Perceive

    • Interpret • Compare 7 Stages of Action • Discoverability • Feedback • Conceptual model • Affordances • Signifiers • Mappings • Constraints ◦ (Entirely separate from auto-layout) 7 Principles of Design
  3. • Public, private, internal • Tests • Sensible method/variable names

    that trigger autocomplete ◦ Not “numberOfSectionsInTableView” • Comments & documentation Discoverability #1
  4. Feedback #2 Automated: • Compiler errors • Compiler warnings •

    Test failures • Runtime crashes • Runtime experience Human: • Pair-programming • Code reviews • Bug reports • App Store reviews
  5. Conceptual Model #3 • People always form their own conceptual

    models. • Conceptual models are heavily influenced by a user’s own experience/background/culture.
  6. Affordances #4 • Methods afford calling • Variables afford getting/setting

    ◦ `var` variables afford resetting • Private helper functions afford readability • Protocols afford decoupled object graphs
  7. Signifiers #5 • Public, private, internal ◦ Yes, again •

    Names • Comments • Tests • Enum/Struct/Class • Protocols • Optionals • let/var • throws • guard