{"id":18382,"date":"2022-12-22T07:00:39","date_gmt":"2022-12-22T05:00:39","guid":{"rendered":"https:\/\/pasiona.com\/net-maui-the-evolution-of-xamarin-forms-2-2\/"},"modified":"2022-12-22T07:00:39","modified_gmt":"2022-12-22T05:00:39","slug":"net-maui-the-evolution-of-xamarin-forms-2-2","status":"publish","type":"post","link":"https:\/\/pasiona.com\/en\/net-maui-the-evolution-of-xamarin-forms-2-2\/","title":{"rendered":".NET MAUI – The evolution of Xamarin.Forms (2\/2)"},"content":{"rendered":"

In these Christmas dates we return, and unlike the Grinch, we come to give you our particular gift and the one we like the most: our knowledge. This time we have the second part on the new technology provided by Microsoft for Mobile development, .NET MAUI.<\/p>\n

<\/p>\n

Remind you that in the first part<\/a> we already discussed the main changes and improvements of .NET MAUI with respect to Xamarin.Forms and how Pasiona, with the technologies with which we work, we have developed great successes<\/a> for our customers. We advance you in scoop that, shortly, we will prepare an article about one of our last clients that makes us salivate, and in which you can meet a member of the team: V\u00edctor Madurga Mart\u00edn, but… We better not advance you more for the moment, and you will discover it in a few weeks!<\/p>\n

Let’s get down to business! As we promised, in this second part we will investigate a little more in the technical aspect and we will comment in depth some of the improvements offered by .NET MAUI.<\/p>\n

As we have already indicated, the improvements that MAUI gives us are many and varied, but from Pasiona we believe and support two major areas: accessibility<\/a> and usability<\/a>. For this reason, in this second article we have decided to focus on both and, as you can see, it will be the small changes that will bring great value in development.<\/p>\n

 <\/p>\n

Accessibility<\/h2>\n

 <\/p>\n

Accessibility is the main issue to be addressed. In the context of mobile applications, accessibility is essential for users with different abilities to be able to use them. For this, MAUI provides us with a large number of tools:<\/p>\n

 <\/p>\n

Semantic properties<\/h3>\n

 <\/p>\n

Semantic properties are used to define information about what text should be read aloud to the user and what the focus of accessibility is. Important to clarify the following: .NET MAUI internally is already responsible for adapting accessibility for each platform, without the need for us to do anything.<\/p>\n

 <\/p>\n

Description <\/strong><\/p>\n

\"*XAML<\/p>\n

The SemanticProperties.Description<\/strong> field represents a brief description about the control in question, in this case an image.<\/p>\n

 <\/p>\n

Track <\/strong><\/p>\n

\"XAML<\/p>\n

The SemanticProperties.Hint field is used to provide additional context to the SemanticProperties.Description<\/strong> property. <\/strong><\/p>\n

 <\/p>\n

Title levels <\/strong><\/p>\n

\"*XAML<\/p>\n

The SemanticProperties.HeadingLevel <\/strong>field helps us define the different headers within a view in our application. This functionality is most useful on platforms such as Windows, as a single header level is used on Android and iOS.<\/p>\n

 <\/p>\n

Semantic focus and screen reader<\/h3>\n

To finish with the issue of accessibility, we will comment on the main change in accessibility that .NET MAUI does provide us and that Xamarin.Forms does not. For now we are able, with respect to the code, to launch any text for the narrator to read to us. This is very convenient when, for example, we need to update the view. With this simple line of code we can warn the user:<\/p>\n

\"\u2022<\/p>\n

We can also focus any type of control with this other simple line of code:<\/p>\n

\"*<\/p>\n

Shaded<\/h2>\n

When we make accessible and usable applications, our colleagues create designs with small nuances such as shading that offers contrasts and improves the visibility of elements. Maui for these small details has also come to help us, for example, with Xamarin.Forms. If we wanted to add shading to a control such as an image, we had to look for alternative solutions, since we were not directly provided with how to do it. With .NET MAUI this problem disappears, since it provides us with an easy and simple way to do it. Here’s an example:<\/p>\n

\"*image<\/p>\n

 <\/p>\n

Adaptation to the theme of the device<\/h2>\n

With .NET MAUI we get our cross-platform application to visually adapt to the light or dark themes of our device. Even so, we may be interested in defining certain colors according to which controls and cases. Here’s an example:<\/p>\n

\"*example<\/p>\n

We have many things that we would like to continue explaining, since the improvements and novelties are many and varied. If you share with us, we will be happy to tell you!<\/p>\n

 <\/p>\n

Links\/Contributions\/Examples<\/h2>\n

 <\/p>\n

While waiting for our next text, do you want to continue browsing what .NET MAUI offers us? Here we share some links:<\/p>\n

 <\/p>\n