|
|
|
|
|
|
by andrei_says_
3077 days ago
|
|
|
It doesn’t help that the designers often do not code and model the experiences in animation software. I am currently working on a redesign and just saw the agency’s suggestions for animation. Seem to be highly influenced by iOS apps’ transitions and motion. But this is a website, for browsers, to be displayed on a variety of screen sizes, on a variety of browser versions. And the users of my website use mostly other websites so if I create something that behaves very differently, the training they have will be wasted and the experience — unintuitive. So the agency will present this to high management, in an ideal layout, designed in animation software, moving perfectly smoothly and solving for only one case without a clue on how to approach corner cases. If management finds it sexy, we’ll be stuck with development and maintenance of ultra complicated code. And the pleasure of discovering and resolving all corner cases ourselves, on a deadline, with limited budget. |
|
|
I don't think even that is a good enough reason. They simply don't approach the problem the way someone using their app would. It's the developers' problem to turn a difficult design into code, but the real problem is that even when that is done perfectly, the UX still sucks.
Every time we redesigned a major UX component of the dashboard of our (desktop) app, we would grab a random secretary, HR person, accountant, or anyone else we could find and borrow an hour of their time and just watch them try to use it without any prior preconceptions that come as a result of designing/coding the interface yourself.
It's been 10 years since we used that trick and I've moved on from that company, but I still think it's the best approach I've ever come across short of outsourcing some sort of panel testing.