Develop cross-platform applications with Xamarin Forms on Windows on Arm
Introduction
Create an application using Xamarin Forms
Implement logic with Model View ViewModel
Next Steps
Develop cross-platform applications with Xamarin Forms on Windows on Arm
Who is this for?
This learning path is for developers who want to learn how to create cross-platform applications and leverage performance improvements on Arm64.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Create and build an Xamarin Forms application
- Measure code execution performance uplift on Arm64
- Learn how to use the Model-View-ViewModel (MVVM) architectural pattern
Prerequisites
Before starting, you will need the following:
- A Windows on Arm computer such as the Lenovo Thinkpad X13s running Windows 11 or a a Windows on Arm virtual machine .
- Visual Studio 2022 with .NET desktop development and Universal Windows Platform development installed.
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll create a Xamarin Forms application on Windows on Arm using the Model-View-ViewModel (MVVM) pattern. First, you’ll add a model for XY data, organize the project in Visual Studio, and connect the view model to the main page. Then, you’ll build and run the app, and time a chosen code path to measure execution on Arm64.
Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Add it to the
Arm64.MobileApp.XamarinForms project. Create a Models folder and then add a new C# class named DataPoint2d.cs inside that folder.In
MainPage.xaml, add the view-model namespace and set ContentPage.BindingContext to the appropriate view-model class. This makes the view model available to the main page.Use Visual Studio to build the solution, then start debugging to launch the app. A successful build completes without errors and opens the app on Windows.
Select the project node (not the solution or a solution folder) in Solution Explorer. If options are still missing, make sure the project is loaded and not unavailable.
Instrument the relevant code path to record elapsed time, then run the app on the Windows on Arm system and note the results. Keep inputs and build configuration the same across runs to make comparisons meaningful.