2 ms·
Maybe it's a bad idea to build critical UI bits with React? I mean, I'm a big fan of React for a lot of things... but I don't think critical pieces of UI/UX in
by tracker1 9mo ago
Maybe it's a bad idea to build critical UI bits with React? I mean, I'm a big fan of React for a lot of things... but I don't think critical pieces of UI/UX interactions should be built with it at all.
The taskbar, start menu, file explorer, desktop and system settings are areas that should be boring, consistent and just work. That hasn't been close to the case since Windows 7.. Windows 8 was the start of the decline and that was over 13 years ago. While I like some of the things that have come to Windows since then, there's probably twice as much to dislike. Hire/promote/raise someone to act as a UX czar for Windows all around... design a "final" UI/UX target that covers existing features (starting with a checklist of everything that currently can be configured everywhere)... and finish that design.
Stop shifting gears and enshitifying the overall experience to wring every cent of "value" out of every user out there. Get a full release cycle or two with no new features... just solid bug fixes and a more consistent UI/UX. I know there's kernel features for new GPUs, improved storage and CPU interactions and scheduling... but the UI/UX on top of the kernel is a mess and it shows too well.
Get your staff aligned on a common UX theme... I don't care if it's back to Fluent or something closer to where Win11 is, but at least get it consistent above all else. It's a mess. Fire half the managers... stop giving out bonuses based on new features in windows, and give bonuses on sections of config/settings that are marked as complete without falling back to legacy UI from the late 90's. Not that the 90's setup was that bad compared to the hybrid bastard we have today.