Frankie Loscavio
My feedback
-
92 votes
An error occurred while saving the comment An error occurred while saving the comment The current design and implementation of XD components is absolutely infuriating and horribly inefficient. Way too many bugs right now and almost certainly any file with complexity will lead to orphaned assets, multiple references to the same asset and source document .xd file for assets that are hard if not impossible to remove or relink.
If there was ever a time, situation and urgency to listen to your users, now is that time. Please fix your component management or lose users to other platforms that allow management of components in more efficient ways that doesn't waste our time and effort. It's a nightmare right now and the effort and time required to clean up your inefficient component implementation is more work than it's worth.
XD Team,
This must be fixed ASAP!!!!!An error occurred while saving the comment This feature is long overdue and getting to be incredibly frustrating managing orphaned instances within and across documents. Adobe if you actually listen, this is a must have feature!!!!
To say this is ".. as designed.." means it's now time for a redesign...
-
287 votes
An error occurred while saving the comment +1
-
Organize assets panel objects (symbols/components/colors/character styles) into folders
-
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
819 votes177 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 This is a desperately needed feature along with the specific ability to better manage and remove unused symbols / components. With the ever increasing complexity our design demands and cross-document linkages, managing orphaned components is becoming a nightmare. The ability to manage components currently in Adobe XD is akin to changing styles on MySpace back in the day (Awful). Currently it's more like a hack rather than a feature or coherent process. Unless this is quickly addressed, our files and design system assets are almost impossible to maintain and will look elsewhere to the likes of Figma. Seems that choosing Adobe XD for our solution is making our lives worse, not better.
-
-
33 votes
An error occurred while saving the comment I believe Adobe XD has designed themselves into a corner with the way their components "work" or lack thereof. Managing components within and across documents has gotten to be a full-time chore right now and if they don't improve it will be losing users to Figma.
-
122 votes
An error occurred while saving the comment Still waiting for a better solution to this problem. Please provide better tools for managing components and unused objects etc..
An error occurred while saving the comment +1
I absolutely agree with this statement from thomasbricker:
"Yes, there should definitely be a way to "clear" all unused Assets and Symbols from a document.
Its too confusing to wade through all of the Assets and Symbols that build up."Hovering is not an efficient way of solving the issue of many unused or orphaned components and elements etc..
-
115 votes
An error occurred while saving the comment +100
-
340 votes
An error occurred while saving the comment +1
-
337 votes
-
491 votes
Hi everyone,
We’ve started working on multiple fills and borders, with plans to extend to this multiple shadows in the future.
Best,
Dan -
349 votes
-
427 votes34 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
-
479 votesfeature-under-review · 34 comments · Adobe XD: Feature Requests » 07 : Integration with other tools · Flag idea as inappropriate… · Admin →
-
621 votes
-
863 votesfeature-under-review · 62 comments · Adobe XD: Feature Requests » 02 : Prototype mode · Flag idea as inappropriate… · Admin →
-
741 votesfeature-under-review · 47 comments · Adobe XD: Feature Requests » 01 : Design mode · Flag idea as inappropriate… · Admin →
-
4 votes2 comments · Adobe XD: Feature Requests » 10: Developer Handoff · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment I absolutely agree with this. However, there is a partially working solution right now that already exists for Font Awesome icons. Currently when a text box is active and has Font Awesome as the font to be used you can type in the shorthand name of the icon and it will auto populate the icon for you. Subsequently as a result of this it shows the shorthand name in the bottom right "Content" area instead of an empty font slot. (See image attached). Also, this short-hand text doesn't help specify the actual type / style of the icon e.g. (light, regular, solid) so additional information is required to "help developers drive better consistency for end product if using an existing design system" etc..
The above described is somewhat helpful, however what would be most helpful is if:
1. It also added the ability to comment uniquely on each asset (Dev notes) as you've described for developers to see (Additional information) when selecting an element in spec mode
AND
2. Also show the actual class name text for developers to see and reference with their css files in the code-base e.g. ("fas fa-filter")
-
106 votes15 comments · Adobe XD: Feature Requests » 10: Developer Handoff · Flag idea as inappropriate… · Admin →
-
18 votes
-
9 votes
I’ll adjust this to focus on the shortcut, but you can already search through elements in your layers panel in the search dropdown at the top of the panel.
-
3 votes
Disappointing that this still isn't addressed as part of May 19, 2020 release