what Microsoft fat client technology are you using?
the current problem for me with Microsoft fat client is there are too much options and no clear one that Microsoft will support long term.
the current problem for me with Microsoft fat client is there are too much options and no clear one that Microsoft will support long term.
Qt 5+ for anything with any level of complexity. Windows has already given up on 'native' UI.
JUCE for audio plugins.
Don't bother with all the 'modern' pretend-windows-is-a-touchscreen-os frameworks.
If pressed I would say WinForms is the most practical choice for most apps today - even though it sucks, even though it's ugly. It's actively worked on (unlike WPF) and it lets you use the latest .NET version.
WebView2 (better Electron) is probably where most Windows development is going in the future, the Windows team is investing a heck of a lot more in it than other technologies.
They deprecated .NET Native and C++/CX and are yet to provide any tooling that compares to them.
.NET Native is stuck in C# 7, while C++/CX got replaced by C++/WinRT with the argument that it is ISO C++ friendly, when in reality it offers the same tooling as using Visual C++ 6.0 with ATL back in the days before .NET came to be, but their developers are so stuck in COM pre-historic tooling that they don't acknowledge that.
Apparently WinUI 3.0 would be the future, with the merge WinRT and Win32, however issues pile up exponentially and even Windows 11 is making use of the deprecated UWP, as the team cannot keep up.
Since MAUI depends on WinUI 3.0, it is yet another reason why it keeps being postponed.
Windows on 2022 with Microsoft stacks MFC (yes really, much better than C++/WinRT), WinForms or WPF (eventually with C++ if required).
Otherwise Qt, Delphi or C++ Builder if enough budget, or PWAs if possible to do so.
Imgui and juce are great frameworks.