Replace your JavaScript Animation Library with View Transitions

Use the View Transitions API to create smooth animations between DOM states with minimal CSS and JavaScript, replacing heavy animation libraries.
Read the blog post associated with this video: www.builder.io...
----------------------
About Visual Copilot 2.0:
Convert Figma designs to high quality code in a single click. Chat to make quick iterations to code or refactor elements for maximum reusability. Import and use your existing components when you have them. Sync your Figma components with your code components to generate code that leverages your components when you have them.
www.figma.com/...
About Builder.io:
Empower your entire digital team to quickly code, create, iterate, and optimize differentiated digital experiences using an API-first platform that has AI in all the right spots. Sign up for free at www.builder.io...
For more resources, visit Builder Blog
www.builder.io...
Follow us on:
Twitter: / builderio
LinkedIn: / builder-io
Get help with questions at our Community Forum - forum.builder.io/
Developer Documentation - www.builder.io...
Headless CMS - www.builder.io...
Design to Code with Builder Develop - www.builder.io...

[@shashankreddy2431]

Thanks

[@talatkuyuk6556]

good. thanks.

[@realOo7-v6r]

I miss, Manu, Adam, Steve and misko

[@AlexeyGubin-x2i]

Nice point, but please don't blame framer-motion. It is already not the same as you described in a video

[@stefanjudis]

OP here.
> It is already not the same as you described in a video
May I ask what's not the same? As explanation, I checked multiple component libs and discovered the heavy `framer-motion` dep multiple times. Then I checked its bundle size, shared this number and rebuilt a similar effect with almost no code. What's wrong about this?
I also didn't intend to blame anyone or anything. `framer-motion` and friends were great for what they enabled back in the day. But I stand by the fact that the web moves one and it becomes more powerful by the day.
"Using the right tool for the job" becomes more important than ever and using a heavy JS lib for things that soon will be working natively in all browsers, will be a "wrong tool for the job" case. 🤷

[@yusril-ihsanul-alim]

wow, ok.