Hello,

I love Adobe Experience Design but I something find myself overwhelmed while working (because I like to organize certain stuff in certain ways). For that I thought about a solution that may help others too.

Publishing without linking (I'm currently working on a project and I have to do changes pretty often because I have to add/replace/change pages and locations and I have to start re-linking everything a lot)
Publish only the "checked" artboards (for example, I want to publish only the homepage and login page, but for now, in order to do that I have to link only those 2 and if I already have 15 artboards linked I have to unlink them).
Publish the "checked" artboards in a certain order (like in Illustrator, it doesn't matter where they are on the canvas, as long as you have them organized in the artboards panel)

Sorry if I'm not coherent, it's 1 AM where I live and it's been a long day.

Any feedback, comments & recommendations are welcomed.

Hope the picture helps.

Thank you.

As you're aware, comments/pins can be applied to a prototype once a link has been generated. However, if a new link has been generated since the previously generated link, then the previously applied pins are erased. When generating a new link, introducing an option which allows the user to carry the pins over to the new link would be very useful feature.

Duplicating or resaving a document does not retain the comments/pins.

Perhaps having the option to apply comments directly within XD could be the way forward. This would allow the creator of the document to add notes, or even flesh out rationale to support the design before passing over to clients or devs.

As a Designer I want to create links that will not change during the project for iOS, Web and Android.

I want to be able to update all (iOS, Web, Android) in one click.
I want to be able to generate a single link for both prototype and specs; all should be updated in one click.

In such case, the links should not be changed but stay the same.

Description
Why is this valuable to you?
Because when designing both iOS and Android applications from one XD file I cannot manage/update 2 spec links at the same time, and have to re-generate one of the 2 links when wanting to publish updates.

If possible, an image or movie to help us understand what you’re talking about
see attachment

I'm often designing for multiple user flows, and thought it would be nice to use the multiple share links feature to share separate links for each flow from the same file. It's dope that this can be done!

However, it's tedious and difficult to a) remember which home screen is attached to which shared link, and b) remember which screens were used in which share link. Sometimes one screen from one "flow" will link to another screen in a different "flow," for example, which makes it hard to deal with. Especially when making simple screen updates it's a lot of work to just update a thing I've already shared.

It'd be awesome if when you switched share links in the panel if it re-highlighted / remembered the screens attached to that link, and which were home. Yes, I could split flows into separate files...but dang, it'd be convenient if those headaches were just made easy.

Please consider creating a standalone viewer, similar to how you have a standalone PDF reader, so clients can open local XD files for viewing.

This is valuable to me for a number of reasons:

1. My client (military) expects to have access to these demos "forever." Our demos cover not simply what the final UI for the final product will look like, but we also create interactive documentation for the product using XD. Over the course of many projects (and links and passwords), this is not sustainable.




2. The shared version that the client sees via the browser often presents incorrectly, particularly with items that use auto-animate. Items animate or jump in a haphazard way when interacted with and are not smooth like they present in the native app. We should not have to explain to the client that the animation really doesn't look this way. Right now we either have to make a video showing them how it works or screencast the animations and interactions while in XD.

In any event, a simple viewer would go a long way in helping us. We could send files securely to the client and they could save the file, open it, and view it as it is meant to be viewed. They would not be able to edit the file.

Thank you for your consideration and votes.

Sometimes when you share your work with others, you may find yourself in a pickle if both of you aren't running the same version of the program.

It's understandable that an older version wouldn't be compatible with a newer one, as it has new features, changed code, etc.
However, I see no reason why we shouldn't allow a newer version to be compatible with an older one. After all, a newer version should have all the same features, and any code changes should be archived somewhere anywhere.

Why not instead make a little warning for the user with a newer version stating that the document was created with an older version, and therefore some functions and features may not be available, and then temporarily open the document using the older version of the program.