Would be great to have a way to save all screen and button links from the prototype mode into multiple sets. So would be much easier to avoid a messy prototype mode with too many links. Especially when more people are working in the same file.

Imagine one UX designer is working with the marketing department to present a simple clickable demo for a short video. In other side, working with the same file, a product owner wants to present a very detailed user journey with several alert and error messages to the development team. Would be great to save the linkages in different sets, with the ability to load them as wished, and then click to play the clickable prototype.

Best regards,
Alex

Beyond Symbols, there is a need to have reusable Components. Where Symbols are a reusable group of elements, a Component is a reusable group of mini artboards that could be placed into a larger layout.

Having Components:

1) Opens up the possibility of showing on-page interactions without having to duplicate entire artboards of content.

The dream is to have each element only once in an entire project because making a single edit when you have duplicate content is a nightmare. A use case example would be needing to show all the states of a small newsfeed widget with tabs for news sources. Right now I have to duplicate the entire artboard multiple times to show what will happen in that one little spot. It'd be better to design the Component separately. Assign all interactions at the Component level and then place that single Component into my layout. An additional sample use case would be needing to show the hover effect of a card. Having Components would allow me to design the natural state as a mini artboard and then the hover state as a mini artboard and then bring the two together as a single Component that can be placed into a layout. The hope of course would be that the animation effects between the mini artboards would now be able to work at the Component level. And that Hover would be added into the list of possibilities.

2) Opens the possibility of creating reusable templated objects.
For example, we need to create a card that has an image, headline, preview text, a color block for tags that need to change width and color based on the card, and a button that needs to have variable width based on the copy. And I plan on using this same card dozens of times over dozens of pages, with different content each time. Now, a change comes through and I need to reorder the elements within the card. If I were to use a symbol to create this reusable object I don't have the flexibility to change shape widths, colors, or artwork individually to accommodate the content. So, right now I have to create a card and copy and paste it over and over again. When the change request comes, I have to go back through my entire project and manually make the changes. If though. the card first been created as a Component then the change could happen at the Component level, effecting all instances, while the individual elements within the component had the ability to override the master for each individual card.

3) Opens the possibility of having flexible "Symbols."
Right now Symbols are a fixed size. So creating something like a primary nav using Symbols requires creating a different Symbol for every breakpoint. Adding an item to that nav means making that change multiple times for each breakpoint. Symbols were really designed for things like icons and logos. Objects that are part of a fixed library and that need to stay consistent. Components on the other hand would be able to take advantage of the new "Responsive Resize" functionality of XD where we build the Component, establish it's resize parameters and then take advantage of it again and again at every breakpoint.

When I create a project, I usually get a lot of arboards, and get loads of small varioations / overlays - so when I want for example print all, or export all to a PDF I will get LOADS of pages which I manually have to remove.. In some projects I also have the Mobile Layout too.

So I would like to be able to Mark / Label / Flag / Group for some key artboards (like: Mobile 1, 2, 3, 4... or Desktop 1, 2, 3, 4... or maybe just mark as Key Artboard)
So that when I then Press print or Export I can now choose to only use the Key Artboards.

This really makes it quicker to share the project with the teams that doesnt have access to the XD file.

Thanks

Would love to be able to navigate a voice prototype WITHOUT having to long press the screen. Having to interact with the screen in order to use voice defeats the purpose of voice prototyping.

I understand there may be privacy concerns, but perhaps there's an option where you can have voice "turned on" at the prototype level. Meaning as soon as you navigate to the prototype and open it, Adobe confirms that this prototype uses voice and that you as a user consent to the mic being turned on as long as particular prototype is open on the phone. If you switch apps, exit the prototype, etc. the mic gets turned off.

It would be great for any button that takes you to a new page or just any button in general to have the option to change its state after it's clicked on. Similar to website links that are blue, after you click on them, they turn purple, showing you that you have already visited that link. For XD it would mean we could show the end user which links they have already clicked on.

Another example would be if we created a game with XD similar to Jeopardy. Where once one of the categories and prices were selected, that it would change its color state so you knew which ones were already selected.

I attached a rough mock-up of what it could look like. It may even be better to change the design, not just color. So in the example, you see a circle with a plus, after it's clicked on, it would be cool to have it change to a checkmark and green instead of purple.