Henrik
My feedback
-
253 votes
An error occurred while saving the comment Henrik
supported this idea
·
-
394 votes64 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
-
Organize assets panel objects (symbols/components/colors/character styles) into folders
-
Screen Shot 2021-05-11 at 2.34.10 PM.png 117 KB -
Components vs Patterns.png 134 KB -
folder.jpg 108 KB -
file-MDfX7gA6Aq.png 85 KB -
Bildschirmfoto 2020-07-23 um 13.39.47.png 139 KB -
Bildschirmfoto 2020-07-23 um 13.39.42.png 163 KB -
Component Design System.png 18 KB -
parent-child.jpg 34 KB -
current-ui.jpg 33 KB -
Capture d’écran 2020-04-27 à 15.01.10.png 38 KB -
makeshift categories in asset panel.PNG 29 KB -
Screen_Shot_2017-02-27_at_1.07.38_PM_copy.png 169 KB -
Screen Shot 2019-08-01 at 1.28.22 PM.png 1194 KB -
feature request 2.PNG 6 KB -
feature request.PNG 13 KB -
Groups_for_Assets_Panel_-_Adobe_Xd_Feature_Request.png 1081 KB
1,131 votes208 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →This is something we are planning to do! Stay tuned for more details.
An error occurred while saving the comment Henrik
commented
How does one become a contributor to the XD feature team? Do you have a panel of professionals that is possible to join or apply for?
An error occurred while saving the comment Henrik
commented
Really longing for these features, and it would be great if you let the community know what you are working on, so that we can follow the progress and plan our own work according to that. It is very hard to make a fully working DSM on an enterprise level working blindfolded not knowing which features will be available when.
- Custom folder/category structure for components/styles that can be fetched by e.g. Diez, Haiku or similar dev-tools. It is impossible to structure your components in a meaningful way for collaboration.
- Option to search for components only, not including colors.
- Option to share specific tokens/styles and not only an entire library with teammembers.
- Do not automatically place "linked components" within the components area of the file you are copying to, if you copy assets from one file to another. The assets ought to be visually seperated and afterwards you can choose to make a local component. It gets really messy .
- Shareable artboard templates in components / Pages from a master document
- Multiple component libraries with sublibraries pr. file. e.g. "Web", "iOS" and "Android" where all three mentioned also have "dark" and "light" sublibrary e.g. in a master document. managing 3 different files is cumbersome and errorprone. Consistency, speed and collaboration is key.
- Shared components across said UI-kits. - A lot of UI components are the same across platforms.
- Possibility to be granted update rights for shared links if you are not the owner of a document.
- Optimized color management, extract colors from file, find and replace. Posibility to choose to "overwrite" a color. That automatic merge is annoying.
- "Hightlighting" of assets, components etc. is barely visible when you have a huge artboard or document. Something simple as navigation through where they are used would be helpful.I believe that many of us working in UX/UI and closely with DEV in an enterprise setup, are lacking the above on a daily basis.
This should be NATIVE features and not handled by a sea of plugins that require login or payment to 10+ 3rd party services. Please consider keeping your eco-system more lean.
I know you don't reply on requests on facebook. but you should consider engaging in conversation there instead of just sending everyone in here on Uservoice. An open dialogue would be much appreciated.
An error occurred while saving the comment Henrik
commented
I would say it is a must for designers to add custom categories to the assets panel. E.g. Buttons, Controls, Forms, Elevation etc. Just like character styles and colors. Right now you have to make a text on the artboard a component to function as a divider. The workaround does not work in asset grid view.
Henrik
supported this idea
·
-
-
1,463 votesfeature-in-the-backlog · 158 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
-
686 votes103 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
-
107 votesfeature-under-review · 17 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
-
4 votesHenrik
supported this idea
·
-
41 votes
An error occurred while saving the comment Henrik
commented
I have issue deleting assets that are no longer on the artboard. It says 0 instances. But no option to delete
-
7 votesHenrik
supported this idea
·
-
2 votesHenrik
supported this idea
·
-
2 votes0 comments · Adobe XD: Feature Requests » 04 : Sharing on the web · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
-
2 votesHenrik
shared this idea
·
-
66 votesHenrik
supported this idea
·
-
7,614 votes406 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
Reopening the feature request, based on feedback.
An error occurred while saving the comment Henrik
commented
Can you please change "Snap" easing property name to something that is widely known or a market standard. e.g Spring. There is no such equivelant in CSS or UIViewanimation in Xcode. Otherwise you will be blackboxing XD.
Also please display transition and animationspeed and other details in Design Spec mode for a much better hand-off experience.
An error occurred while saving the comment Henrik
commented
This i s by far the best request! I was designing a search bar today and i really wanted it to slide down from my header when I press the search icon in the app. This would make it so much easier for both developers and stakeholders to understand and "feel" the thoughts the designer has put into it.
Henrik
supported this idea
·
-
66 votes
An error occurred while saving the comment Henrik
commented
Yes, I am doing that work around right now, but they are not stored in "Character styles". I am requesting a feature to create sets under character styles not assets/symbols that DO NOT overwrite styles with the same values. e.g. I have a font that on mobile and desktop are equal but on two different breakpoints, but they overwrite eachother.
Since Adobe XD does not support EM or REM values, we need to do sets of different fontsizes for developer handover and a collaborative UI Kit, where fontsizes for different breakpoints are fixed.
It is fairly simple actually.
An error occurred while saving the comment Henrik
commented
It would be great to be able to create character style sets that can be used in e.g. UI kits and Design Specs for developers
Styleset for Desktop, Tablet and Mobile.
Henrik
supported this idea
·
-
1,611 votes139 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
-
1,295 votesHenrik
supported this idea
·
-
552 votesfeature-under-review · 138 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
-
Apply gradient to border/stroke
-
Screenshot 2021-05-21 163654.png 25 KB -
Figma.jpg 21 KB -
03.png 48 KB -
02.png 40 KB -
01.png 23 KB -
gradient-stroke-3.JPG 98 KB -
gradient-stroke-2.JPG 132 KB -
Gradient.jpg 67 KB -
1_4FUR-8xiff-8OuCxWl0swQ.png 295 KB -
1_4FUR-8xiff-8OuCxWl0swQ.png 295 KB -
Screenshot_2.png 13 KB -
circ;e.PNG 44 KB -
B2up3QxIYAAw4K8.png 20 KB -
Screen_Shot_2017-01-21_at_12.56.47_AM.png 31 KB -
Screen_Shot_2017-01-21_at_12.56.22_AM.png 26 KB
884 votes102 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
-
-
1,025 votesfeature-under-review · 76 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →Henrik
supported this idea
·
What is going on here? I am SOOOOO tired of making new component -> stack, padding, fill color, states upon states all over again again and again.
1 component done -> Dublicate and change what needs to be changed. voila!
Once this feature hits I will have to redo + 100 components from scratch, again :/