From a2471123d3cea368cb16c8ff19a40b080d2501af Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Fri, 13 Nov 2026 20:49:50 +0100 Subject: [PATCH 1/4] feat(notes): add progressive animations --- src/content/notes/progressive-animations.mdx | 21 ++++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 src/content/notes/progressive-animations.mdx diff --git a/src/content/notes/progressive-animations.mdx b/src/content/notes/progressive-animations.mdx new file mode 100644 index 0000000..a94f0c2 --- /dev/null +++ b/src/content/notes/progressive-animations.mdx @@ -0,0 +1,21 @@ +--- +title: Progressive animations +pubDate: 2026-11-13T20:00:00Z +description: Animations teach, then they cost time +slug: progressive-animations +published: true +--- + +Animations help new users. Motion shows what changed and makes a new interface easier to learn. But once the user knows the interface, the same animation just takes time on every action. + +What if interfaces removed most of their animations after the user has learned them? + +This idea has a name: [progressive reduction](https://layervault.tumblr.com/post/42361566927/progressive-reduction). You start with a rich, guided interface and simplify it as the user gains experience. Games do this with tutorials: the first level explains everything, and later you just play. + +[Emil Kowalski](https://animations.dev/) made a related point recently: before choosing an easing or a duration, ask how often someone will see the animation. A command menu opened a hundred times a day shouldn't animate at all, while onboarding can afford some delight. His axis is frequency, mine is experience - a frequent animation should never play, and a familiar one should stop taking your time. + +But animations don't only teach. They also show that something changed and where it went. Remove them all and a fast UI can feel broken: states jump around, and you're not sure the app responded at all. + +So maybe the end state isn't zero animations, but faster ones. A 150ms fade instead of a 500ms slide. Enough to follow what happened, short enough to never wait. + +I haven't built this yet, but I keep thinking about a switch: not "reduce motion" for accessibility, but "I've learned this app, give me the fast version." From 651bbfef169ef4c02f9158510e866642112a2b98 Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Fri, 13 Nov 2026 20:52:58 +0100 Subject: [PATCH 2/4] chore(notes): add italics to progressive animations --- src/content/notes/progressive-animations.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/notes/progressive-animations.mdx b/src/content/notes/progressive-animations.mdx index a94f0c2..ca7ca5c 100644 --- a/src/content/notes/progressive-animations.mdx +++ b/src/content/notes/progressive-animations.mdx @@ -10,12 +10,12 @@ Animations help new users. Motion shows what changed and makes a new interface e What if interfaces removed most of their animations after the user has learned them? -This idea has a name: [progressive reduction](https://layervault.tumblr.com/post/42361566927/progressive-reduction). You start with a rich, guided interface and simplify it as the user gains experience. Games do this with tutorials: the first level explains everything, and later you just play. +This idea has a name: [_progressive reduction_](https://layervault.tumblr.com/post/42361566927/progressive-reduction). You start with a rich, guided interface and simplify it as the user gains experience. Games do this with tutorials: the first level explains everything, and later you just play. -[Emil Kowalski](https://animations.dev/) made a related point recently: before choosing an easing or a duration, ask how often someone will see the animation. A command menu opened a hundred times a day shouldn't animate at all, while onboarding can afford some delight. His axis is frequency, mine is experience - a frequent animation should never play, and a familiar one should stop taking your time. +[Emil Kowalski](https://animations.dev/) made a related point recently: before choosing an easing or a duration, ask _how often_ someone will see the animation. A command menu opened a hundred times a day shouldn't animate at all, while onboarding can afford some delight. His axis is _frequency_, mine is _experience_ — a frequent animation should never play, and a familiar one should stop taking your time. -But animations don't only teach. They also show that something changed and where it went. Remove them all and a fast UI can feel broken: states jump around, and you're not sure the app responded at all. +But animations don't only teach. They also show _that_ something changed and _where_ it went. Remove them all and a fast UI can feel broken: states jump around, and you're not sure the app responded at all. So maybe the end state isn't zero animations, but faster ones. A 150ms fade instead of a 500ms slide. Enough to follow what happened, short enough to never wait. -I haven't built this yet, but I keep thinking about a switch: not "reduce motion" for accessibility, but "I've learned this app, give me the fast version." +I haven't built this yet, but I keep thinking about a switch: not _Reduce motion_ for accessibility, but _I've learned this app, give me the fast version_. From 5cd70986b33002f0ed5259c1a14667c6e34b2962 Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Fri, 13 Nov 2026 20:54:06 +0100 Subject: [PATCH 3/4] Revert "chore(notes): add italics to progressive animations" This reverts commit 651bbfef169ef4c02f9158510e866642112a2b98. --- src/content/notes/progressive-animations.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/notes/progressive-animations.mdx b/src/content/notes/progressive-animations.mdx index ca7ca5c..a94f0c2 100644 --- a/src/content/notes/progressive-animations.mdx +++ b/src/content/notes/progressive-animations.mdx @@ -10,12 +10,12 @@ Animations help new users. Motion shows what changed and makes a new interface e What if interfaces removed most of their animations after the user has learned them? -This idea has a name: [_progressive reduction_](https://layervault.tumblr.com/post/42361566927/progressive-reduction). You start with a rich, guided interface and simplify it as the user gains experience. Games do this with tutorials: the first level explains everything, and later you just play. +This idea has a name: [progressive reduction](https://layervault.tumblr.com/post/42361566927/progressive-reduction). You start with a rich, guided interface and simplify it as the user gains experience. Games do this with tutorials: the first level explains everything, and later you just play. -[Emil Kowalski](https://animations.dev/) made a related point recently: before choosing an easing or a duration, ask _how often_ someone will see the animation. A command menu opened a hundred times a day shouldn't animate at all, while onboarding can afford some delight. His axis is _frequency_, mine is _experience_ — a frequent animation should never play, and a familiar one should stop taking your time. +[Emil Kowalski](https://animations.dev/) made a related point recently: before choosing an easing or a duration, ask how often someone will see the animation. A command menu opened a hundred times a day shouldn't animate at all, while onboarding can afford some delight. His axis is frequency, mine is experience - a frequent animation should never play, and a familiar one should stop taking your time. -But animations don't only teach. They also show _that_ something changed and _where_ it went. Remove them all and a fast UI can feel broken: states jump around, and you're not sure the app responded at all. +But animations don't only teach. They also show that something changed and where it went. Remove them all and a fast UI can feel broken: states jump around, and you're not sure the app responded at all. So maybe the end state isn't zero animations, but faster ones. A 150ms fade instead of a 500ms slide. Enough to follow what happened, short enough to never wait. -I haven't built this yet, but I keep thinking about a switch: not _Reduce motion_ for accessibility, but _I've learned this app, give me the fast version_. +I haven't built this yet, but I keep thinking about a switch: not "reduce motion" for accessibility, but "I've learned this app, give me the fast version." From 60eaef733a6c76e9d0c53b06184ae32ca3694c64 Mon Sep 17 00:00:00 2001 From: Vlad Esafev Date: Fri, 13 Nov 2026 20:56:16 +0100 Subject: [PATCH 4/4] chore(notes): emphasize frequency and experience --- src/content/notes/progressive-animations.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/notes/progressive-animations.mdx b/src/content/notes/progressive-animations.mdx index a94f0c2..978b815 100644 --- a/src/content/notes/progressive-animations.mdx +++ b/src/content/notes/progressive-animations.mdx @@ -12,7 +12,7 @@ What if interfaces removed most of their animations after the user has learned t This idea has a name: [progressive reduction](https://layervault.tumblr.com/post/42361566927/progressive-reduction). You start with a rich, guided interface and simplify it as the user gains experience. Games do this with tutorials: the first level explains everything, and later you just play. -[Emil Kowalski](https://animations.dev/) made a related point recently: before choosing an easing or a duration, ask how often someone will see the animation. A command menu opened a hundred times a day shouldn't animate at all, while onboarding can afford some delight. His axis is frequency, mine is experience - a frequent animation should never play, and a familiar one should stop taking your time. +[Emil Kowalski](https://animations.dev/) made a related point recently: before choosing an easing or a duration, ask how often someone will see the animation. A command menu opened a hundred times a day shouldn't animate at all, while onboarding can afford some delight. His axis is _frequency_, mine is _experience_ - a frequent animation should never play, and a familiar one should stop taking your time. But animations don't only teach. They also show that something changed and where it went. Remove them all and a fast UI can feel broken: states jump around, and you're not sure the app responded at all.