XAML 프레임워크들 비교

hongminhee · 7월 13, 2022, 9:01오전

XAML 기반의 GUI 프레임워크들이 많이 나와 있는데요, 그들 각각의 특징과 장단점을 실제 경험한 사람이 잘 정리해 둔 글입니다.

robloo/PublicDocs/blob/master/XAMLFrameworkComparison.md

Last Updated 27 July 2023 | License CC BY-SA 4.0

# XAML Framework Comparison

XAML-based UI frameworks have evolved considerably over the years. This is best illustrated in the below graphic. The bulk of these frameworks: Avalonia UI, the Uno Platform and .NET MAUI support cross-platform applications. In fact, except for Avalonia UI, the need for cross-platform XAML is the main driving force behind their development. If Microsoft stepped in earlier and created a true Flutter-like cross-platform UI framework years ago we likely never would have ended up with all of these options. This is both good and bad: Good that we now have lots of options to choose from and bad that all have a different object model and dialect of XAML.

While following the various .NET UI frameworks, the same question was being asked: Which XAML UI framework should be used to write apps? This is a valid and important question. For there to be so many options today indicates there is no clear solution. That said, on a per-app basis, the answer to the question is easier as each of the frameworks have clear strengths and weaknesses which can be compared with a specific application's needs. By outlining the strengths and weaknesses in the main XAML-based UI frameworks, this document aims to help companies and developers answer the question:

 > Which XAML framework should I use for my cross-platform app?

<p align="center">
<img src="https://github.com/robloo/PublicDocs/blob/master/XAMLFrameworkEvolution.png?raw=true" width="800px">
</p>

At a very high level the difference in the three cross-platform XAML frameworks can be described in terms of architecture. All frameworks are based on the same .NET (formerly Mono) tooling. Xamarin's contributions to .NET allowing all of these frameworks to exist must not be overlooked. Additionally, with .NET 6+ all of these frameworks are using the same runtime and core libraries on every platform.

 * [**Avalonia UI**](https://github.com/AvaloniaUI/Avalonia) : Fully renders controls and user-interface elements itself. This is the same approach that Flutter uses.
 * [**.NET MAUI**](https://github.com/dotnet/maui) : Standardizes a set of names, properties and events and applies/links them to platform-specific native controls. Mapping to native controls is a least-common-denominator approach. If a single platform doesn't support a feature it likely won't be in MAUI for all platforms (without dropping into platform-specific code).
 * [**Uno Platform**](https://github.com/unoplatform/uno) : Uses a select few platform-specific primitives to build and render controls. For high level controls this gives nearly pixel-perfect results. This means the Uno Platform behaves like Avalonia UI or Flutter which fully render their controls; however, it also supports direct embedding of platform-specific native controls. It is a hybrid architecture.

This file has been truncated. show original

Vincent · 7월 13, 2022, 9:27오전

주관적이지만 공감이 많이 됩니다.

역시 아직은 UNO가 MAUI보다 훨씬 좋은 것으로…

nyjin · 7월 13, 2022, 9:49오전

누가 이렇게 예쁘게 정리를 ㅎㅎ 정보 감사합니다.

level120 · 7월 13, 2022, 12:13오후

Uno가 평이 좋네요 ㄷㄷ

heojaehun · 7월 19, 2022, 12:48오전

좋은 정보 감사합니다!