What is unclear to me, is how does it work with Avalonia pricing wise? If I am having commercial application for Windows, Android, MacOS, iOS (Microsoft MAUI range) then according to [1] I would need to dish out 125000 EUR per application. But it was never clear to me what are the conditions which actually triggers the difference between free and paid plan.

[1] https://avaloniaui.net/xpf/pricing

▲

exceptione 3 hours ago | parent | next [-]

Let me rephrase what sibling said: the paid offering is for you when you have gotten an existing traditional windows-only wpf application and you want to have that appplication cross-platform as-is, foregoing any effort to port it to AvaloniaUI.

You won't need the paid offering if you build your stuff in AvaloniaUI directly.

▲

oblio 2 hours ago | parent [-]

How mature is Avalonia for an universal app? Big 3 desktop plus big 2 mobile?

	▲	exceptione 2 hours ago \| parent [-]
		I can't comment on that specifically, but it works with MVVM extensions toolkit, which is handy for decoupling of event handling and is helpful in complex scenario's. Most import thing to look for are the components you need imho. You can build themselves, but if you can use something ready made, that helps of course. You would best take look at their gallery to see if you see something similar for your needs.

▲

Kwpolska 3 hours ago | parent | prev [-]

Avalonia is free and open-source. Avalonia MAUI currently appears to be MIT as well [0]. The pricing you’ve linked to is pricing for their paid offering, which wraps Avalonia and a WPF-style API for easy migration of legacy apps.

[0] https://github.com/AvaloniaUI/Avalonia.Controls.Maui/blob/ma...