A Windows developer's attempt to build a simple utility app revealed the platform's development ecosystem is in shambles. After creating a basic tool to blackout monitors during gaming, the author discovered why developers increasingly choose Electron over native Windows applications. The fragmented landscape forces painful choices between outdated frameworks, bloated binaries, and complex deployment options.

Windows development history reads like a series of abandoned experiments. From Win32 C APIs through MFC, WinForms, WPF, WinRT XAML, UWP XAML, and finally WinUI 3, Microsoft has repeatedly rewritten the rules. Each transition promised modernity but delivered fragmentation instead. The current Windows App SDK requires developers to choose between C++ (memory-unsafe), .NET framework-dependent deployment (requires installing .NET 10), or .NET AOT (bloating apps to 9 MiB for simple utilities).

Distribution adds another layer of pain. While Windows supports traditional installers, Microsoft pushes MSIX packaging that demands expensive code signing certificates costing $200-300 annually for non-US developers. Unsigned sideloading requires cryptic PowerShell commands run from admin terminals. This complexity explains why native Windows development has become a niche pursuit, with most developers opting for cross-platform solutions despite performance trade-offs.