If I started prototyping and publish design specs without the prototype linking all the screens the design spec shows only the screens that are linked in the prototype. The specs link doesn't get updated even if I remove all the links.

We need to be able to output design specs to PDF - not all of our clients can access the design specs URLs due to security constraints on their networks so being able to email static PDF design specs is essential to what we do.

How can we export Hover states to development?
In the specs there is only one state in the component. How will development see all states?

Please create the option to download assets as JPGs from design specs. As of right now, there are only options to download as PNG or PDF. JPG seems pretty odd to exclude. Additionally, it would be great if you could have the ability to control your batch export preferences.

Could you build a way to display variable names for color in the specs doc and the ability to write comments to developers?

Also, specs doc is not accurate when displaying colors, spacing and font sizes. You can see the workaround I built to make up for this deficiency.

When you are working with many different fonts it's handy to name them to keep check of what you are working with. However when uploading the design specs to hand over to the developer, it lists the font styles WITHOUT the custom names.

Please can you upload the style names too?

At this time one can see "The date when the design specs was last updated"

When working on a living project, with constant improvements, or in general during development phase, it would be pretty handy for
- developers (identify what to do)
- testers/customers/responsible persons (what to review)
to easily see that there where changes on special screen since last look by showing date and time of last update for each screen.

Having Design Specs online is great, but it should be available inside the app too! OFFLINE.

Thanks in advance.

While sharing the screens to developers on the web. Assets artboard having all the icons/images should get created automatically when all the interactions / screens are done ... and icons/images are marked as assets. This way not only developers can see all the assets at one go but also can download them instantly instead of going to multiple pages and downloading assets separately. It will make designers life easy as well.

It would be great if you can gather the files you’ve used, including fonts and linked graphics, for easy handoff. When you package a file, you create a folder that contains the xd document, any necessary fonts, linked graphics, and a package report.
Like we have in Illustrator or InDesign.

Brackets Code Editor has good integration with PSD Files, which allows it to grab layers, colors, font details and spacing info. More on that here (https://helpx.adobe.com/creative-cloud/help/extract-for-brackets.html)
I wonder whether you can work on features that allow Adobe Extract to grab data(images, font names, sizing info etc) from XD and transfer for Brackets, the same way it happens to PSD ?

Show layout grids on artboards when in development mode - how this feature (https://helpx.adobe.com/xd/help/inspect-design-specs.html#Viewandinspectlayoutgridproperties) was removed as a feature with update 24.x boggles me...

If a link update has been made by a designer to the Design Spec a slack notification automatically gets sent to a channel/user within slack with the link and the changes that have been made. e.g new artboards added etc.

Going from UX to UI I need to give my client a general word/character count so a copy writer can write to what the design is. Would be great to have a "show word/character count" somehow integrated. I currently copy paste everything into a word counting tool, and then document the word counts in a PDF. Super time consuming.

It would be great if the assets library in Adobe Xd be exported to the design specs. In that way developers will be able to get a general specification sheets from the designer. Designers can even create classes for each font and name the colors based on there branding standards.

It's great to have the component at last. But now I need to communicate the component name with the developers. for example: the values of a certain text are not interesting - they only need to know its class (is it H1, H2...?)

Swatches already have the name (only on hover, why?) in the specs, so it's obvious you did recognise the need for that.

For people using Xamarin to develop Mobile Apps we need a Px's to Pt's conversion on the design specs. We are doing a lot of work converting those numbers when developing. Seems to me that a converter would be fairly easy.