ReactiveUI VS Introducing .NET Multi-platform App UI (MAUI)

ReactiveUI is based on Rx and very popular in the .Net world: https://www.reactiveui.net/.

I use PropertyChanged.Fody all the time and it works fantastically and consistently for implementing INotifyPropertyChange. It is even smart enough to understand dependencies within your get/set functions (should you choose to have custom ones) and notify that property if any of it's dependent properties change. While we are on the subject, if you are using MVVM with observables, you should really check out ReactiveUI. It is wonderful.

Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.

My favorite framework is Reactive UI but it's a bit more advanced than most MVVM frameworks since it uses Reactive Programming. You can still try its most basic features, though.

There is a lot of overlap between WPF and Avalonia so I would start with either one of those. Most certainly Avalonia if you plan to do cross platform dev. I would also highly recommend that you learn and conform to MVVM and dependency injection for your architecture in order to write clean, maintainable, and testable code. My recommendation is ReactiveUI. It leans heavily on more modern patterns like Reactive extensions and IObservable and it can do so much more than just MVVM. As such, it is also very similar to Angular so the concepts will transfer easily if you ever need to do web development. On a side note, Pluralsight has a nice quick course on SOLID design principles. If your code is a mess, it would be a good idea to take a course on this though learning MVVM will be a big step in the right direction.

Also, about data binding and reactivity if you really enjoy WinForms, nevar forget!! https://www.reactiveui.net

Your UI needs to bind to something that can programmatically notify it about changes, we call these things View-Models. Usually View-Models implement INotifyPropertyChanged interface (another key interface is INotifyCollectionChanged that is responsible for notifying collection views that number of items is changed and they need to update the UI accordingly). You can do that (the implementation of the interface) manually or use some library to do that for you just to cut some boilerplate code (e.g. ReactiveUI + Fody or Microsoft.Toolkit.MVVM or maybe even this or this).

Some projects like ReactiveUI take on a more webapp style project structure, with resources being in some static resources folder and all code being in a src folder.

I am migrating XF app into MAUI and writing a simple Navigation framework because Prism doesn't work well and I didn't use anything advanced anyway. So, I am surfing the code of MAUI to intercept all the back buttons, etc. I haven't found a single mention of apis related to predictive back "RegisterOnBackInvokedCallback", "OnBackInvokedDispatcher", "OnBackPressedDispatcher", "AddCallback", "android:enableOnBackInvokedCallback" Also I don't see any issue on github that would say "Support Android Predictive back". Only one kinda related https://github.com/dotnet/maui/issues/8680

Below issue is still reproducing in Maui .net7.0 version also. #10163

Maui is Open Source, MIT License

https://github.com/dotnet/maui

.NET is Open Source

https://dotnet.microsoft.com/en-us/platform/open-source

I do share your skepticism of Microsoft, but it looks like the economics and cash flow dynamics have changed drastically after the advent of the cloud.

Microsoft is more focused on getting developers onto its ecosystem and help them with open source projects with the hope that they will use its Azure cloud services and bring in the money.

My skepticism is a bit relaxed now and I have no qualms using .NET.

I hope I am not wrong.

It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.

Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.

[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup

[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)

While this is the quite endorsed by the community: https://github.com/dotnet/maui/discussions/339

I think the fundamental issue is that desktop Linux is way too fragmented. Not only just GTK2/3 and Qt but you have GNOME, KDE, XFCE, Cinnamon and then you have X11, Xorg, Wayland...

To be honest, all those craps are why desktop Linux never took off. I'm very safe to say MAUI for Linux will eventually renders components off its own using framebuffer and hardware acceleration APIs such as OpenGL or Vulkan just because of the market fragmentations...

If desktop Linux truly wants to get the attention, it will need to unify. Fixing dependency hell using Flatpak is the right direction.

There is an existing old fork of MAUI for Linux that uses GTK: https://github.com/jsuarezruiz/maui-linux

First I came across this Github issue: https://github.com/dotnet/maui/issues/9687 - According to this issue, this is a known bug for MAUI iOS, but it works OK for MAUI Android. As I said, I target Android only and I have the exact same issue. It's apparantly fixed with some of the latest versions for MAUI but the problem still occurs to me even with MAUI version:

I saw this and tried to imitate (ofc my lack of experience wouldn't allow me to do it in the exact way). Already found some documentation that allowed to understand better. Thanks for the insigh.

I implemented the Auth controller following this sample code from Microsoft.