Skip to main content

Case:



  • Working on a design task in file(s) that contain 50 screens,

  • Making changes on just a few screens and also adding a few new ones,

  • When the work is ready for review there is no option to group frames that are relevant just for that particular task like it’s possible in Abstract with collections.


Having the Collections feature would make things much easier as it’s won’t be needed for duplicating frames and putting them in a separate page or similar, which makes noise in files and can lead to performance issues.


Please add this feature!

big +1


we used collections exactly the same way in feature branches.

and also to add another use case: we used collections in the master branch to document the core capabilities of the product. e.g. “header”, “dashboard”, “user profile”, “settings” etc. this was valuable for visitors as they did not have to sift through dozens of pages with dozens and dozens of frames/artboards (for edge cases, error handling, a11y specs, etc.) in order to get an idea of the current state of design decisions for the product (btw: we used the master equal to the master of our dev product). AND it also allowed fellow designers to quickly look into our designs to get inspired or find topics that they also were working on …

of course one could make components out of these key screens and put them on an extra page but that just feels very weird and also probably introduces other issues.

Reply


Terms & ConditionsCookie settings