I love your attention to UX, but clearly developer experience is above user experience in simply a chronological sense.
I love your attention to UX, but clearly developer experience is above user experience in simply a chronological sense.
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.
For better or worse, does seem the days of Apple engineers working weeks on perfecting an animation behavior are largely over.
Surely we're not going to start making arguments that out ultimate UX delivered apps are hand written asembly (at the most absurd end of the argument ;-) )