Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/12-principles-of-animation/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ Why is this important? Because focusing on key poses helps you prioritize what m

If something doesn't need to be animated, don't animate it (please). Not every key moment needs motion. Sometimes the best animation is none at all.

For example, consider context menus. Apple's context menus only animate on exit, never on entry. Opening happens instantly. They do this beecause context menus are used constantly, and that entrance animation would compound into irritation.
For example, consider context menus. Apple's context menus only animate on exit, never on entry. Opening happens instantly. They do this because context menus are used constantly, and that entrance animation would compound into irritation.


## Follow Through & Overlapping Action
Expand All @@ -109,7 +109,7 @@ The above example makes use of springs to make the transitions feel more alive.

They add that organic overshoot-and-settle that easing curves can't replicate. Apple's WWDC23 talk on springs is worth your time if you want to go deeper.[^4]

Knowning this, the maing danger is latency. Too much stagger and your interface feels slow, like it's thinking too hard, so save it for none critical elements.
Knowing this, the main danger is latency. Too much stagger and your interface feels slow, like it's thinking too hard, so save it for none critical elements.

## Slow In & Slow Out

Expand Down