r/windowsdev • • Aug 13 '25

How do I make native Windows apps in 2025?

41 Upvotes

I’m trying to figure out the best way to build native Windows applications in 2025.
There seem to be so many options, but these are the ones I am interested in:

  • .NET (WinUI, WPF, MAUI)

  • Flutter

  • Qt

From the .NET options, which one is the best choice today and why?
Should I also seriously consider Flutter for a Windows-only app, or is it better to stick with something in the .NET ecosystem?

Also — is there any other framework or technology I should be looking into that I haven’t mentioned?

I’m mostly interested in performance, ease of development, UI flexibility, and long-term support.
Real-world experiences are welcome!


r/windowsdev • • Jun 11 '25

Windows 7 was absolutely perfect

26 Upvotes

It was the best version of windows ever made, good modern UI with aero glass and animations, it was fast and consistent with widgets and a lot of features that look modern in 2025, windows 11 looks like a messed up child’s project, it doesn’t feel like a operating system a company who care about their users will make let alone one of the richest companies on earth with enough people and resources to do better

I just don’t understand what’s wrong with Microsoft executives or whoever is running this shitshow, like how much data can they sell, how much money can they make? How much are they actually getting paid to absolutely destroy trust and user experience for billions of people, like I’m ready to pay that’s how desperate I am, just make a Windows 7 remaster, I’d honestly pay $500 if it’s a one time lifetime license fee, please just give me a operating system that looks good and I can use it for a long time without worrying about random windows fucking updates

I mean come on, I honestly wanna know the number they sold their souls for? Was it worth it?


r/windowsdev • • Nov 06 '25

I built an open‑source C# email client with Uno: Gmail, Outlook, IMAP, native Proton Mail

Thumbnail
gallery
23 Upvotes

I started this project on UWP, and Uno’s WinUI/XAML parity made it the natural path to go cross‑platform without rewriting the UI. I’m shipping Linux, Windows, and macOS builds today from the same codebase, with Android/iOS/WebAssembly on the horizon. Thanks to the UWP roots, it also runs on Xbox.

What it supports:

  • Gmail, Outlook/Microsoft 365, and generic IMAP/SMTP

  • Proton Mail natively without Proton Bridge

On Proton specifically: I implemented Proton‑compatible cryptography in C# using BouncyCastle, following Proton’s public specifications and open‑source references. The implementation is open source, and all encryption/decryption and key handling happen locally.

Local AI agents (optional): the app supports pluggable on‑device AI via Microsoft.Extensions.AI.Abstractions and Microsoft.ML.OnnxRuntimeGenAI. This enables things like local summarization/classification/draft‑reply helpers without a cloud dependency.

Why Uno (for my use case): coming from UWP, WinUI/XAML parity and strong Linux/Web (Skia/WASM) targets aligned best with my constraints at the time.

What worked vs. what was tricky:

  • Worked: high code reuse from UWP; solid desktop performance with Skia; straightforward path to Linux/macOS (and keeping an Xbox build via UWP).

  • Tricky: consistent theming across Linux desktop environments (GNOME/KDE/Cinnamon), packaging/signing (especially macOS), and a few control‑level parity gaps.

I’m collecting broad feedback: what should a modern desktop mail app get right for you to use it daily? Share your must‑haves, dealbreakers, and any general thoughts.

Links:


r/windowsdev • • May 11 '17

New controls and brushes from Microsoft Fluent Design System

23 Upvotes

If you have been watching the Build conference closely, you would have noticed the new Microsoft Fluent Design System, aka Project Neon. Now a few documentation have come up

What do you think of these? Did I miss anything?

edit 1: added Tree View and Color Picker. Thanks tpartl!

edit 2: added Parallax.


r/windowsdev • • May 09 '26

I built an ext2/3/4 read/write driver for Windows with Claude's help — looking for brave testers

22 Upvotes

30 years of dev experience, never enough free time. I always wanted a proper ext4 driver on Windows and never had eight weeks to spare to write one. Turns out with Claude doing the typing, I needed about three hours.

Before anyone rolls their eyes: "AI wrote it" usually means nobody understood it. That's not what happened. I know how to code. Claude knows the manuals — ext4 on-disk layout, WinFsp, MBR/GPT, the SCM dispatcher — in a way nobody carries in their head. My job was telling it what it got wrong, which spec section it misread, which bug to chase, what the test suite needed to prove. A lot of "no, re-read section 4.2, that field is little-endian." It works because I knew what wrong looked like, not because the model is magic.

⚠️ Heads up: this isn't a finished product yet. It's read/write — yes, it really does write to your ext disk, and yes, that means a bug can corrupt it. Back your data up first. Beta quality: works well in practice, but you're still the QA team.

That said: in daily use it's been solid. I've never lost a disk to it, including on the write path. I think it's a marriage of three things: the ext3/4 journal catches anything that goes sideways before it becomes corruption, Rust makes it hard to be sloppy with the on-disk structures (no accidental field mis-sizes, no UB, no "oh I forgot that case"), and the spec ties it together — if you follow it correctly, the FS does what it's supposed to do. Plug in a Linux USB on Windows, it shows up as a drive letter, you read and write like any other drive.

I actually use this every day. I work on a Raspberry Pi project, and the typical setup is SD cards bouncing between the Pi, Windows, and Mac. I'm on Mac, a developer I work with is on Windows — so I built an ext4 driver for me and one for him. This isn't a hobby I'll lose interest in next month; making it rock solid is in my own self-interest.

Two repos:

  • ext4-win-driver — the driver itself. Read/write ext2/3/4, auto-mounts on plug-in.

  • winfsp-fs-skeleton — want to build your own Windows FS driver? Start here. I pulled all the WinFsp boilerplate (service, disk-arrival watcher, partition parsing, raw I/O, MSI installer, CI) into a reusable skeleton. Plug in a detect() and a winfsp-rs FileSystemContext and the Windows side is done. FAT, XFS, btrfs, ZFS, HFS+, APFS, your weird hobby FS — go.

It's Rust, but you're not locked in. If your existing FS code is C or C++ (most reference implementations are), build it as a library with a C ABI and link it from the FileSystemContext. Rust does C FFI fine. Keep your battle-tested parser, write the Windows glue once.

And Rust is a genuinely good fit for working with an LLM. The compiler doesn't let trivial mistakes slide — no nulls, no implicit conversions, exhaustive matches, lifetimes. The "looks plausible, crashes at 3am" class of AI-generated C bug just doesn't survive cargo build. The borrow checker is a much harsher code reviewer than I am, and it never gets tired.

GPL-3 (WinFsp is, so anything linking winfsp-rs ends up GPL anyway).

I'm posting because I want testers. Bug reports, crashes, "it mounted the wrong partition on my 16TB array", "it scrambled my journal" — all welcome. Especially interested in weird setups: LVM, encrypted volumes, ext4 with unusual feature flags. If you've only got one copy of the data, please don't be the first person to find a bug. Spare USB stick or a disk image.


r/windowsdev • • Jul 19 '26

I made an open-source BAT-to-EXE compiler with a CRT-free Win32 runtime (14 KB)

21 Upvotes

Most BAT-to-EXE tools I found are either closed-source, outdated, or no longer actively maintained. I wanted to build a fully open implementation that anyone can inspect, modify, and build themselves.

The compiler itself is written in C++ using the Win32 API, while the runtime stub is written in C and built without the CRT using MinGW. The runtime stub is only about 14 KB, has no runtime dependencies, and supports both x86 and x64 Windows (Windows 7 and later).

Current features include:

  • Resource embedding

  • Custom icons and version information

  • x86/x64 compiler/output

  • An experimental in-memory execution mode (executing the embedded batch script through pipes)

The in-memory mode is still experimental and intentionally isn't the default. Some batch features that rely on a physical .bat file or interactive input are not fully compatible yet, so please read the documentation before using it.

The project is licensed under LGPL and I'm mainly looking for feedback, bug reports, feature suggestions, or general thoughts from people who are interested in Windows native development.

GitHub: https://github.com/LeapHeap/XBat

Thanks for taking a look!


r/windowsdev • • Dec 17 '16

UWP Experiences – App Samples - Building Apps for Windows

Thumbnail
blogs.windows.com
18 Upvotes

r/windowsdev • • Dec 14 '25

Setup.exe Icon - History & Modern Appearance

16 Upvotes

The Icon in question.

Being a developer in the modern era, who "grew up" in the modern era, I am always happy to go on rabbit holes, learning the most obscure facts around parts of the Windows Operating System. But this one has really stumped me.

The earliest usage I can find of this icon is within the MSI toolset for the Windows Installer Engine.

There used to be a bootstrapper feature of the toolset which came in two parts: the setup.exe template file, and the msistuff.exe. These are both deprecated, no longer installed with the WINSDK with their source code available, where the icon can be found. Despite their deprecation, something as modern as the .NET 10 SDK installer executable uses this icon, among thousands of other third-party installers.

How is this icon being used in the modern era to bootstrap msi installations? I assume there isn't one singular answer, but it would be nice to know the source of this icon usage, which allows me to learn more about how other developers (like official Microsoft developers) package their MSIs for distribution.


r/windowsdev • • Jul 01 '25

How to Integrate Your App into the Windows 11 Main Context Menu (Bypassing "Show More Options")

16 Upvotes

When I recently had to implement a context menu extension for Windows 11, I found that getting clear, up-to-date guidance was surprisingly difficult. The documentation was scattered, and many examples still targeted legacy approaches. After some trial, error, and digging into GitHub repositories and official samples, I managed to get it working.

To help fellow developers avoid that same confusion, here’s a clear, technical roadmap to integrate your app directly into the primary Windows 11 context menu, without being buried under “Show more options.”

Why This Matters

Windows 11 redesigned File Explorer’s context menu to improve consistency and security. However, this change also deprecated most traditional IContextMenu handlers from the top-level menu.

Unless your app uses the new IExplorerCommand API and follows proper registration via MSIX or Sparse Package, it will appear only in the legacy overflow menu, hurting discoverability and UX.

Technical Roadmap

1. Implement IExplorerCommand

Write a COM shell extension using C++ (C++/WinRT or WRL). At a minimum, implement:

  • GetTitle() – label for your menu item

  • GetIcon() – optional icon for branding

  • Invoke() – logic to launch your app/tool

  • GetState() – enable/disable logic

  • Optionally: IObjectWithSelection to work with selected files/folders

Note: C# is not supported for this integration, due to COM registration and packaging limitations.

2. Register via MSIX or Sparse Package

You must declare your command in an AppX manifest and register it through either:

  • A full MSIX package, or

  • A Sparse package (recommended for unpackaged desktop apps)

Example manifest snippet:

<Extension Category="windows.fileExplorerContextMenus">
  <FileExplorerContextMenus>
    <ItemType Type="*">
      <Verb Id="MyCommand" Clsid="{YOUR-CLSID-HERE}" />
    </ItemType>
  </FileExplorerContextMenus>
</Extension>

This ensures your extension is recognized by the modern Windows 11 shell.

Reference Implementations on GitHub

These projects helped clarify the process for me:

Real-World Examples

  • Notepad++: Supports top-level Windows 11 context menu integration (v8.5+).

  • NanaZip: Fork of 7-Zip with native Win11 menu support using.IExplorerCommand

  • TortoiseSVN/TortoiseGit: Provide optional support for modern menu styling.

Limitations to Be Aware Of

  • No deep submenu support yet in the Windows 11 menu model

  • Limited number of top-level custom items (roughly 16)

  • Only native code (C++) supported; no C#/.NET wrapper compatibility at this time

Summary

If you're developing a shell tool, editor, or utility that users interact with via right-click:

  • Use IExplorerCommand for native integration

  • Package via Sparse or MSIX with the correct manifest

  • Reference the GitHub examples above for implementation patterns

This approach avoids “Show more options” and puts your app where users expect to find it.

Hopefully, this saves others the same learning curve I had to go through.


r/windowsdev • • Sep 24 '18

How I Built a $700/mo Windows App

16 Upvotes

My app growth is not viral, but it is consistent and I am super proud of it. I put together a few tips based on my experience.

https://medium.com/@ibliskavka/how-i-built-a-700-mo-income-stream-ad63c9a9ec12


r/windowsdev • • Aug 29 '16

5 Tips for Designing Beautiful UWP Apps

Thumbnail
simonjaeger.com
16 Upvotes

r/windowsdev • • Oct 31 '19

Microsoft to release an alpha of WinUI 3.0 next week, starting with UWP

Thumbnail
zdnet.com
14 Upvotes

r/windowsdev • • Nov 01 '16

Every app looks better with charts: Introducing UWP QuickCharts

Thumbnail
blog.ailon.org
14 Upvotes

r/windowsdev • • Mar 22 '18

Windows 10 on ARM and devices–hang on to your continuum dock!

Thumbnail
dotnetbyexample.blogspot.com
13 Upvotes

r/windowsdev • • Oct 31 '17

UWP Community Toolkit: Driven by Microsoft, Developed by the Community

Thumbnail
blog.ailon.org
13 Upvotes

r/windowsdev • • Jun 29 '17

We're looking for a remote UWP dev, anyone interested? We will pay for your nuts and dried fruits (srsly 😅)

Thumbnail
doist.com
13 Upvotes

r/windowsdev • • Nov 18 '16

Announcing UWP Community Toolkit 1.2

Thumbnail
blogs.windows.com
13 Upvotes

r/windowsdev • • Aug 18 '16

GitHub - Microsoft/UWPCommunityToolkit: The UWP Community Toolkit is a collection of helper functions, custom controls, and app services. It simplifies and demonstrates common developer tasks building UWP apps for Windows 10.

Thumbnail
github.com
13 Upvotes

r/windowsdev • • Jul 09 '25

WinUI3 Visual Design

12 Upvotes

I just created a tool for visually designing a WinUI3 XAML for WinUI3 apps.
https://github.com/WindowsNT/XAML-Lab

Waiting for your comments so far, I 've put a few FrameworkElements, a menu designer and XAML export. Binary download available.


r/windowsdev • • Aug 08 '18

Announcing Windows Community Toolkit v4.0 - Windows Developer Blog

Thumbnail
blogs.windows.com
12 Upvotes

r/windowsdev • • Feb 19 '17

Lessons learned from Building a Visual Studio Shell with UWP - includes links to UserVoice so you can upvote features

Thumbnail
thomasclaudiushuber.com
12 Upvotes

r/windowsdev • • Oct 06 '26

Inside the Windows I/O Manager : Deep dive into how read I/O requests are initialized.

Thumbnail
winware31.blogspot.com
11 Upvotes

r/windowsdev • • Oct 24 '19

Well-known UWP developer Rudy Huyn joins Microsoft

Thumbnail
windowscentral.com
11 Upvotes

r/windowsdev • • Aug 29 '19

Anyone who tells you UWP is dead is a liar, they're adding TONS of stuff to the SDKs

Thumbnail
twitter.com
11 Upvotes