[xanderjanz]

Russ, whats the value of UX on products that don't exist yet? DevEx is the egg that creates the UX chicken.

I love your attention to UX, but clearly developer experience is above user experience in simply a chronological sense.

[xenadu02]

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]

Yep. 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.

[pnloyd]

This is such an interesting counter point. So really there needs to be a balance in tool choice that finds an optimum between deliverable UX with enough devX so that devs can stay sane enough to get the product built in the first place so the UX can exist.

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 ;-) )