Windows native app development is a mess

A nostalgic Windows fan tried making a tiny utility—Display Blackout—that simply dims side monitors for gamers. Instead of a chill throwback, he hit a maze of choices and ancient plumbing. To do basic stuff like list screens, show black overlays, catch a hotkey, and add a tray icon, he kept tripping over decades of frameworks: Win32, WPF (Windows Presentation Foundation), WinUI, MAUI… and still needed old-school Win32 for key pieces. His verdict? “I’ll pick the web stack any day.”

The comments lit up. One camp chanted “framework bingo,” with ashwinnair99 summing up the vibe: it’s been a mess for 15 years and nobody knows what to pick. Others fired back with user-first takes—wolvoleo loves how fast native apps feel, even if building them is chaos. The plot twist? intrasight blames Windows’ legendary backwards compatibility—the thing that keeps your grandpa-era apps running—calling it both blessing and curse, like Win32 refusing to retire. Meanwhile, drive-by advice flew in: “Just use Qt,” declared delduca. And the web crowd piled on: ozim says even Microsoft ships apps with web tech like Electron—because open standards beat platform lock-in. The running meme? “Choose your fighter: Win32 vs WPF vs WinUI vs MAUI vs Electron vs Qt.”