Update interaction wires across symbols / components (keep in sync)
Adding a wire to an object inside a symbol or changing a wire inside a symbol should create/change the same wire/link across other instances of that symbol in the same way styles/text etc changes other instances.
This would allow navigation to be edited throughout a project.
I love the convenience of symbols, and I love that we can now add links to objects within a symbol, but not being able to propagate that interaction to other symbols is a problem for me.
Tom Fletcher-Jones
shared this idea
138 comments
-
Nick Diederich
commented
So basically say you have 10 artboards, and you have a settings button on all of those artboards, and you have 1 settings destination. I think it would be really cool and efficient if you can just select all of the settings, or make them a component and make them all go to the same destination (settings page) really quickly!
Right now:
Click icon, set trigger, set type, destination, duration, and easing 10x
The idea:
Click all icons, set trigger, set type, destination, duration, and easing 1x -
Matěj Kříž
commented
In FIGMA it is so easy to set global navigation. One "navigation" component, "navigation__items" set to navigate to specific Artboard (Frame). Than you make a copies of this component to individual Artboards (Frames) and it is DONE.
In Adobe XD you can set transitions on master component, but this is LOST in component's copies.
Sooo SAD
This FEATURE is "under-review" since 2018?! OMG
How we should create global navigation? Its on every webapp, on every website. Please, Adobe, COMPLETE this FEATURE. -
Anonymous
commented
Lack of support for this makes XD a non-starter for me.
-
Seth Horsley
commented
This is a must! Figma supports this idk why xd doesn't.
-
rebekah
commented
this is a critical feature for anyone working on large projects with shared nav. :(
-
Anonymous
commented
it is an absolute must!
-
James
commented
First major issue I have come across with XD.
-
Vlada
commented
Actions in the master component do not apply to all instances.
For instance:
1. I created a 'navigation panel' symbol which contains buttons with assigned actions.
2. I made instances of it (in Prototype mode to keep all actions) for all pages.
3. I changed action for one of the buttons in master component.
4. NOTHING CHANGED in all instances. So I should go and change manually 100 screens. Come on!Another example:
1. I created symbol with website menu and copied it for 100 screens.
2. I added actions to items in menu symbol
3. All this actions are not applied for instances.PLEASEEE!!! Add built-in actions to symbols. For now I should waste hours to make changes into menu navigation.
-
Benjamin Smith
commented
How this hasn't been done yet is completely beyond me.
-
Anonymous
commented
Example scenario:
I have 2 documents:
- a library file/design system
- project file 1I have imported the assets and components from my library file into the project file. I reuse a particular button (a linked component) many times throughout the project file.
Now when I go to prototype: all instances of the button in the project file should be prototype linked to the same artboard. Because my "master" component is technically the one in the library file, I can't include the prototype link as part of the component. This means I have to set up a separate prototype link for each instance of the button, even though they all go to the same place.
So we had this idea that maybe one instance of the linked asset could be the "local" master - aka it is the master only for the specific file it is in. This would allow all instances of the button to still be linked to the asset in the source file, but also allow you to set up a prototype link on the local master that would apply automatically to each child instance of the component within that same file.
I realize there could be various problems with this - such as clashes between updates made to the linked asset in the source file vs the local master. I think keeping things in this hierarchy would work:
Changes made to the source file master > changes made to the local master > overrides to the local child components
There are probably things I haven't thought of but it's just a thought! Hopefully some of it makes sense. Thanks for reading!
-
Signwalker
commented
For Designing Websites you always have to create a Navigation Menu that has to work for every artboard. Everytime you have a Major Change you have to check if its Linked Correctly.
My Suggestion: 1 Menu Component with different Responsive states.
Standart Links like off canvas Menus and Start should be saved within the component. -
Swamitra Singh
commented
Please, Adobe Sir, Do this as fast as possible, I don't want to go to each artboard and update the path again.
-
Bruno Monteiro
commented
Can't understand how and why this simple and basic feature it's not yet something that it's implicit with XD.
-
Brandon Comstock
commented
This sort of functionality is **critical** for any sort of complicated UX project (e.g., a university redesign with multiple rounds of stakeholder feedback followed by user testing etc.). I’m taking the plunge with XD but shudder to think how it will be to implement nav changes / states across dozens of art boards.
-
Jordan Kicklighter
commented
This suggestion has existed for a long time apparently, and barely has any votes: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/19612669-update-interaction-wires-across-symbols-componen
-
Jordan Kicklighter
commented
My Sketch license has ended, so I decided to check XD before renewing. Lacking this feature is a complete deal-breaker for me, so I guess it's back to Sketch or giving Figma a shot.
-
Anonymous
commented
2 years on and this is still the reason I don't use prototype mode. I can't believe Adobe have worked on hundreds of less important issues and features since but they can't get the basics right. I just don't think they understand how people use their product or what their priorities are.
-
Anonymous
commented
Agreed! Need this!
-
James
commented
@Hariharan That is not an ideal solution. The point of rapid prototyping is to reduce the amount of "re-do" work.
Currently Figma is a superior solution to XD because you can prototype links into your master component and those links cascade down to all instances of that component. In addition, when you want to add a link or change a link, those changes will also cascade down to each instance without having to re-copy and re-paste the entire component on every artboard that you want that current state to exist.
If Adobe wants XD to be a competitor in the rapid prototyping market, they have a lot of improvement to make. XD is just not improved enough to be a superior product at this moment in time.
-
Sergei Rybakov
commented
Please introduce a navigation symbol.
The main idea is to have a special symbol that will contain:
a. all links to other artboards
b. styling variations related to a state of selected Tab or icon.Placing this symbol to any artboard will automatically connect with proper artboards. In case user need to relink to another artboard it will be done only once in the master navigation symbol. Thank you.
