Adobe XD: Feature Requests
We love to get feature requests for Adobe XD! You can view existing feature requests, vote on them and add your comments, or you can submit a new feature request.
While creating a new feature request, please include:
- Description of the feature
- Why this is valuable to you
- If possible, an image or video that helps us understand your feature request
-
Drag in multiple directions
Would love to drag an object both directions. Perhaps if we could add hot spots to the left and right of a container, then you can either drag it left or right.
Example: in g-mail, drag the message right to delete, left to archive. Would like to render this behavior.
Thought two, add these touch points or hot spots to and image so I can drag left or right from the image itself to go forwards or backwards.
666 votes -
Allow components event to change states of other components
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.549 votes -
Drag and time trigger on components states
Allow drag gestures and time trigger to transition from a component state to another. Now, only tap and hover triggers are available.
331 votes -
Scrollable action to another artboard anchor
I'm hoping this idea is just an add on from the current Scroll action.
At the moment you can create a button etc and link it to a certain area on your artboard. It then automatically scrolls to that area once clicked.
My idea is to have this same feature, but with an option to jump and scroll to a specific area on another artboard.
It will make the user journey so much better when using things like quick links etc
88 votes -
One single interaction can trigger multiple actions to take place.
I found when designing navigation for a single page site, I want the button to change color while on a specific part of the page. It would be nice if one interaction like tap, could trigger multiple interactions to take place.
-
Zrzut ekranu 2020-10-23 o 14.49.36.png 20 KB -
Scroll to 'about' by 'tap' triger but the state is still 'default' (home) and I can't add another action to change the state on 'tap' trigger.png 54 KB -
About state by hover triger.png 63 KB -
default state.png 50 KB -
Scroll to 'about' by 'tap' triger but the state is still 'default' (home) and I can't add another action to change the state on 'tap' trigger.png 67 KB -
About state by hover triger.png 66 KB -
default state.png 65 KB
30 votes -
-
Allow more than one of the same type of interaction on a component
Allow more than one of the same type of interaction on a component.
For example two taps. One triggering an overlay menu, and One moving down to anchor link on another part of the page (where the overlay is position to show)
21 votesThanks for your feedback. One of the things that you might want to consider is adding the interaction you’re looking for inside the component itself to change states through an entire component itself.
How would you want to determine between the two interactions (when to trigger an overlay vs. when to go to a different artboard) if you have both interactions defined?
-
Ability to update selected artboards rather the updating the entire prototype
most of my project are huge and heavy, not less than 200 artboard
I would like the ability to update certain or specific artboards on the link rather than uploading all the link again
that's time-consuming.
plus some times I would like to share specific changes done with my manager while other changes are still under going-which I don't want my manager to see yet
7 votes -
Stop fixed position scrolling at a certain point
The option to fix the position of a layer has been a great addition in recent updates. It would also be great to be able to release a fixed layer at any point of your choosing.
For example, having a side panel filter fixed as you scroll down the page, but once the page reaches a certain point, the side panel filter no longer becomes fixed and you scroll past it as normal, and continue down the page without it showing on the screen.
17 votes -
Allow nested components to trigger component states
Currently, a nested components cannot trigger a component state. You would have to ungroup it, so that it is no longer a component in order to be able to target a component state.
eg. I have a card component which has multiple states. Inside the default state, I have a button (which is a component). When I select to Tap that button component, I do not have the option to target the other states of that component. It only displays artboards as potential targets.
5 votes -
Hover triggers to ALL elements to trigger artboard navigations; not just state changes
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,…
68 votes -
Overlay positioning below "fold"
I would like to be able to position an overlay so that it is connected to a specific element regardless of whether that element is below the "fold".
There are many instances of long, scrolling pages where a dropdown or tooltip needs to appear below the fold.
4 votesThanks for your feedback! If you need something pinned to a specific position, have you tried using a component instead?
-
Hover connecting artboards
If would be great if the hover doesn't only present in states, rather in the artboards too
10 votes -
Overlay via hover not possible?
I noticed I cannot put a Hover-Interaction on a component to trigger an overlay. When I use Hover, it only allows switching between states. And when I set a new Element and try to let it trigger an Overlay, the Option "Hover" is not even given in the Interaction-Menü.
Is this a bug or a non-improvement?
16 votesUnfortunately, this is not supported at the moment. Can you explain to me what you’re trying to accomplish?
-
side phone
Prototyping rotating the phone on its side as a trigger
2 votes -
Long press trigger
It would be great to have a long press/touch gesture. Since both Android and iOS have it available, it's an interaction that is getting more use recently.
If it comes with a new State for the component it would be even better!
8 votes -
Stack actions within a single interaction (multiple, cascading, ordered)
Let's say you're designing a switch, and you want to hint to the user that it can toggle with a tap, so you want it to bounce gently when hovered over. It would be great to be able to auto-animate to a different state, then immediately auto-animate back to the previous state upon completion of the first action.
The ability to stack actions would allow for complex interactions with the least amount of user interaction.
8 votes -
Custom/non square hit area
Right now, bounding boxes are always rectangular, with the height of the tallest object it contains and the width of the widest one.
However, many times it is necessary for the box to maintain the exact same shape as the objects it contains, in order to only activate effects such as hover when the mouse is directly on top.
Consider the attached files. Here we have 3 tabs. I would like to make them "jump" up slightly on hover so users can tell it is clickable. The tabs do not overlap, but because the bounding box is rectangular, the active…
5 votes -
Component states to inherit interactions from master default state
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.
51 votes -
Change state based on keys and gamepad
I request that component states could be controlled by keys and gamepad, not only tap. Today you can control the component states by using tap, but not with keys and gamepad. This is not good if you are prototyping for console games.
3 votes -
While navigate to a new artboard allow user to choose component state
while building a prototype when connecting two artboards allow the option to choose the state for the components on the destination artboard
2 votes
- Don't see your idea?