> For another, the ability to control how a checkbox animates when you check it is of course a valid reason to add another 50 packages and 3 layers of frameworks to their product
To be fair, this sort of complexity usually results from "UX" requirements. Just think about what it takes to materialize those damn figma designs. Google's Material Design is not a simple "skin".
When it comes to business applications (forms, reports, requirements strongly influenced by end-users and evolving in ways hard to predict), my most successful experiences consisted of multi-page apps + vanilla js for validation.
My last project in this field failed though. The client was infected by the figma virus and I failed to compatibilize this methodology with the UI fluff they so fiercely demanded.
To be fair, this sort of complexity usually results from "UX" requirements. Just think about what it takes to materialize those damn figma designs. Google's Material Design is not a simple "skin".
When it comes to business applications (forms, reports, requirements strongly influenced by end-users and evolving in ways hard to predict), my most successful experiences consisted of multi-page apps + vanilla js for validation.
My last project in this field failed though. The client was infected by the figma virus and I failed to compatibilize this methodology with the UI fluff they so fiercely demanded.