Please! Stop releasing such buggy updates!

Hi All,

We apologize for the bad experience. Would you mind updating XD to 41.1 version and let us know if you are still struggling with XD? 

We have also shared your feedback with our team for making improvements in the future.

We will try our best to help.

Thanks,

Harshika

I feel your pain. It feels Adobe XD isn't tested on Windows. Last updates just added boring features instead of fixing bugs.

Where to start?

The project I currently work with started out in Sketch. I imported it into XD, and thought "wow, this actually works!"

Then I noted that masking works totally different. Fair enough, I went through about 4-500 symbols and re-masked them. To my chagrin, I noted that as soon as you mask something, you can't do zip about the layer order. You have to unmask, change order, then mask again. OK, so let's do that then, I thought, and found out that as soon as you change any groupings that contain text, all the text overrides in all instances of the symbol/component is reset.

By now I'm really starting to wonder about the speed and efficiency of XD. Not only all the extra manual work because the app behaves like the village idiot. But with a sh*t-load of artboards on the same canvas, moving, resizing or manipulating stuff reminds me of pouring really cold maple syrup. Where is that supposed "design at the speed of thought" thingie? Finding anything in the component library turns out to be painful. Rather than a neat hierarchy mirroring the design context, it is like a scattershot, sorted by who knows which parameters. Re-sorting to your own liking is pretty damn tedious, and when it has reverted to chaos the next time you open the file you give up. Searching sounds good, but require you to change focus from where you are to a search field, hoping you named your master in a reasonable manner.

A million years later, with all the symbols I actually need to override under control. Now renamed to be easy to find without hierarchy. With states replacing other overrrides etcetera, etcetera, ad nauseam, I'm supposed to start collab with another designer. We push the document into the cloud, and the maple syrup is turned into a slowly melting glacier.

As soon as you open the document, it starts "saving" (exactly what is a mystery), and is unusable for up to half a minute. Then as soon as you do anything, there is a freeze while it does an interative save. Those saves BTW is not always reliable, and from time to time, regressions surface, where elements, component instances and even component masters goes back in time to an earlier iteration. Not only does the app freeze for my own saves, it does so when my collegue does something and it gets saved. The only thing smooth about the process, is watching the element you just tried to move in vain, suddenly start sliding slowly over the screen as the app unfreezes.

By now, I'm just about on the verge of trying to force the team leaders to go all Mac for the designers, allowing us to use Sketch Cloud in place of the CC-cloud that never seem to work anyways. The only reason to live through this pain, is to allow the project to be multi platform. I'm even eyeing Figma as an alternative, just to flee the monumental pain of spending half my days waiting for and repairing whatever XD f*cked up.

This app need the following, ASAP:

• A component hierachy, with folders, subfolders and sorting.
• Components should be available without leaving the layer view.
• Colors, Character Styles and Components are not the same concept, keep them separate.
• If you have more states than the very limited vertical space in the state box allows, make it possible to expand the state box, rather than to introduce scrolling.
• Multiple canvases, so that each canvas can be limited to a handfull of contextually related artboards.
• Smart use of resources, so that the canvases not currently visible is keept in the background with minimal cpu/memory load.
• Override dependability, with an option to reset styling only, with text-overrides and icon-choices intact.
• Override inheritance. If I have embedded an instance into another component and overridden it, it should stay overridden when I use the new component.
• Respect for the difference between paragraphs and line breaks, so that you can use these concepts to the fullest.
• Respect for internal margins within a component, so that when an element or a string of text changes length/size, the neighboring elements move with the change.
• Shadows should match what is possible with CSS, that is multiple shadows. This is crucial for Material Design etcetera.
• X/Y positions should be contextual for elements within an artboard. After all we design on artboards, not on the whole canvas.
• Dependable and fast iterative saving and loading, you should NOT have to keep backups locally at all times.