Win2D VS Windows UI Library

For Windows only, Win2D!

You're looking for Win2D: https://github.com/microsoft/Win2D. It's the official D2D WinRT wrapper, supports UWP and WinUI, has seamless interior with XAML, it's very easy to use and has extensive interop APIs (even more so once we ship the next release) that give you maximum control if needed. I recommend checking it out 🙂

Your easiest bet is likely to use Win2D within UWP or WinUI 3, then you could just throw a CanvasControl as the root of your UI and draw whatever you want on it, including setting individual pixels. Alternatively an easy way to do that could be to use a WriteableBitmap in WPF/UWP/WinUI 3 just drawn into a root Border or something, and then you can easily manipulate pixels there. Of course, that'd be slower and not CPU accelerated, but still viable depending on your exact use case.

Alternatively you can also try Win2D, which is an official wrapper for D2D available for UWP and WinUI. You could use its CanvasAnimatedControl panel and then do your drawing from there, and just manually draw all your particles. The actual drawing would still be GPU accelerated, so it'd be relatively efficient (though less than using a custom shader, as you'd be queueing each particle from the CPU side).

To make a long story short, it's a UWP app since I've used DirectX 11 for drawing on the screen. I use C#, and I needed win2d (https://github.com/microsoft/Win2D)

Universal Windows Platform was introduced as the new hotness, but in my personal experience lacks a number of features from WPF I couldn't part with. It seems to have flopped a bit outside of applications developed by Microsoft. Projects that I though would bring features I really wanted (like win2d: GitHub - microsoft/Win2D) seem to have lost support. I'd hold off on this.

I wish that was true, but even the new stuff, like their new frameworks, performs poorly while their older frameworks perform really well. That's brand new code, with no legacy codebase to care for.

The reason why I don't recommend Winui is the million bugs it has. See the github issues page. All Microsoft ui stuff sucks currently. But if you use WPF why not FluentWPF

Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.

Compared to UWP or WPF, WinUI 3 is somewhere between 100-200% slower and consumes 7-20 times as much RAM as the old frameworks (for certain operations).