Branching and merging versions
It is very necessary to make a version control system available, which allows "commits", "branches" and "merges", and more functionalities, just as version control services do for developers.
I know there is a design application for this purpose, but every time that application is updated it is no longer compatible with Adobe XD
Chinedu Chuks commented
I think adobe xd is the best tool out there, but they are a couple of things i can say i face in my everyday life using xd that can make it the experience even better and one of it is versioning.
As a designer i have always had issues versioning my work in adobe xd, from my design file down to my design systems. Whenever i work on a design and i'm trying to update to version 2 in the future, i'll have to create a new separate document which isn't the best because then i have to copy and past design into the new file and update what needs to be updated. I'll advise something in the form of Pages like figma does, not saying it has to be the same, but something that allows us to version designs properly without creating more than one document.
Now concerning design systems, whenever i build design systems and i publish that library to use across my actual design, i also cannot version my new update. I.e when i want to do a design overhaul i have to some sort create another document to publish another brand new design system that wont affect my existing design which is stressful because i manually have to change things. But if there was a way to have a version system that allows you to have more than one document library in a particular file it would be nice.
1. I want to be able to update designs and keep track of it in one document without having to create separate document for V1 and V2
2. I want to be able to update and publish more than one design system from a document as a way of versioning V1 and V2
Our organization is doing a trial to move into Figma for our UX team. From a general tool standpoint, I still prefer XD however from a collaborative and cloud file management standpoint, Figma is leaving Adobe in the dust. Not being able to transfer ownership of my Cloud files (or allowing others to build to and share the cloud file) is bad enough but I've been trying the Branching option on Figma and am in love with the freedom it gives me.
The fact that I can use that to try new things and merge the work into my main file or blow it away because it doesn't work is super beneficial even from a single user standpoint. I really think if Adobe spent a lot of time on their cloud/sharing and collaborative and added some branching, XD would be the clear leader.
This capability is probably going to be the main reason design teams across the org move from Sketch + Invision to Figma even though we have a design system in XD.
This is essential!
Amen. This, please.
Derek Rudel commented
We use XD as our primary design tool to create our design system and core product designs. We would love to leverage the full power of working solely in the CC environment, but the thing that's missing is the ability for designers to check out a project and merge it back into the master as developers do with Git.
We currently use Abstract to do this, but it lacks the integration with CC hosted libraries and files. It's a nice tool, but we would prefer to move 100% into managing projects/files through XD with the ability to create branches and merge them back to master.