I would like Adobe XD to be able to export/sync to InVision to support "Motion".

"Motion" is a closed beta at Invision that supports micro animations/interactions – similar functionality to what thirdparty apps/services like Atomic, Marvel and Flinto has to offer.

By enabling Adobe XD to export its assets to Invision in such a way that "Motion" inside InVision can be applied to the XD wireframes/prototypes/designs inside InVision.

Preferably XD export to InVision should support sync, perhaps via Dropbox.

PS. For the long run XD could add "Motion" functionality inside XD and thus reverse sync the motions from Invision "Motion" back to the XD files and the integration would be both ways.

Would like XD to work with InDesign in much the same manner that AI and PSD files do. This might be more of a feature request for InDesign however I imagine they both play a role in working together.

Ultimately, in order for a design to be implemented correctly, we need to provide a detailed UI specification for engineering. This specification is often worked on by interaction and visual designers which is part of what makes InDesign an ideal solution for us.

The prototyping functionality is great for communicating how a design could work, but we still need an accompanying UI spec in order for it to be built correctly. This document is also used as a reference for QA down the line to validate the implementation.

I would like to be able to connect different shapes (rectangles, rhombuses/diamonds, ellipses, but potentially everything). The connector line should either be solid, dashed or dotted and end in an arrow. If I move a shape, both of the connected shapes stay connected (the line expands/contracts as necessary). The line should be able to carry a text label, either in the middle, at the beginning or the end (supercool would be if you could add an offset from/to beginning/end of the line).

In other words: I would like to be able to draw a flowchart.

For me as a UX designer (not doing visual design at all!), this is a very important feature to think about interactions on a high-level (which screens/states are there, how are they connected, how does a user move through these screens). Right now, I still have to use Axure for that job, or a dedicated diagramming software like OmniGraffle or (in the old ages) Visio.

This feature could be supported in Design Mode. It's not meant to span several artboards. In fact, for such a feature I would only need one (large artboard), or even better an infinite canvas. As an alternative, it could get a dedicated mode, like a "Flowchart Mode".

Also, in large projects I had to draw more than one flow chart. As an example, last year I had to draw a really large one (needed to be plotted on A1 paper to discuss with clients), but in addition to that, I drew ten sub-flowcharts (the large one was the high-level, the smaller sub-diagrams showed what happened when a user entered a specific screen). All those flow charts were printed into one PDF file with eleven pages. With Axure no big deal – with XD impossible. :-(

Thus, it would be cool to be able to draw one flow chart. Then, add more features like the support of more than one flowchart and the abbility to export only a selected one or all of them into one PDF file. Add more features over time to further improve that, like the different positions of the text label on connecting lines.

Adobe Creative Design supports svg export which is great, but the resulting svg is a little bit suboptimal. For example, if i create a simple circle, give it a stroke-width of 4 with some color and a fill
the resulting svg contains a group element containing 2 circles, one with a fill and the other with a stroke.

It would be great if the exported svg could be cleaner. I attached some sample files. the "exported.svg" is the file exported from Adobe XD, the "edited.svg" contains the svg, which yields the same result but is cleaner.

A cleaner svg would allow to export some portions of a canvas as svg and wrap it up in a Angular or React component. Currently the developer has to scan through the svg and remove unnecessary elements/rearrange them etc.