Xamarin support has ended
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.
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.
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.
Project structure, dependency injection and the build pipeline move first, so a MAUI app compiles before any screen is ported.
We port screens and flows in order of risk rather than menu order, so the hardest parts surface early instead of at the end.
Tested on real devices, per platform, since this is exactly where migrations that looked finished usually turn out not to be.
Signing, provisioning profiles and the store submission itself, handled the same way for both the App Store and Google Play.
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.
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.

Everything below is checkable before you talk to us.
Two libraries, each shipped for Xamarin and rebuilt for .NET MAUI, with 690,000+ combined NuGet downloads and 750+ GitHub stars.
A verified Clutch review highlights a completed Xamarin.Forms to .NET MAUI migration, successfully published to both app stores.
Send the .sln or dependency list and we return an inventory of packages, renderers and platform services. No estimate before that.
We’ve migrated projects across different industries, including Farmashop in m-commerce and PowerPlus in logistics, across iOS and Android.
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.
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.
No. Microsoft ended support for Xamarin on May 1, 2024. Existing apps keep running but stop receiving fixes, while app stores keep raising minimum SDK levels. .NET MAUI is the official continuation: same language, same business logic, a different UI layer.
No. In a Xamarin.Forms app the business logic, models and data layer port with few changes. The work concentrates in the UI layer and in third-party dependencies.
They get rewritten as handlers. .NET MAUI replaced the renderer architecture, so there is no automatic conversion and each one is ported by hand. The renderer count is the largest single driver of effort.
Each one gets a decision: replace it with a maintained equivalent, fork and update it, or reimplement the part you actually use. The audit produces that list before any code is written.
Yes. The Xamarin app stays releasable while the .NET MAUI version is built alongside it, which matters when you have store commitments or a fixed release cadence.
No. A migration keeps your current UI and IA one-for-one; a redesign is optional and can run as a separate, later phase if you want one.
It is the same app and the same store listing; you ship a new version. Bundle identifiers, signing certificates and store presence stay yours.
The current long-term support release. .NET MAUI is also moving from the Mono runtime to CoreCLR on Android, which changes startup performance. We wrote about what that means in the blog.
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.
During this phase, we conduct a comprehensive project review and provide estimations for the project's scope, timeline and required resources.
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.