Interested in a private company training? Request it here.
If you have all the time and money in the world, you can build an Android app and an iOS app and maybe a Windows app in their native development environment. But what if you don't have all the time in the world? How can you write an app that works on Windows, Android, iOS, MacOS and Tizen? This is where MAUI comes in.
XAML is the UI-language important for developers using the Microsoft developer stack. This module teaches students how to use the XAML language for building desktop and mobile applications, focusing on .NET MAUI.
This module gives you an overview of what kinds of controls are available and how to compose them together.
Modern hardware becomes more and more diverse: big screens, double screens, high resolutions, low resolutions, .... This does require some special up-front design. In this module, students will learn about the different controls to keep a nice UI on all devices.
How to reuse objects like colors, sizes, etc. in your application? XAML has reuse built in. In this module, students will learn how to reuse objects for their applications.
How do you apply a style to your whole application? XAML makes this easy with styles and templates. In this module, students will learn how to quickly customize their whole application with styles and templates.
In many cases, some data needs to be displayed to the user. Changes in data need to be validated and captured efficiently. In this module, students will learn how to use data binding to accomplish this.
Multiple screen-size, portrait-mode, landscape-mode. How do we make a screen that looks good, and which adapts when you turn your screen? You will learn all about it in this chapter.
An application with only one screen? It happens, but most application have multiple screens. How do you jump between screens? How do you pass information between screens?
The fact remains that you are developing for different platforms with different possibilities and a lot of differences. How can you deal with that?
.NET MAUI already contains functionalities that help you overcome the differences on the different platforms. Some functionalities normally need to be implemented multiple times against the different platforms. In this chapter we will see a whole bunch of functionalities covered for you.
Applications start and stop constantly. Sometimes you need to save some state for fetching again later. We'll see how to do that here.
An application that downloads data to show you, every time you open it. How slow would that be? And what do you do with the entered data when you are offline? Storing data on the device itself might help you in those scenarios.
How to talk to webservices for getting and sending data? You will learn all about it in this chapter.
User input needs to be validated. Are all required properties provided? Do the values match the format? In this chapter, you will see several options for validation.
MVVM is a design pattern which is immensely popular with technologies relying on declarative databinding, like XAML.
Everybody hates those constant on-screen notifications. Learn how to be annoying in this module!
Creating a mobile app is seldom creating one app. It's creating one app per platform. Learning different platforms is time consuming. MAUI allows us to do this in a much more efficient way. One language to rule them all: C#, while staying true to the platform. And only one UI paradigm to learn, in which we create the UI only once using XAML. MAUI, which evolved from Xamarin Forms, is based upon .NET. By combining reusable C# code and MAUI UI, MAUI is able to create cross-platform native apps with all the features and power of the native platforms.
Participants of this course need to have a good understanding of C# and a notion of mobile app development.