Choose which artboards to share (share link to prototype/design spec subset / exclude some artboards when sharing)
Because we are often working with multiple dev teams on a single project it would be great to be able to select a specific path of actions and share them as a link. Example: share just the contact flow or the shopping cart flow.
The benefit of being able to see all screens and link to them is great. Being able to see and share a subset as well would be awesome. We could focus on just sharing that specific interaction and the team it is being sent to wouldn't have to go through everything just to see the UX of a single section.
We are currently evaluating ways of enabling you to define multiple flows and then publish those links individually from a given document. Thanks!
Still cant select specific artboards to share? come onnn
Amanda J commented
This was first brought up 4 years ago and is still not a feature? This seems like a no-brainer, especially for artboards used for style guides. Please add!
Evan Zappel commented
This needs to be a thing. I keep artboards in my project that are for reference only. Having to version save and then delete them when I need to share is huge pain. This feature seems fairly obvious...
Seems like this feature has been a work-in-progress for a while. Is there any expected delivery date on this? This is very much needed in my designs. I have over 100 artboards to maintain in my current project along with multiple states on a variety of pages. Right now, I must resort to saving out new instances of my document, deleting all unnecessary artboards, and creating new links to share. If there are any changes needed to be made, this process has to be repeated over and over again, becoming very inconvenient not only for me but for the devs and BA's to make sure they have the most up to date link. This feature needs to be added asap.
Yes, Need this feature. One of my case apart from sharing with different teams - i'd also like to archive alternate designs for design team reference but would not want to publish that with dev team.
Yes! I am looking for this feature as well!
You definitely need to be able to share only specific artboard to a link. Zeplin allows you to do this.
Also, I want to be able to name my links. If it's already possible I don't see how I am supposed to do it.
It would really help if xd adds this feature, we often work on different themes and don't wanna export all of it to the developers, or most of the time it works in iterations. Please consider this feature.
Justin Roberts commented
I need to be able to EXCLUDE an artboard from a flow. e.g one I use for working elements or old components that I do not want to be visible to the people I share with
Philippe Heckly commented
Adding my voice to the long list. Being able to select which art board one wishes to share would be a very good feature to have.
Joo Chung commented
Just ran into this for the first time today. Adobe XD is like a box of chocolates, but every chocolate has gone bad and is rancid. Come on, this is such a very basic feature. Are you deliberately trying to make UX work take longer? Because that's what you're doing.
Brett Taylor commented
Hi. Feels the sharing needs to be less restrictive. I should be able to select any artboard and share just those.
Right now it only shares ABs if they are linked together in a prototype. This is very frustrating.
In Abstract they have a feature called "collections" this allows us to select any ABs and share just those as a unit. I think this is the way XD needs to go.
Heidi Boor commented
I would like to share certain artboards and hide others. I often have multiple versions of one page (i.e. Home Page), and it would be nice to share my selects. It doesn't make sense to have to prototype them together to do this.
Please have an option to hide artboards when sharing a prototype for design review. Some artboards are in progress and I don't want to show it on the share mode.
Would love to be able to share a selected subset of artboards without having to string them together as a prototype. Right now I have a couple of boards that belong to an in-app flow for iOS, with an associated web version for one of the boards. They're not in the same flow, not even for the same platform, so I don't want to include them all in the same prototype just to be able to share a subset of artboards. Just let me select which artboards I want to include in the share link?
Adobe, like others commented here, Just add Pages feature to handle sets of artboards and allow sharing each page separately.
Can we please allow multiple flows in just one link as well without having to put false click journeys.
I already have what feels like 250 dev links across multiple xd files, this will be even to harder to maintain if I then need to think of how to maintain the ability for one file then has 7 flows within it.
I would also really like to hear how you want to deal with making it really obvious which DEV link within that file you are updating as it would be
- awful if you overwrote the wrong one.
- annoying if every flow update HAD to have it's own dev link as updating documentation would be draining.
»We are currently evaluating ways of enabling you to define multiple flows and then publish those links individually from a given document. Thanks!«
Please make it not to complicate! Just selecting specific artboards with my mouse pointer and then share these selected is enough!!!!! Please make it quick! Don't think of it too long! Sketch did it before, so you don't have to do it again!
huge +1 to that
Need to be able to make different sets of shared artboards for different audiences.
- validation process with client for finalized screens
- internal reviews for work-in-progress
- end-user testing screens.
- guidelines and pages for devs
That's hardly a solution. In my workflow I don't want to wire up interactions for every project. Also I need to be able to share multiple links of a prototype at the same time.
For example I want to share a few artboards for design critique with one link, while having another part of it already shared with development and another link to other stakeholders to keep them in the loop.
In this way the XD file becomes even more central to my workflow.