New states feature is excellent but restricted for self components interaction. In many cases, especially in web and desktop apps, there are cases where a component event should affect another element on screen.
It would be a super powerful option to allow a component event to change states of another component.
Currently if i use component A inside component B, i can't use A to change state of B, even though A is part of B.

Timeline to refine auto animate animations, as invision studio do.

You've entered a new feature that is great but now we want more :D

Could you please provide the drag direction?
Thanks

Allow drag gestures and time trigger to transition from a component state to another. Now, only tap and hover triggers are available.

We need to add multiple ways of moving from one screen to another. Currently the only way to do this is to add the interactions to various elements on the artboard, which makes it difficult to find where those interactions are.

For example, to move from artboard A to artboard B, a user could press Home, Down or say "Artboard A". I can only add one of these interactions to the artboard as a whole at the moment.

i hope we can trigger the timed auto animations when you scroll to a portion of your website mock. I want my elements to appear only when i pass thru them in my page prototype. This feature will create a more seamless, animation rich prototypes!

Allow for multiple interactions on a single elements. Aka, be able to drag multiple wires from a single object.

Use case 1: When designing a carousel, a user should be able to swipe on an object left or right and navigate to the next or previous slide.

Use case 2: When designing an app with similar interactions to Bumble or Tinder, the test subject should be allowed multiple interactions on the same object. Swipe up, down, left, or right.

Add timer trigger to interaction easy simulation of non permanent states like: saving, erasing, exporting...

Thank's

Component states should behave like component copy instances. This includes interactions to be copied to all child states. This is essential, for example, for a menu component in which each state is the active status of each menu item. But when I create new state it loses all interactions. Maintaining 5 states with 5 menu items becomes tedious.

We like the new features for components, but it is still limited to taps and hovers. we would like to have keypresses for state changes inside components

Add an option to toggle between states instead of choosing a specific state to go to.
In some cases like a gallery, carousel, counters etc, the interaction is linear and a a single next/previous interaction can apply to all states.
It will save a lot of time and errors to define a single interaction and apply to all states.

Hi
I needed to .exe export when I create a project demo on prototyping mode to sending this export to the manager or somebody that he doesn't have XD on his Computer.
please add .exe export in this section.
thank's a lot.

When recording a prototype interaction, the circle cursor shows off all of the jerky movements of my mouse. An option to automatically smooth my cursor movements would make for a cleaner and higher fidelity animation.

The latest update (OCT,15,2018) got me so excited I thought of giving it a spin after a long time. Great work team!

The feature I wanted to request was the ability to see colors transition from one to the other' smoothly in auto animate'. Right now it just jumps to the next (check attachment).

For now this effect can be achieved in after effects by keyframing the 'Fill' preset.

Defining a path the elements follow while in auto animate is a feature that will be appreciated. While creating a graph some elements have to follow the curve of the graph like a point on the graph. While animating that using auto animate, the point moves outside the graph. Yes, multiple dashboards can be used to define it but with path animation, only two artboards will be enough.

Woud be great to see typing function in the prototyping mode. It could be made by combining text boxes and components (By using states). This feature needs some advanced insights to be clearly sorted, but in live, we will use this functionality in our user test.