Add your own custom UI Kits
The ability to add your own UI Kits to the start screen
It's great having iOs etc on there but for professionals working on lots of projects (web based) for big brands there is definitely a need to have custom UI Kits for each brand. This will speed up projects massively as well as maintaining consistency across all projects. Thats essential when you are working to strict brand guidelines.
Make it happen Adobe ;)
Jeff Mendoza commented
Can we have cloud-based / library integrated UI Kits?
Ravi Lautan commented
I think it would be great to accompany this feature with a UI kit pane. UI kits could be added and updated from here from a repository. That way you can make sure you're using the latest.
Anita Hall commented
Once I have a custom UI Kit, can I add it to the "Open UI Kit" menu?
steve petoniak commented
Super useful for my whole company. We're building out a UI kit in XD and its working great.
However, If I work on too many files without opening it again, it gets out of my recent files.
I'd want to be able to keep it in the UI kit tab.
Yes! This is what I miss from sketch! The possibility to download UI kits, and use those. On my latest project I would love to have a iPad UI kit
well, once the "libraries" are accessible...this should be no problem. It could be easier to select elements from the library...as opposed to jumping between screens.
Yes, I agree. We have pattern libraries both high fidelity and low fidelity for multiple projects.
Please Adobe make it so.
I want to replace Balsamiq as our wireframe tool and MS Visio as our flow diagram tool.
Nicholas McClay commented
This could be killer actually
I agree, when I first opened the app I said ok how can I create my own UI kit and pull it into this app. And then eventually sell it to other designers. To speed up their workflow.
Capt. Proton commented
This would be great if it could be defined/imported in as a separate (standard) .xd file in a special, uneditable window palette (i.e. Brand or Assets) next to Design and Prototype.
Kevin Neal commented