flowmo can run an interaction as pure CSS or via GSAP. The engine auto-picks: simple reveals/hovers/scroll compile to lightweight CSS when eligible, and anything complex (stagger, text-split, custom ranges) falls back to GSAP. You can force a mode.
Where: Interaction → Settings → engine selector — Set the CSS/GSAP mode
Key ideas
- Auto: CSS when the interaction is eligible (load/reveal/scrub/hover/focus, no stagger/plugins/custom-props), else GSAP.
- Force: Pick css (lighter, where possible) or gsap (always), per interaction.
- Why it matters: CSS is cheaper and smoother for simple cases; GSAP covers everything else.
Steps
- Open an interaction’s Settings.
- Use the engine selector (auto / css / gsap).
- Check the eligibility note if CSS isn’t available.