Creative Cloud Library Support (share symbols/assets across multiple files or team)
This would make it easier to use the assets created in other Adobe applications.
Dear XD Community -
I’m excited to announce that we have shipped a new version of Creative Cloud libraries in XD that allows you to:
1. Add assets from XD to CC Libraries
2. Brings in the full functionality of CC Libraries in other CC Apps such as Photoshop and Illustrator into XD
3. Allows you to consume XD components in other Apps such as Adobe Photoshop and Adobe Illustrator
To learn more about the new Creative Cloud Libraries improvements, please check:
Please give it a try and share with us your feedback on areas that you would like us to further improve upon.
Does "Feature In The Backlog" mean that you're going to get it into a sprint soon???
I wasted an hour trying to embed the assets from my CC library into Xd. Can't believe that this function doesn't work right from the start. Until then Xd is quite useless.
Eunah Lee commented
Do you know when the CC library will be available in XD?
This would be THE ONE most obvious thing converting me from Invision, UXPin or others. Plus the micro interactions mentioned above.
Sergi Gallent commented
Cross-file styles syncing would be great too
Alex Connor commented
"We plan to support libraries, for sure."
This is great news, but unfortunately a bit vague. Is there any further information as to when this feature will be in development, or a potential introduction date?
Vincent Koopmans commented
I completely agree with @Joel
Having acces to CC Libraries would make XD project-ready in the near future.
Joel Meine commented
@joan_lafferty, Is the plan for CC libraries to also support "chunks" of XD files as well? (i.e. a Header element used across 100 art boards)? So if a designer changes one XD file that is in their CC Library - the change affects all instances, just as a traditional linked file would or any other CC library graphic would?
When I read this morning that the April 25th update supported "Linked" objects - I was initially ecstatic -- only to find it was for exporting artwork and not linking files "into" XD (which would quintuple any designers productivity on any large projects).
Linked "Single Art Board" XD files - even without any prototype-mode linked-target embedding, would be a massive tool improvement. I already am producing XD files with over 175 Art Boards in one file, to be forced to manually update 100+ Art Boards when I change a set of graphics in a header is - IMO - probably the largest productivity-killing missing-feature in the tool so far.
I know Library support itself is in the backlog, however some insight into the strategy for rollout would be nice - so we can forecast which tools we use to produce active projects the next few months.
The lack of character styles and being able to change font defaults is killing me slowly.
Thomas Hallgren commented
When importing AI file as artboards, if AI Library Elements (and/or symbols) on the AI artboards could retain library element object status in XD. Would be nice.
Component library so I can build components and my team can use them across projects
Without this feature - it's really just invision/uxpin/etc. And UXPin is still winning due to micro animations.
So .... this, without question, should be at the top of the list.
Agreed. After my first click around Xd the biggest thing missing was the integration of CC Libraries/Symbols. Really important from a workflow perspective - hopefully this comes sooner rather than later.
For large apps design is necessary to sync the symbol in different files
Ryan Means commented
This is critical, and was the very first thing I noticed when I started working. I use Libraries extensively and was shocked (even in a preview) to not see them supported. Any idea when this will be supported?
Q Manning Manning commented
You should remove the following blurb from the XD site :\
"Adobe XD integrates with Creative Cloud so you can bring your Photoshop and Illustrator assets right into the app to enhance your wireframes and prototypes."
Because right now, it doesn't :p
library support +1