Pre loader

Xamarin support has ended

Xamarin to .NET MAUI migration!

Microsoft ended Xamarin support on May 1, 2024. We migrate Xamarin.Forms apps to .NET MAUI, audit first, then a staged port that keeps your app releasable the whole way. We also maintain four open-source .NET MAUI libraries, so when a control misbehaves mid-migration we are usually reading our own code.

Xamarin
.NET MAUI
.NET MAUI
Why migrate

Benefits behind migration!

Existing Xamarin apps keep running, but they stop receiving fixes while app stores keep raising the minimum SDK levels every release. .NET MAUI is the official continuation: same C#, same business logic, a different UI layer.

Migration icon

Back on a supported track.

Xamarin support ended May 1, 2024. .NET MAUI on .NET 10 LTS is supported until Nov 2028, restoring security updates and years of support.

Performance icon

A faster runtime.

.NET 11 will move .NET MAUI from Mono to CoreCLR, the same engine behind ASP.NET Core. Our early testing ahead of GA shows real performance improvements.

Blazor icon

The full .NET ecosystem.

One codebase shares models and business logic with your .NET backend. Blazor Hybrid even reuses existing web components inside the app.

Freedom & responsibility

Your app keeps shipping.

The Xamarin app stays releasable while we build the .NET MAUI version alongside it, the same approach behind every migration we’ve run.

Our process

How we run a migration.

Five stages, AI agents doing the repetitive parts. The app stays runnable at every one of them.

01

Audit.

Our own agents scan your .sln and .csproj files fast, producing a full inventory of dependencies, renderers and platform services, then we verify what actually matters.

02

Foundation.

Project structure, dependency injection and the build pipeline move first, so a MAUI app compiles before any screen is ported.

03

Screen by screen.

We port screens and flows in order of risk rather than menu order, so the hardest parts surface early instead of at the end.

04

Behaviour and testing.

Tested on real devices, per platform, since this is exactly where migrations that looked finished usually turn out not to be.

05

Store release.

Signing, provisioning profiles and the store submission itself, handled the same way for both the App Store and Google Play.

Migration case

A Xamarin app migrated to .NET MAUI, live in both app stores.

Farmashop is one of Uruguay's largest pharmacy chains. Their app runs Magento sync, in-app payments, geolocated stock and push campaigns on iOS and Android, all originally built on Xamarin and now on .NET MAUI.

From the pharmacy to your couch: one click away.

Farmashop

Retail
iOS
Android

Through our m-commerce app, we created a new sales channel for a well-known drugstore chain that allows customers to purchase pharmaceutical products at any time, location and device, while providing a mobile-optimized user experience. Our app made it easier for our client to reach customers who prefer the convenience of mobile shopping, resulting in increased sales and customer satisfaction.

View project

Why migrate with us?

Everything below is checkable before you talk to us.

Migration icon

We maintain the libraries.

Two libraries, each shipped for Xamarin and rebuilt for .NET MAUI, with 690,000+ combined NuGet downloads and 750+ GitHub stars.

Client Satisfaction

Reviews you can check.

A verified Clutch review highlights a completed Xamarin.Forms to .NET MAUI migration, successfully published to both app stores.

Time-to-market

We audit before we quote.

Send the .sln or dependency list and we return an inventory of packages, renderers and platform services. No estimate before that.

Xamarin icon

Migrated apps.

We’ve migrated projects across different industries, including Farmashop in m-commerce and PowerPlus in logistics, across iOS and Android.

Teamwork

We work in your hours.

Uruguay is UTC−3, a full working-day overlap with Eastern and Central time across the US and Canada, so reviews and standups happen the same day.

Freedom & responsibility

No stake in the answer.

We also build in Flutter and Uno Platform. When we say migrate rather than rewrite, it isn't because .NET MAUI is the only thing we sell.

FAQs

Frequently asked questions.

Is Xamarin still supported?
Do we have to rewrite our app?
What happens to our custom renderers?
What about NuGet packages that were never updated for .NET MAUI?
Can we keep shipping the Xamarin app while the migration runs?
Do we have to redesign the UI at the same time?
Will the app need to be published again?
Which .NET version should we target?

What’s next?

1. Reach out

Send us the .sln or the dependency list with a brief summary of your requirements, and we respond in under 4 hours. If necessary, we will sign an NDA first.

2. It’s our turn…

During this phase, we conduct a comprehensive project review and provide estimations for the project's scope, timeline and required resources.

3. Get your proposal

We send you a detailed proposal outlining the project's scope, deliverables, investment, and timeline looking forward to being part of this transition with you.