Artboard overview in published prototype
Hi,
2 related questions here:
- forgive me if I'm wrong, but I can't seem to find a way to open the artboard overview (if there is one) in the published prototype. I mean in the web application, not the desktop preview. The published design specs have an overview page of all artboards, the published prototype doesn't. Am I missing something? Or is it not implemented (yet?) ?
I consider this as a nice to have feature, because in some cases not all prototypes are clickable, so only navigating with the arrow keys is not sufficient.
- Is it possible to add the artboard name somewhere in the view of the published prototype? Now it's only visible in the url, also for navigation purposes, the artboard name could be important to know you are on the right screen.
Keep up the good work. Thx
Hi,
Thank you for sharing your feedback with us!
We are happy to know that you like the overview page with all Artboards listed for a glance. Please note that currently this overview page is only presented for Design Specs.
To understand more about your use cases w.r.t Prototype, I had couple of questions here.
1. Is navigating to the artboards the only use case that you would use this overview page for in case of Prototypes?
2. When you say not all artboards are clickable, can you explain this with an example? I wanted to understand how would your artboards be linked in that scenario.
3. When your prototype is created, how would you like your clients or stakeholders to navigate through for review? Would you be ok if they just use the overview page and go all across without going through the experience flow you have created?
Thanks!
-
Siau Jiun Lim commented
it would be great if XD able to show an overview page with all artboards in the prototype view, with the reason below:
- it is human instinct want to able to control, see the overall picture before they interact
- at the state of reviewing, most team members are technical, they want to able to see pages and where they are at.
- some artboard is not fully clickable, this enables team member to navigate all the artboard
-
Thomas commented
I can add a better use case: when I publish the prototype without any linked artboards, all artboards are published. I do this mostly to share designs internally and gather feedback (they navigate with the arrow keys) before creating a working prototype.
This way I can share my designs quickly without linking artboards, but It's there that the overview would be much appreciated.
-
Thomas commented
A question related to that:
Artboards that have no link in the prototype are not included in the published prototype. Why is that?
I would like to share the preview, like I have in the design mode, to another stakeholder (without any prototype interactions). Navigation with arrow keys is sufficient.
I really think this should be an option to either include or not include unlinked artboards. Not including unlinked artboards should not be the default in my eyes.
-
Thomas commented
1. Yes, mainly for navigating. If I can, I compare the behaviour with Invision, they have the overview through a horizontal panel apearing from the bottom. We are trying to work with the complete Adobe XD flow to drop the Invision license in the future. This is a question I receive from the people I share the prototype with. Invision has this feature, and I think we got used to it over time.
2. Some artboards are not fully clickable, to save some time, only a certain flow is clickable. It may be also useful for seeing artboards that are not linked through an interaction. (I understand now artboards are not published when you don't link them?). F.ex. greyed out ...
3. The prototype way by clicking through the artboards is my preference for the stakeholders, but if they want to review a specific screen, they would go to the overview (they say) and find it in the overview or by artboard name. Sometimes it hard to find the screen they are looking for, because not every piece of the artboard is clickable (or maybe because the designs are not user friendly :) ). Once again, we got used to this by the use of Invision, I guess.
Thx