[zackbrown]

The first half of this is spot on (the flaws of declarative CSS for interactions) — your last paragraph has some mistakes about Haiku, though.

> From the video it looks like Haiku is using a library from AirBnB called Lottie to handle the animations. Then they turn around and wrap that in a React component + others forthcoming.

For the Web, Haiku Core is our renderer. We don't use lottie-web; we use Lottie only to export Haiku Core for rendering on iOS and Android.

Haiku Core uses "the fastest parts" of SVG + CSS + JavaScript to render its animations. Nothing magical here, it's just using web standards, though it was important for us to build around SVG+DOM instead of canvas so that you can still use the Web for what it's best at: rendering documents.

Haiku Core is a component format explicitly defined for reusability — and hackability. Haiku components for the Web aren't 'generated' or 'exported'; the design source file is the code source file. And due to the way that Haiku handles state (strictly internally) and data flow (strictly message-passing,) they work in any codebase, as polite and predictable guests.

EDIT: P.S. tuchsen, I'd love to chat with you some more. Can you email me [e-mail] ?

[tuchsen]

Hey sorry for misrepresenting your architecture, I did start with the caveat that I'm not with you guys though :). I shot you a couple of emails.