Besides code cleanups and undo/redo, the main motivation for the rewrite was a different strategy on how properties are represented, parsed and updated. Transforming nodes on the canvas is way more predicable even when using complex math expressions as values.

After a couple of weeks reworking a large portion of Lotions codebase I'm almost back to where I was before. The new update introduces undo/redo behavior with the ability to store the history alongside the project, this enables you to undo changes made in previous sessions.

Since Lotion is still very much in its infancy, persistence and project management in Lotion currently happens through the file system by utilizing the File System API and IndexedDB. Some of which are still very much experimental. Personally, I really like the simplicity of it.

Positioning a node relative to the viewport is trivial in Lotion, since properties of the canvas node can be referenced by other nodes.

Every element which makes up a design is a node. Currently "Frame" is the only supported node type, but "Text", "Vector", "Stack" and "Grid" types will be supported too. In fact, the canvas itself is just a node of type "Frame", which allows for some cool interactions.