Why animations in Astro still feel fragmented

Over the past few months while building Astro projects, one thing kept bothering us:

Animations in Astro still feel surprisingly fragmented.

Most solutions involve:

• adapting React-focused libraries

• wiring together multiple tools

• writing repetitive motion logic

• adding more runtime JavaScript than expected

Astro’s architecture is fundamentally different:

• islands

• partial hydration

• server-first rendering

• View Transitions

But most animation workflows weren’t really designed around those ideas.

That led us down a rabbit hole exploring:

• CSS-first motion systems

• framework-native animation APIs

• progressive enhancement

• zero-runtime approaches where possible

One interesting thing we noticed:
many Astro developers prioritize simplicity and performance over extremely complex motion systems.

Curious how others here approach animations in Astro projects today:

• custom CSS?

• GSAP?

• Motion?

• handcrafted utilities?

• View Transitions only?

Would genuinely love to hear different workflows and pain points from other Astro developers.