Beautify the Web with smooth layout animations
Framework-agnostic Layout Projection and GPU-accelerated layout animation with various framework adapters.
Caution
This project is currently under a massive re-design, and the tutorials and website is not yet updated.
Please stay tuned and come back later!
- Getting started with Vanilla JS (WIP)
- Getting started with Angular
- Framework-agnostic Kernel API:
Layout animations have always been a challenge for web developers, especially when it comes to implementing advanced layout animations like shared-element transitions.
To address this issue, Matt Perry invented Layout Projection, which is a Web animation technique making it possible to implement GPU-accelerated layout animations in the Web platform by calculating and applying appropriate CSS transform styles on elements in each animation frame.
Checkout Inside Framer Motion's Layout Animations - Matt Perry for more details.
Matt Perry heavily applied the Layout Projection technique in Framer Motion, a well-known React animation library. Unfortunately, this left out web developers who don't use React.
Therefore, in this project, we aim to offer a framework-agnostic implementation of Layout Projection with a variety of framework adapters, to enable all web developers to enhance their applications with layout animations!
| Path | Purpose |
|---|---|
packages/core |
framework-agnostic implementation of Layout Projection |
packages/animation |
framework-agnostic implementation of layout animators |
packages/angular |
adapter for the Angular framework |
site |
app of the documentation website, powered by Angular |
playground |
app serving as the testing playground, powered by Angular |
npm i
nx serve playground| Command | Purpose | Example |
|---|---|---|
nx build <package-name> |
Building the target package and its dependent packages | nx build animation |
nx test <package-name> |
Run the Jest tests for the target package | nx test core |
nx serve <app-name> |
Starting the dev server for the target application | nx serve site |
npm run release <specifier> [preid] |
Bump the version and publish to NPM (prerelease if preid is present) |
npm run release minor beta |
FLIP (First Last Invert Play) is also a technique for performing layout animations using CSS transforms, where the elements are also transformed to pretend that they were in their previous layout and then animated back to their new layouts.
However, FLIP is a very simple technique with a lot of drawbacks. FLIP did not take the parent transforms into consideration, which causes severe layout distortion when a FLIP animation changes the aspect ratio of an element, or when one FLIP animation is performed inside another.
This makes FLIP only applicable for very simple cases where only the position of element needs to be animated and no nesting animation is required, such as animating the layout changes of items in a list.
Layout Projection, on the other hand, is much more advanced and perfectly addressed the distortion by constructing a tree structure based on the DOM, so that parent transforms can be tracked and canceled by applying an accurately calculated transform to the child element, enabling much more advanced layout animations.
Nice catch! Why don't we use the shiny brand new View Transition API? It is true that View Transition API allows you to implement any layout animation that Layout Projection can implement, and View Transition API sometimes does even a better job for shared-element layout animation across multiple layers of DOM structures. View Transition API requires even less setup - it does not require maintaining a Projection Tree.
There is really no clear answer on which one is better, since View Transition API and Layout Projection focus on different types of layout animations.
View Transition API animates the entire viewport by creating an overlay on top of it, which is interruptive and expensive, making it more appropriate for large-scale layout animations such the transition between pages.
Layout Projection animates specifically the changed elements, and most of our framework adapters allows automatic layout animations whenever the layout changes. Therefore, Layout Projection would be much more convenient for relative small but exquisite interaction animations.
Using View Transition API does not mean you don't need Layout Projection. They can co-exist and work well together!
Big thank to @taowen for providing the GitHub Gist copy of the missing original blog by Matt Perry about the tech details of Layout Projection.