Skip to main content
M
mowglivj
Inspiring
September 9, 2022
Question

Clear guide to overrides behaviour

  • September 9, 2022
  • 1 reply
  • 220 views

Is there a definitive guide to component overrides and their behaviour?

My experience is that it all works with trial and error, you never know exactly what's going to happen when you edit a master component after several instances with overrides are present.

 

This is the same when editing component states. Editing any master component with images or text is an absolute nightmare that involves revisiting every single instance and all of its states. Hardly a time-saving tool.

This topic has been closed for replies.

1 reply

HARSHIKA_VERMA
Community Manager
HARSHIKA_VERMACommunity Manager
Community Manager
September 12, 2022

Hi @mowglivj,

 

Thank you for reaching out. We would request you to please go through this help article: Components which might help you.

 

It would be really helpful if you can share the exact issue you're experiencing while doing overrides so that we can help you better.

 

Thanks,

Harshika

M
mowglivjAuthor
Inspiring
September 12, 2022

The exact issue is that the way they work is ill-conceived. A simple visit to the User Voice clearly reveals this but before it got to that, some basic user testing would've revealed all the roaring faults instantly. 

 

The way overrides work is just wrong...

- It makes no sense whatsoever to have to update every single state of a button when you change the text on it.

- it makes no sense whatsoever to have to resize each state of a component individually

- it makes no sense whatsoever to have to replace an image override in every single state of a component when the image doesn't change between any of the states.

 

I could go on and on but this is not my job. My job is to design interfaces not to tell Adobe how to design their interfaces. I would happily do that if they pay me.

 

I recommend that whoever is responsible for designing the UI of XD does some reading on the matter. Some good reference points are Nielsen and Raskin.

 

Being aware of some UI theory basics like GOMS and its variants allows the UI designer to design interfaces efficiently which is something that XD lacks in spades.

 

Basic consistency would also be welcomed. XD's interface is unpredictable, as proof here's a fun quiz:

- If you have something selected in the layer stack and you paste something, where in the layer stack will your pasted element appear? 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices