I have thought along the same lines for a while now. For me, it started with sacrificing MagSafe, and then the move to drop every port but USB-C. I believe both of those were design decisions without any thought to their real world impact.
The wolves were not some sort of grand threat to commerce in the region. Everyone who made money from livestock and westward expansion were still doing both of those things when the wolves were there.
We decided to kill all of them because they were annoying. That isn’t a capitalist reason, that is a human reason.
The framework you choose to write the application should not in any way impact the UX of that application. You can have crap UX in a React app and great ones using static pages and vanilla JS.
So if their UX sucks, it isn’t because they are choosing to use this framework over something more robust.
May I suggest you adjust your hiring process to ensure you are hiring for attitude and not ability? I put together an article a few years back that explain how we do this:
From my own experiences of being a front end developer and now running a UX team, designers ALWAYS want to involve developers from the start. The issue is that developers either don’t want to participate, or are too overloaded with their own tasks to make time to join.
I get what you are going for here, but less than 6 only works if your options are nice and short as pictured here.
If you have something like “Terrible,” “Below Average,” “Average”, “Above Average,” and “Amazing,” you are going to quickly be fighting horizontal space limitations, especially on smaller screen sizes.
While this is a great article, I continue to take issue with this very one-sided conversation.
The high-tech industry is becoming more and more design-driven. Some of the biggest names in the business…