The Prototype Panel moves the interaction from the element to a panel. This results in little breaks in the prototyping design flow. The previous version was much easier to use because the element initiating the action and the action settings weren't separated. Keeping the interaction settings above the wire helped to keep the connection in the designers mind. Personally I find it much more difficult to think through changes when I have to look from the element being clicked to the panel where the actions are located. Further more, the 'Scrolling' setting which controls sticky elements feels disconnected and isolated in the prototyping panel. While it is a prototyping function separating element settings doesn't make sense when designing. Having a single location for element settings helps keep the designer in flow state. Pausing to think of which panel a setting is in is task switching and gets to be annoying after a few minutes.

My vote is that the Interaction settings be removed from the left panel while in prototyping mode and the interaction settings revert to being above the wire settings to promote the connection between the element and its wire. Furthermore I would ask that the Fixed position when scrolling setting be put back into the Design side under appearance.

In the attached file you can see how keeping the interaction settings on the wire you help build the connection between a trigger and it's method of carrying out the action.

If multiple wires/interactions are selected the interaction panel could be useful, and should be left alone - but if a single interaction is selected, putting the interaction in a panel just slows down the prototyping process.

Thanks for listening! You guys have done some amazing work.

Currently when I change my artboard fill to black, and decrease transparency by a percentage, to simulate the 'lightbox' effect for my design, then go into Prototype mode and select 'Overlay' as my action - the fill on my artboard gets deselected. At first i thought this was a bug, but after reviewing the bugs list, it appears this is by design.

I would like to suggest a couple improvements:

1. Instead of 'auto-deselecting' the fill, set it to 0% transparency instead -> This will make interacting faster for those who want to go back in and change the fill color, while achieving the same results.

2. Run a check to find out if the user has changed the default fill color. If they have, then do not 'auto-deselect' or otherwise change anything. If the user has NOT changed the default fill color - then implement the 'auto-deselect' (or transparency change.) -> This should help prevent users who've indicated a desire for a specific state (fill) from doing extra work to re-fill or correct the change.

This may overlap with requests for horizontal scrolling and drag direction but it may solve both.

Drag currently only works between two states and in one direction. It would be nice if several artboards could be used with the same drag. For example: think of a carousel with multiple images shown horizontally. I don't want to have to click+drag each time I want to advance. It would be nice if I could click once and continue dragging until the specific image I want is centered. Letting go would snap to that artboard. During the drag it would transition through all of the artboards in-between. It would also need to be reversible.

I love auto-animate and drag by the way.

Say we have Artboards A, B, and C respectively whereby;
- Artboard A has a TAP TRIGGER which auto-animates to Artboard B; and
- Artboard B has a TIMED TRIGGER which auto-animates to Artboard C

Feature Request:
- If Artboard C has a TAP TRIGGER that invokes PREVIOUS ARTBOARD action, it should go back to Artboard A and not to Artboard B.

Similarly:
We may have Artboards A, B1, B2, ...B(n), and C respectively whereby;
- Artboard A has a TAP TRIGGER which auto-animates to Artboard B; and
- Artboard B through to Artboard B(n) has a TIMED TRIGGER which auto-animates sequentially to Artboard C;
- If Artboard C has a TAP TRIGGER that invokes PREVIOUS ARTBOARD action, it should go back to Artboard A and not to Artboard B(n).

IMPORTANT:
In cases where we have Artboards A, A1, ...A(n), and B respectively whereby;
- Artboard A through to Artboard A(n) has a TIMED TRIGGER which auto-animates sequentially to Artboard B;
- If Artboard B has a TAP TRIGGER that invokes PREVIOUS ARTBOARD action, it should go back to Artboard where the first instance of TIME TRIGGER occurred.

Prototyping for people who are visual impaired is almost impossible to do. With the voice feature added it has become a bit easier to fake but if two more featured would be added Adobe XD could prototype for even more users.

• Vibrations could be added within the action area. This would make sure that extra feedback could be added to certain buttons/area's instead of textual feedback. This would also mean that two actions should be possible; a vibration and a transition if necessary.
• The VoiceOver function of iOS can't read the Adobe XD app. It doesn't distinguish buttons/area's that have an action attached to it, which makes it impossible to test with visually impaired users who use their iPhone with the VoiceOver function. No other prototyping tool can be read, would be amazing if the Adobe XD could in the future.