3 ms·
It's all still there in Win32 Apps microcosm, available for anyone to use. I'm currently working on a pure Win32 application and Microsoft's tips are delightful
by mopsi 7y ago
It's all still there in Win32 Apps microcosm, available for anyone to use. I'm currently working on a pure Win32 application and Microsoft's tips are delightfully helpful for establishing a consistent design language across the whole platform. They call it "powerful and simple" in https://docs.microsoft.com/en-us/windows/win32/uxguide/how-to-design-desktop-ux https://docs.microsoft.com/en-us/windows/win32/uxguide/how-t... Win32 Guidelines are also very illuminating: https://docs.microsoft.com/en-us/windows/win32/uxguide/guidelines https://docs.microsoft.com/en-us/windows/win32/uxguide/guide...
My favourite aspect of Win32 is built-in behaviour. Things like keyboard-based navigation and screen readers work without needing any dedicated effort on my part. Visual elements are drawn by the operating system and remain consistent with system theme colors, font size, contrast and other user preferences. I always think about that when I see "Now supports dark mode" in a changelog... why don't they just use standard controls and leave all the finer details to the OS to deal with. Windows has supported system-wide theming for decades.
- int_19h 7y agoThe problem is that even Microsoft's own desktop apps often don't follow these guidelines. And then there's UWP...
- userbinator 7y agoWindows has supported system-wide theming for decades. ...and more recently has been castrating that ability greatly, seemingly in favour of the horrible bland-and-flat trend, which is unfortunate because the ability to customise is highly desirable for usability/accessibility. (Long-time Win32 programmer here, I agree that the built-in behaviour of the standard controls is highly consistent and also very usable.)