2 ms·
I have an analogous problem with my UI guy hat on. I want to develop a UI that makes a complicated product simple, so users can actually use the features effec
by Silhouette 11y ago
I have an analogous problem with my UI guy hat on.
I want to develop a UI that makes a complicated product simple, so users can actually use the features effectively and get their job done. I don't want to build a system that is just putting pretty colours on a convoluted mess of configuration settings and interacting corner cases. That's what some of my clients' competitors do, and their customers have to spend a fortune on consultancy just to make the box work, and my clients pay me because hopefully I'll do better.
Oh, wait, back up. My clients' competitors are making a fortune in consultancy because their customers can't make their boxes work. Good UI is an anti-feature if you can sucker customers into paying for consultancy as well as your product but you can't reliably convince customers to pay more for a product that is better in the first place even if it's cheaper overall, and both of those things may be true more often than we'd like to admit.
This does not leave me in a comfortable position either commercially or ethically.