Software is often judged based on these UI/UX nuances, but the complexity of building a competent front-end system remains an undervalued part of the process.
The front-end team is usually (1) brought in too late in the game to provide effective feedback and (2) not given enough time to build.
When there's not front-end representation at early design reviews or at initial discussions on how APIs should work, then it's easy to forget things like form error handling.
Designs don't account for all possible states, services/APIs are in flux, until the very end.
Everything else is late, and then all of it has to get slapped together with duct tape and shipped in a few weeks. Performance and browser support be damned.
Software is often judged based on these UI/UX nuances, but the complexity of building a competent front-end system remains an undervalued part of the process.
The front-end team is usually (1) brought in too late in the game to provide effective feedback and (2) not given enough time to build.
When there's not front-end representation at early design reviews or at initial discussions on how APIs should work, then it's easy to forget things like form error handling.
Designs don't account for all possible states, services/APIs are in flux, until the very end.
Everything else is late, and then all of it has to get slapped together with duct tape and shipped in a few weeks. Performance and browser support be damned.