Adobe Xd Version 57.1.12.2 x64 | Creative Cloud Synch 6.6.4.2 | Mac OS Ventura 13.6.1
____
Does Adobe Xd have an unknown limit to…
1. the number of states a component even of moderate UI complexity can have?
2. the number of tap-interaction transitions to other states supported by each component state?
I cannot share the file or a screen capture of it for confidentiality reasons; I'll have to describe the scenario.
The component in question has 24 distinct states in addition to its default state, which I use to edit the UI elements recurrent throughout the feature. The default state is the 'edit flagship' of the feature, not a representation of a navigable variant of that feature, to ensure that any minor UI change is easily cloned to the 24 dependent / 'subservient' states of the component, without countless copy-paste actions.
Each state has between 1 and 7 tap interactions, each causing a transition to other states within that component. Assuming an average of four destination paths in each state, the total permutation count is under a hundred. It should be well within Xd's prowess to keep each interaction and its destination completely separate, unambiguous, and free from interference.
And yet this is not what happens in preview mode. Basically, I cannot rely on the click/tap interactions I've assigned to UI elements, individual or grouped, to lead to the destinations I've specified. The actual path taken when tapped is often utterly random, leading me to believe the destination assignments are wrong. That should be easy if time consuming to fix—but it's not what happens: They're correct, but ignored.
Needless to say, such a prototype is utterly useless for conducting a clickthrough test with users.
I'm wondering what's wrong here.
The feature in question is a popover menu with a short checkbox list on which 4 of 10 options are selectable, and a date picker on which only one date is selectable, plus a standard cancel/submit call to action that leads to the menu closing and an ensuing state indicator of the selection permutation the user has made.
The pattern (since I cannot reveal the actual use case) resemples that of a product downselector on your typical e-commerce site, where a combo of checkbox or price range selections on a filter panel becomes sticky on the page header (to remind you of your filter choices) while you're browsing the results.
What is it that could introduce destination ambiguity here? In other words, why does Xd ignore and override clearly defined and stable click destinations and then appear to do what it wants in a UI consisting of text, lines and fills—nothing that introduces undue memory burden or file bloat?
In my experience with Axure RP, interaction randomness is usually a consequence of some mutually exclusive setting or interactive assignment—something that is physically impossible with Xd's much simpler interaction design paradigms. Any ideas? Are there limits to the flow complexity Xd tolerates?
1 Correct answer
1
Reply
AdChoices