Now that the "Tap/Hover Effect" request ()https://adobexd.uservoice.com/forums/353007-adobe-xd-feature-requests/suggestions/12941394-tap-hover-effect?tracking_code=c41a5301558789f85205f7c47ec8b9ca) is officially closed, we need a feature to do what (I believe) the 8952 people who voted for it have been asking for since March of 2016:

A way to assign Hover events as triggers for the existing interactions platform.

Component states is a wonderful addition to XD, but it barely scratches the surface of what designers need for prototyping hover events.

We need to be able to add tooltips, menu pop-up overlays and many other effects that still can only be achieved by transitioning to another artboard. As it stands, to prototype a menu overlay that will ultimately occur as a hover event, we must use the "Tap" trigger and tell the design reviewer "this will be activated by a mouse-over event, we just can't simuate that with our current tool."

Obviously, XD is able to trap the hover event. We just need it to be wired to the transition interactions.

FINALLY there's a hover state on components! GREAT!

However I quickly ran into a limitation. When the user touches a button or clicks it with the mouse/trackpad, the button needs an "on tap" or "on click" state that very briefly changes a button's appearance to give the visual feedback "your click or touch was detected".

So now that you have HOVER please add ON CLICK/TAP ort whatever you want to cal it.

Basically the component state changes for a definable amount of time before the destination or next state is triggered.

While you're at it, how's about looking at some of the long-time available link states we know from the web, like visited, or on-focus (when users like to use the tab button to move from button to button)

Hey guys,

it would be great if you expand the States of component not only for Hover or Tap, but also a simple Loop Animation... Here is the tutorial of what I mean -> https://www.youtube.com/watch?v=Ev3fSi7P66c
And the video below is an actual prototype I'm working at of wayfinding in the museum, where animated arrow shows you the way...
For now I can achieve this effect only between 2 different artboards... But it would be really cool if the component in some way had a "loop" auto-animate option between states... 🤓

And hey, this could be the beginning of making gifis directly in XD... 😊 which would be AWESOOOOOOOOOME! 🥳Thank you 🙏

In order to export an Adobe XD prototype to Alexa Preview, the first artboard must contain actual content; an empty space will result in export error. This is a new issue as previous exports have accepted a single space as content.

I wasted several hours trying to address this. My exhaustion to figure it out on my own led me to leave a 1-star rating on Amazon for the XD skill, a phone call to the Adobe support team, rescheduling a client meeting and lost wages.

My feature request:
Make export error handling better and more descriptive.

Explicit indication that something has gone wrong. The very worst error messages are those that don't exist. When users make mistakes and get no feedback, they're completely lost. Email, for example, offers several situations where explicit indication would be useful. Such as: When you send a message that gets eaten by the system and never reaches the recipient. Another good example? When you state in an email that you'll include an attachment, but forget to do so. Finally a job for that annoying paperclip: "You seem to want to attach a file to this message, but you have not done so. Would you like to attach one now?"
Human-readable language, instead of obscure codes or abbreviations such as "an error of type 2 has occurred."
Polite phrasing that doesn't blame users or imply that they are either stupid or doing something wrong, as in "illegal command."
Precise descriptions of exact problems, rather than vague generalities such as "syntax error."
Constructive advice on how to fix the problem. For example, instead of saying "out of stock," your error message should either tell users when the product will be available or provide a way for users to ask to be notified when the product is restocked.

I thinks its very annoying that you now force us to present the design specs and prototype in the same share cause now it's impossible to iterate these two documents separately. Most of the times my design specs and my prototypes are different iterations and must be shared separately. Often we iterate different prototypes and we send design specs for just sections of the design, the section that has been accepted for release. With the new setup it's impossible to continuous this strategy and it messes things up. Please give us back the opportunity to share ONE thing at the time! You could for instance make two options in the share section of XD where we could choose to share the specs with or without prototype or at least give us back the chance to share prototype files separately.

It's a very good thing that we can now easily share colors between projects. But to be really useful, we need to change a linked color on a specific project.

I work on multiple projects based on the same UI library. Each projects has its own main color.

I created a project to maintain all my atomic elements and my other projects use those linked elements. But for now, when you use a linked color you can't change it on one project only so I can't use your great new feature for sharing assets between projects.

Here is how it could be implemented :
1. On the contextual menu of a linked color choose "Edit for this document"
2. Choose the new color
3. All the artboards and components with the first old color are updated with the new color

Complementary rule for linked assets updates : the unicity of a color is determine by its name and not its hexa code. So if a color has the same name in further projects, it has to be considered as the same color and not to be change by the update.