Skip to content
DT Nova
Services

.NET mobile app development: .NET MAUI apps and Xamarin upgrades

.NET mobile app development lets a company that already runs on C# and Microsoft's stack build its iPhone and Android apps in the same language, with the same libraries and the same people. We build new apps with .NET MAUI, upgrade Xamarin apps that can no longer publish updates, and take both through App Store and Google Play review. The code sits in your repository and the apps are published under your company's own accounts.

  • You see the result before it goes live
  • Fixed price for the agreed scope, in writing before work starts
  • Source code, domain and accounts in your company's name

Request a quote

Who .NET for mobile fits

The strongest reason to choose .NET is what you already have. If your backend is ASP.NET, your business rules live in C# libraries, and your team knows Visual Studio and NuGet, a mobile app in .NET reuses all of it: the same data models, the same validation, the same authentication code, and people who can read every line. That reuse matters more over five years of maintenance than any difference between frameworks in a demo.

.NET is also the natural choice when the same app needs a Windows version for staff at desks next to the mobile version for staff in the field, which is common in field service, logistics, inspections and healthcare administration. The same .NET MAUI project builds for Android, iOS, Mac Catalyst and Windows.

It is a weaker fit when nothing in the company is .NET. In that case Flutter or React Native usually has the larger community and more third-party packages, and our cross-platform app development page explains how we choose. Our guide to mobile app development frameworks compares them all, with their current versions.

The options inside .NET

OptionWhat is sharedFits when
.NET MAUI with XAMLInterface, logic and data across Android, iOS, Mac and WindowsBusiness apps with forms, lists, maps and offline data; teams used to XAML from WPF or Xamarin.Forms
.NET MAUI Blazor HybridRazor components shared with a Blazor web app, inside a native appA Blazor web app already exists and the mobile app shows much the same screens
.NET for iOS and .NET for AndroidLogic and data in C#; each platform's interface built with its own APIsApps that need a fully native interface, or Xamarin.iOS and Xamarin.Android apps being upgraded
Native Swift and Kotlin partsCalled from the .NET app through bindingsWidgets, watch apps and other features that .NET does not reach directly

Most of our .NET apps are .NET MAUI with a small amount of platform code for the features each store expects, such as notifications, sign in with Apple, background work or in-app purchases. The scope names those parts so you know where the two platforms differ.

Xamarin apps: why they have to move now

Many companies still run apps written in Xamarin.Forms, Xamarin.iOS or Xamarin.Android. Microsoft's Xamarin support policy states that Xamarin support ended on 1 May 2024 for all Xamarin SDKs including Xamarin.Forms, and that Android API 34 and Xcode 15 SDKs (iOS and iPadOS 17, macOS 14) are the final versions Xamarin targets, with no new APIs planned. The stores have moved past those versions:

(All three pages read on 11 November 2026.) In practice, an app still built with Xamarin cannot publish an update to either store, not even a security fix, and on Google Play it gradually disappears from new users' devices. The app keeps running for people who have it, until an operating system change breaks something nobody can fix. If your company has a Xamarin app, the upgrade is no longer a modernisation project; it is the only way to keep the app in the stores.

How a Xamarin upgrade works

An upgrade is usually much less than a rewrite. Microsoft's guide to upgrading from Xamarin to .NET (read 11 November 2026) states that all projects need to become SDK-style, that projects do not need to be rewritten, and that multi-project solutions do not need to become a single multi-targeted project. It lists Xamarin.Android, Xamarin.iOS, Xamarin.Mac and Xamarin.Forms among the project types that can be upgraded, and two that cannot: OpenGL on iOS, because OpenTK is not available, and Xamarin.watchOS, where the recommendation is to bundle Swift extensions with the .NET for iOS app.

The work that takes time is around the code rather than in it:

  1. Inventory. Every project, NuGet package, custom renderer, effect and platform-specific file, with a note on whether a current .NET version of each dependency exists.
  2. Dependencies. Packages that were never updated for .NET are replaced, and Xamarin.Forms custom renderers are moved to .NET MAUI handlers where needed.
  3. Project upgrade. Projects are converted to SDK-style and moved to the current supported .NET version, then built for each platform.
  4. Store requirements. The app is brought up to the current Xcode and Android target levels, with the permissions, privacy details and background rules those versions ask for.
  5. Testing on real devices. The upgraded app is tested against the old one, screen by screen, on current and older iPhones and Android phones, before it goes out as an update to existing users.

Your users keep the same app: it is published as an update under the same store listing, so ratings, reviews and installs stay where they are.

Keeping a .NET app supported

A .NET mobile app needs a planned upgrade every year. Microsoft's .NET MAUI support policy (last updated 10 November 2026, read 11 November 2026) explains that .NET MAUI is released with each major .NET version, and that a major version receives support for a minimum of six months after its successor ships. .NET MAUI 11 was released on 10 November 2026 and is supported until 9 May 2028; .NET MAUI 10 is supported until 11 May 2027; .NET MAUI 9 went out of support on 12 May 2026. Servicing updates ship monthly, on the second Tuesday, together with the rest of .NET, and technical support from Microsoft requires the latest servicing level.

So the maintenance plan for a .NET app has two rhythms: monthly servicing updates, and a yearly move to the next major version within six months of its release, timed with the stores' own yearly requirements. Our mobile app maintenance covers both, and the upgrade dates are written into the plan so they never come as a surprise.

What you get

How the project runs

  1. Brief and code review. For an existing app, we read the code and the dependency list first; for a new app, we map the screens and the systems it talks to.
  2. Scope and fixed price in writing. One document with what is included, the store requirements it meets and the upgrade dates ahead.
  3. Build in short rounds. A test build on your phones every round, through TestFlight and Google Play testing tracks.
  4. Release. Store review, launch or update, and monitoring of crashes and reviews in the first weeks.

For apps in other technologies, see mobile app development; for apps for staff in larger organisations, see enterprise mobile app development; for Windows and Mac software, see desktop app development.

You own it

As a standard term, your company owns the code, the store listings, the signing keys and the build pipeline. The repository is yours from the first commit, and nothing runs only on our machines. See prices.

Questions we get

What is .NET mobile app development?

Building iPhone and Android apps in C# with Microsoft's .NET. Today that means .NET MAUI, which shares the interface and logic across platforms, or .NET for iOS and .NET for Android, which use the platforms' own interface APIs from C#. Both replaced Xamarin, whose support ended on 1 May 2024.

Is Xamarin still supported?

No. Microsoft's Xamarin support policy states that support ended on 1 May 2024 for all Xamarin SDKs including Xamarin.Forms, and that Android API 34 and Xcode 15 are the final versions Xamarin targets. Apple and Google Play have since raised their requirements beyond those versions, so a Xamarin app cannot keep publishing updates without an upgrade.

Do we have to rewrite a Xamarin app to move it to .NET MAUI?

Usually not. Microsoft's upgrade guide states that projects do not need to be rewritten: they need to become SDK-style projects, and their dependencies must move to current .NET. The work is in the dependencies, custom renderers, platform code and testing, and a few project types, such as Xamarin.watchOS, have no direct upgrade path.

How long is a .NET MAUI version supported?

According to Microsoft's .NET MAUI support policy, a major version receives support for at least six months after its successor ships. .NET MAUI 11 was released on 10 November 2026 and .NET MAUI 10 is supported until 11 May 2027, so apps need a planned upgrade about once a year.

When is .NET MAUI the right choice, and when not?

It fits best when your company already works in C# and .NET, with a backend, libraries or a team you want to reuse, or when the same app also needs a Windows version. When there is no .NET in the company, Flutter or React Native often have a larger pool of people and packages, and we will say so in the scope.

Who owns the app and the code?

Your company. The code sits in your own repository, the apps are published under your own Apple and Google accounts, and the build pipeline runs in your account. You can keep us for maintenance or hand the app to your own .NET team.

Get a written quote

Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.

See every price · Contact details

Request a quote