Let's talk about the evolution of Xamarin—.NET MAUI, which was shared Tuesday, May 19, at Microsoft Build.
Hello! 😍 Let me tell you that I am super excited and that is why I wanted to come running to write my post! And as you can see, the title does not say Xamarin but .NET MAUI. 😯 Well, in this article I want to make a short summary about what was shared Tuesday, May 19, at Microsoft Build about this news!
The first thing is to be clear that it is .NET Multi-platform App UI (MAUI).
MAUI is the evolution of Xamarin: it is a framework that will allow us to develop native user interfaces for mobile and desktop with the objective of developing native multi-platform user interfaces, on a unique project with shared code, using .NET.
We will see some key points such as improvement in performance, new options enabled like the Model-View-Update (MVU) pattern and facilities in the extension of controls.
NO and absolutely NO😎 . The other good news is that we can transfer our Xamarin Forms knowledge such as our handling in XAML, the implementation of MVVM to the projects that we build in MAUI.
Similarly, Xamarin Forms will continue its evolution and improvements in the same release cycle, which is every six weeks until the release of MAUI with .NET 6, after which it will receive support for a year.
➖ Xamarin will NOT change names. MAUI is a new framework.
➖ You should NOT worry about the applications you have in Xamarin, as of the information presented at Microsoft Build. In my opinion, the learning curve will be quite simple, and in addition they spoke about some tools to streamline the migration process. So relax! 😎
➖ We can continue using Xamarin without problems. Quite the opposite in fact, we will have the joy of having the knowledge of a new platform even without knowing it, just from acquiring more Xamarin skills. 😎
➖ This goes as a tip: Although we will be able to transfer our knowledge of Xamarin, MAUI is a new framework so it is important to keep abreast of the news about MAUI, catch up when releases come out and practice with them, so we will stay in step with the platform as it evolves.
The more time I spent watching the Microsoft Build video, the more excited I became!
Let’s look at the differences divided by classification. Highlighted in red are the changes that seem most relevant to me and some of my favorites.
In which Visual Studio will it be available?
As we already know in Xamarin.Forms, the base structure is that we have a shared project and an additional project for each platform contained in the project.
This time we will have our most simplified project, allowing us to work only on a single project.
Translating to configuration, it would be something like this:
This is super nice! Now from the single project we can see all our devices or emulators in the same column.
This amazed me! 😍😍 Just by adding our shared resources, the tool will manage the necessary images for each platform!
You no longer need to do the image conversions for each platform and dimension. (For example in Android we have the MDPI, XHDPI, among others) and in iOS we have the @ 2 and @ 3. We will no longer have to worry about this. Time saved!
When we need to add code for a specific platform, we can do it in a much easier way, within that specific platform under the broader Platforms!
Simplified architecture in the implementation of Renderers.
Animation improvements. (For example: Its compatibility with multi-window.)
Dependency management aligned to Microsoft experience. (Same as ASP.NET Core.)
More and better tools for UI customization.
Leomaris Reyes is a Software Engineer from the Dominican Republic, with more than 5 years of experience. A Xamarin Certified Mobile Developer, she is also the founder of Stemelle, an entity that works with software developers, training and mentoring with a main goal of including women in Tech. Leomaris really loves learning new things! 💚💕 You can follow her: Twitter, LinkedIn , AskXammy and Medium.
Subscribe to be the first to get our expert-written articles and tutorials for developers!