Designing Interaction States

Most screens are designed in one state: full of realistic data, with every request succeeding. Users mostly see the others — empty on day one, loading on a slow network, an error on a typo. Those states are where an app feels either finished or neglected.

Contents

• The state inventory
• Empty and first-run states
• Loading
• Forms and validation
• Errors
• Success and feedback
• Destructive actions
• Microcopy rules
• Checklist

The state inventory