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.
Jay
shared this idea
We are currently evaluating ways of enabling you to define multiple flows and then publish those links individually from a given document. Thanks!
108 comments
-
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.
-
Anonymous
commented
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.
-
max2xper
commented
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?
-
Yoav
commented
Adobe, like others commented here, Just add Pages feature to handle sets of artboards and allow sharing each page separately.
-
Rae
commented
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. -
Matza
commented
»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!
-
okp
commented
huge +1 to that
Need to be able to make different sets of shared artboards for different audiences.
e.g.
- validation process with client for finalized screens
- internal reviews for work-in-progress
- end-user testing screens.
- guidelines and pages for devs
-... -
Michiel
commented
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.
-
Juan Carlos Lopez
commented
It has been taken care of!!
You need to select the starting point of your pages (they have to be linked to the rest)
XD will ignore the other artboards.https://helpx.adobe.com/xd/help/share-designs-prototypes.html
-
Lynn
commented
As a designer I have many ALT options on other boards, as well as the style guide etc. for reference. It's a major pain having to save out a new document with the artboards I want visible. Please add a feature to only select certain boards for the sharable link.
-
Shan
commented
This is a huge thing that is missing. We have large Sketch files that we've imported to XD with many, many artboards including versions-in-progress and I do NOT want all of them published to the share link. Right now my workaround is to export the drafts for review and send them as a JPG which sucks because that's the whole reason we were trying to use XD in the first place. A few of these cloud/sharing features aren't practical with the constraints as set up so even though in theory XD is a better choice, it's becoming more work to try to make it functional for our use cases. And now, it's sharing ALL the screens which is even more infuriating since I haven't created any flows at all! Obviously there are some cases where I'd want to share all the screens but I'd like the option.
Would like to see:
- ability to separate "flows" and share each flow individually without having to create a new XD document.
- ability to tell XD which screens I want included in the prototype and to maybe toggle "share all" as well -
Logan
commented
Yeah this problem is compounded by the fact that there is no way to organize a file into pages like sketch does. I would essentially have to set up like 5 different files in order to separate different interactions into different links.
I've noticed the usability problems in XD really compound pretty frequently. Too many to count honestly. After working with this or a couple months, I'm pretty upset that our organization has chosen to switch to XD. As it has slowed my workflow a LOT. The program is constantly fighting me, and I spend a lot of time having to come up with workarounds or redo work that shouldn't need to be redone.
Need to edit a component? Forget about it, probably easier just to build a new one from scratch. Need to copy a component with overrides into another file because XD doesn't let you organize your file into pages? Forget about that too, your instance will revert to master state and you'll just have to make those adjustments all over again. States hardly carry over from file to file either (~30% success rate) assuming this is just due to bugs, but could be a feature, Who knows...
I could go on and on...
-
Rae
commented
This has become frustrating as we have master styleguide file (with all of our master components) and now we had to link all the pages which is a waste of time.
We have got the point where we have had to pick something small to link the pages as otherwise if you just click anywhere on the page it switches to the next which is not helpful.
Furthermore we sometimes need to show a 'version' of a page (such as nothing to show) as now we have to create a 'false' interaction as otherwise the page won't be included in the DEV link so I have to add notes over what interaction should not be added in the real site it is just to include the page.
From a user perspective I am not sure why you have starting controlling how want I share my files?
-
Mike
commented
This is basic functionality that is absolutely imperative to our workflow when sharing work with clients, but also when sharing screens with developers.
The XD > JIRA plugin isn't useful unless we're able to share specific screens and flows, and we can't expect our development team to comb through 50+ artboards to find the screen that is relevant to their task.
Additionally, we can no longer have draft or in-progress artboards in our documents because they will be included in any share links that are generated.
This type of functionality is something that all competing tools offer and it doesn't make sense to keep using XD if this isn't addressed soon.
-
Andrea
commented
For us as an agency (a major one), the use of Adobe XD is seriously at stake if the workflow is made complicated by not having the possibility to share selected artboards! If we need to create different files only to be able to share selected deigns with the client, the principle of the single source of truth (which is one of the main advantages) is not valid anymore.
-
Anonymous
commented
Please ! I don’t want to be forced to link the artboards to share them !
In some step of the work it's non-sense !
I don't understand why Adobe changed this from the oldest versions of Xd !!! -
Matza
commented
In the Januar release there is an option to share/publish ONE artboard if there is just ONE artboard in the document. Hope this is the beginning of the possibility to select specific artboards. This is very important for the design state where I designing different design variations. I need to keep all variations to come back if the stakeholders don't like the first design step. For that I need to select specific artboards with design variation 1 to share it with the stakeholders. Selecting the artboards with mouse pointer on the canvas is much faster than wire/link them in the prototype mode (the prototype function will be implemented afterwards, after the stakeholder select the design!)
-
Axe
commented
I like to be able to select, which artboards will be included in the prototype without having to wire them. That way developers can navigate easy between the screens without me having to build an extra navigation for linking them.