The team and I have been compiling a list of features we’d love to see get implemented at some point. These are primarily related to design systems and have come about as we’ve been working on improvements to our own system. Would love to know if others have found a need for other design systems related features.

Improved token/variable manager: The current token manager is pretty basic and a couple simple additions would really improve our workflows.

• The ability to search for tokens in a given collection


• More verbose token arrangement tools, we’ve accidentally moved the wrong set of tokens many times


• Token mode/column arrangement, the order of the options that are displayed when changing themes is determined by this but if you set it up wrong at first or add any new mode then you can’t rearrange them.


• Ability to natively export tokens/variables without needing a third-party plugin. Options for raw data, JSON, CSS, etc.

Theming and modes: Modes are relatively one-time use right now. But there is a growing use case for product iterations on a given theme. More specifically it would be great to be able to create a master token structure that can be utilized by other “products” or systems.

Change history: It’s pretty difficult to tell what tokens were added, deleted, or modified when pushing new versions of a library. Just listing “200” variables changes and listing whether or not they had one of three previous change types applied isn’t enough. Seeing what it changed from and to, what mode it changed for, etc. In addition revamping the version management feature to be more like Github or any other git structure where you can see a timeline of merges with notes and contributors.

Getting closer to code: Figma’s autolayout is probably the closest thing we can use to represent a coded component. But there are lots of things that could be added that would bring designs even closer to their actual implementation.

• Add the option to change box-sizing model for the library


• Allowing components to live inline with written content/text objects. Right now we have some pretty hacky solutions for this that are quite brittle

Other: An easier way to handle uncertain component compositions. Specifically when you have menu or list components with an unknown quantity of items within them. Right now we either have designers compose the inner menu with menu items or we’ll have a set of 10 items for them to show and hide. But the first option puts a lot of responsibility on the designer and the second option introduces file size/efficiency issues.