Thanks, Andrei.

Regarding artboard export, we have some of this available in our Export, and there's also a plugin called Print Artboard that lets you export to common artboard sizes.

We're shipping monthly and itching away at our competitors little by little. We want to do some things the same and some things differently and, in either case, do it right. We have a lot more coming this year to reach parity but features like voice and gamepad help us expand the category to support emerging experience types.

For gamepad, Adobe works with a lot of game companies and this was a heavily requested feature from some of our customers. The body of work to support this isn't dissimilar to supporting keyboard inputs (necessary for web design, desktop app design, and some accessibility design).

Thanks, Justin. We leverage the cloud for our whole sharing model and don't expect that to change now. In your scenario, would you be editing a design system/component library in one file, saving locally, and then hoping to see those changes in another local document?

Hey Matt,

I wanted to follow up on some of the items you point out.

First, we're working on a complete redesign to the Share experience in XD. This will include a unified link for review, development, presentation, etc. For the viewing, this is something we're including in the redesign of the Share experience and are looking into right now!

Mike

Thanks for the feedback, Matt. We're spending a lot of time looking into our sharing features and exploring different ways to support the needs of designers, developers, product managers, exec stakeholders, etc., etc.

Support for things like gamepad or voice doesn't necessarily come at the expense of other features. The team always maintains that we want to do some things (i.e., voice) first and take our time with things we want to do best. Sharing is a big focus for our 2H roadmap this year.

Thanks for the feedback. The XD team pushes for rapid time to market but we also release monthly and expect many of these features to be iterative.

I've passed this to the team that just released guides and we can start including some of these use cases in our roadmap.

You got it. We leverage cloud to enable linked assets between documents (i.e., allowing a designer to use components that another designer is maintaining) and it will be the basis for some future features, but at the core you can still design offline and using local documents.

Hey Paul - you can load up a local file and add Assets (colors, type, components) from the document. You can also save files locally and share them as you wish.

Are you referring to something else?