3 ms·
I'm not making that argument, though that is often the reaction I get. My argument is that you should understand when you're choosing to compromise the user ex
by xenadu02 8y ago
I'm not making that argument, though that is often the reaction I get.
My argument is that you should understand when you're choosing to compromise the user experience, why, and how compromised it is. For example, you should know roughly how much worse the user's battery life is because of your decision. That makes the decision an informed one, based on your goals, budget, time to market, and so on.
To claim a decision born of necessity comes with no compromises is delusion. That delusion might not kill you but it points toward muddled thinking. That's dangerous at the best of times, doubly so for a startup.
- xanderjanz 8y agoYep. UX is our jobs (as devs), it should be our main focus and sacrifices of it made minimally. For better or worse, does seem the days of Apple engineers working weeks on perfecting an animation behavior are largely over.