Allow interaction wires/links from objects inside a symbol
I was so excited about the new symbols feature that I made all of my navbars in a design a symbol. This may be one of the most obvious uses of symbols, since every page will almost always have the same navbar. But you can't connect objects inside a symbol. Therefore, you can't connect nav items, icons, logos in a nav bar.
Either allow connects for objects inside symbols, but don't propagate them in all instances, or DO propagate them in all instances. But you HAVE to be able to connect objects inside symbols in prototype mode.
Otherwise, we can only get halfway to easily and efficiently editing UI elements like navbars, sidebars, and such.
Will Viles commented
A must-have feature. The #1 use case of symbols is for headers/footers. What do they contain? Loadsa links.
Brian Campbell commented
This is a must have. Without it i have to change my global nav by hand across dozens of screens. Major PITA!
Thomas Hallgren commented
Definitely would be useful. I absolutely love symbols, but if elements inside a symbol placed on an artboard was independently a link. Bliss.
Derek Heisler commented
I would like a certain symbol in a menu always link to a certain art board, regardless of how many times I copy and paste that menu onto other art boards. I'd like to reduce the amount of time it would take to to relink that symbol on all art boards to the same art board. Hopefully that makes sense.
LESLIE ARIAS commented
Symbols are made to repeated. The most repeated item in an application is the header and nav bar elements. So the most natural thing is to want to convert these elements into symbols.
However, if i my nav bar into a symbol and then go on to create 50 screens. I now have to break the symbol and link each item in the nav bar for each screen. At that point the symbol feature becomes inefficient.
This is the most important feature missing from AdobeXD. Without this it is impossible to design complex apps. You have to go back to InvisionApp.
Having the option to link a standard target to a certain symbol would result in working more effectively. At the moment I have to link the same symbol on every artboard to the same target manually. Wouldn't it be great having an option where a symbol, like an arrow of which the target navigates to the previous artboard, links this target to the symbol for every artboard?
I think a better and probably easier to implement, with less usability issues and overhead, will be to include linkage when copying and pasting in design mode or prototype mode. As currently you'd need to go and relink everything anyway, you might as well just duplicate the links at this stage and if users need a differing link they can easily change it. No overhead just a massive win. Upvote here: https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/13041930-copy-paste-should-preserve-interaction-wires-links Tom also said this wouldn;t be too difficult to implement too.
Josh Kapp commented
I think if you collect all the use cases you'll likely find that the desired result is split between the two ideas. Navbar seems to be the most common case, which would suggest propagating links. But if you're building something sequential like a wizard-style flow, obviously each page needs a unique "Next" and "Back" link. My vote would be to have a mode to select the desired behavior for the entire symbol. As a second choice, since the sequential case is less typical, defaulting to propagating but allowing per-instance override is probably sufficient.
Zach Bruce commented
I would appreciate defaulting symbols sharing the same link, but then being able to "detach" or "override" from it.
Default behaviour should be to set up links inside symbols that are universal. e.g. all instance of home icon will link back to home. Then when editing prototypes, manual overrides can be made if necessary. Similar to the way master pages work in Indesign. This would be intuitive to understand and very powerful.
In my case, I would like the Symbol case to function similar to the RepeatGrid when it comes to Prototyping. In a repeat grid I can just link one particular portion (or grouped layer) and hook it up via prototyping e.g.
- Tabbed content
- Exit/Back/Forward/Toggle screens
Essentially I use the Symbols for grids/headers/footers and I want to make my mockups completely linked together - before I discovered Symbols I used the RepeatGrid which provided me with everything I needed except that one change on an artboard had to be repeated across all artboards manually vs. Symbols...but the prototyping doesn't work so I always have to ungroup my Symbol and then start prototyping which is contradicting the purpose of the Symbols
When creating a megamenu, I need to have the same top nav links link to the same target location across artboards. Instead I end up having to individually link symbols to the same target location across multiple artboards. Depending on how many links are in menu, that could be A LOT of artboards!
Make links inside symbols global (Like in every other prototyping tool)
Maybe make this work like dynamic symbols in Illustrator:
• Editing a symbol in the symbol library applies a global change
• Editing a symbol in an instance applies only to that instance
• Give an option to go back to the 'mother' settings of the symbol for every instance
• Give possibility to inlcude micro interactions for often repeated symbols (eg buttons with hover state)
Can't wait for an improvement of any kind on this!
Cannot link objects from inside a symbol (eg a menu item from within a navigation bar that is a symbol) . Pretty sure this used to work before.
Propagate the connects in all instances. So interactions should automatically apply universally to all copies of the symbol!
Harun Alikadić commented
Like in InvisionApp templates. Links should be part of the symbol. Once they are set, they should be active everywhere the symbol is applied. It would be nice to go step further from Invision and make it possible to override the default symbol element link in some special screens, without affecting other screens where the symbol is applied.
Yes, the ability to link interaction within a symbol is at least half the point. Navbars will likely be on most pages, in some form or another. Each instance needs to not need to be babysat individually.
Not sure if this has been already suggested... but how about this to chew on?
Do both. When selecting an object within a symbol...you can either further drill down, making that item a symbol, thus giving it the same functionality across all instances and future instances... AND you have the option to leave it as just another object, thus allowing for more flexibility.
If you want to get WILD, if you can figure out a way to make it behave in certain ways on certain pages... and excluding behavior on any pages not selected... whoa. :P
Sjur Grønningsæter commented
Links inside symbols is core in navigation and menu interaction design. To be honest, this is so basic in prototyping that I’m surprised it’s not a core feature in Adobe XD from the start. Navigation design in XD is currently so time-consuming that it’s a deal-breaker.
Harun Alikadić commented
There's need to select a single elements within the symbol to be linked with a screen and not the whole symbol. I use symbol for the top menu.