Cross linking prototypes
When working on large projects it becomes hard to drag prototype links when you have 80 plus pages.
It would be great to be able to link from one xd item to another in a separate prototype file. So you can break large files into usable chunks. maybe have tabs within the artboard.
Malgorzata Szczurowska commented
Would be nice to have ability to connect artboards (in prototype mode) between different files of Adobe Xd so then you dont need to keep all parts of the prototype in one file but you can split it into other ones and then just connect into one big prototype.
This would be awesome!. Would be a huge help to be able to pin a single screen to a user story without having to place the XD link with a call out to page number.
Some project managers to get this done quicker... started taking screen shots, this caused a management mess having to keep stories in sync with XD wireframe updates.
I create a lot of apps using a single design system. I find myself creating a huge amount of duplicated workflows. The components solve the problem of reusable controls but I want a reusable process.
An example might be a logon process. It might be the same for all apps. Instead of recreating that process for all apps, I would like to embed a login workflow to my process and define an entry and exit point (or multiple entry and exit points) which I can then hook a wire onto.
In the attached annotation, the purple node on the login process is a single entry point but I see no reason why you couldn't define multiple.
The purple node on the Log in button defines the exit point.
When embedding that encapsulated workflow it would expose its entry and exit points which you can drag a wire on to.
SHAJI T K commented
If I have a big project, I would like to split it into smaller files and later on join the files and send as a single prototype link
Use case: Navigation and content interlinking with individual XD files
- A navigation XD file with three content links
- Interlinked to separate XD files for the content.
Wes Gehbauer commented
This would drastically increase the efficiency of our team!
Currently you either need an insanely complex file in order to reflect an entire application (even a simple one) or several disparate files for various flows and scenarios
Being able to link from one prototype file to another would allow us to create realistic interactive prototypes of an entire app and various scenarios while keeping the flow of each scenario separate and more manageable for both designer & developer!
PLEASE ADD THIS FEATURE :D
Hello! I have a question about Adobe XD options: will there be in the future an opportunity to compile few projects in one prototype with hyperlinks? At the moment I have a big project with lots of artboards in Adobe XD. I would like to make one link for our customer, but I don’t have enough space in the prototype project in Adobe XD. I thought about consolidation of few Adobe XD files by buttons with hyperlinks. And I'd like to tell about the heat-map optional function for Adobe XD for the best analytics. Best regards,
Manoj Balineni commented
Ability to link one art board from one prototype to other art board in other Xd file makes your work easier instead of coping and pasting art boards and re creating links to art board.
Anthony Schmidt commented
Love this idea. To be able to have an .xd file per user story, sprint, or epic - depending on how your group likes to develop features - and then be able to link from one to the other, would let us demonstrate end-to-end tasks, while keeping the source files small and agile.
Birgit Pohl [ACP] commented
Since the stage is limited in the size I would also use it for one big project.
Thomas Hallgren commented
As a designer I would like to share my designs on the web, and be able to jump from one XT project to the other. There are many uses to this capability. 1) Breaking up a project. 2) Sharing a chapter page that can be updated.
As projects increase in number of screens it would be great to link to a screen contained into another project.
This could be useful for the development workflow. My developers generally can conceive one flow per time. (from 3 to 20 screens)
This function can help to divide the project in compartments for a more agile workflow.
For more details please send me a message and I would be happy to explain better.