Differences from Avalonia

[unoplatform]

Differences from Avalonia

[juepiezhongren]

ava's decision to not use mono is unwise

[danwalmsley]

From Avalonia side, we are all templated lookless controls, we are like a cross platform version of WPF.
We support Windows, Linux, Mac, IOS and Android. we do not support Webassembly (yet).

We do support embedding native controls, but that is very early stage work.

We have several backends for Direct2D, Skia, etc for rendering, and all our rendering is done ontop of these. So our UIs look identical on any platform its running.

[jeromelaban]

I'll assuming you want a list of differences between Avalonia and Uno.

Here are a few:

• Uno uses the UWP API and XAML, whereas Avalonia uses a derivative of WPF
• Uno renders using the underlying platform, uses native controls whenever possible, particularly for input controls
• Uno supports WebAssembly, but not Linux and MacOS natively

The Avalonia people may have some more differences here: AvaloniaUI/Avalonia#1636

[jeromelaban]

Yes, and CoreRT is not available on iOS and Android, so Xamarin/Mono is the only possible choice.

[yowl]

A key thing here for me, is that Uno is attempting to be UWP compatible as I understand it. So third party UWP controls should run eventually in Uno on all heads (including wasm), whereas because Avalonia have their own dialect of WPF/Xaml, third party WPF controls will not run in Avalonia.

[jeromelaban]

@juepiezhongren not sure what you mean... android and iOS builds for Avalonia use Xamarin. Which platform are you talking about ?

[juepiezhongren]

sure？ it is said ava is run on core's runtime

[carldebilly]

AvaloniaUI/Avalonia#587

[hossein-bakhtiari-revolut]

Now Avalonia like UNO has WebAssembly support as well