Xamarin app development services
Xamarin apps are still running in plenty of organisations, particularly where .NET is the corporate standard. We maintain them, and we plan the move to .NET MAUI when that becomes the right call.
Where we use Xamarin
Xamarin is part of the stack on this service. Each page covers how we work, what you get and what it costs to start.
Xamarin in practice
Xamarin let .NET teams write mobile apps in C# with native UI underneath, and a lot of enterprise software still runs on it. Microsoft has since moved that story to .NET MAUI, and Xamarin support has ended — which makes every remaining Xamarin app a maintenance question with a deadline attached.
That does not mean urgency for its own sake. A working Xamarin app can be kept compliant with store and SDK requirements while a migration is planned properly. What it does mean is that the plan should exist, with a real assessment of how much custom renderer code has to be rewritten, rather than being discovered when a store deadline forces the issue.
What we build with Xamarin
Keeping shipped apps compliant with current iOS and Android store requirements and SDK levels.
Assessing what ports cleanly, what needs rewriting, and what the sequence should be.
Mobile front ends for organisations whose backend and identity estate is already .NET.
Is Xamarin right for you?
Ask usA good fit when
- You have an existing Xamarin app that needs to stay compliant and working
- The organisation is .NET throughout and mobile should share that estate
- You need a realistic assessment before committing to a MAUI migration
- Business logic is already shared with a .NET backend
Probably not when
- Any new project — .NET MAUI is the supported successor
- A consumer product where interface polish is the differentiator
- Teams with no .NET presence at all
- Products needing the newest platform APIs quickly
What we run alongside Xamarin
The rest of the setup, and why each piece is there. We keep this list short on purpose — every dependency is something someone has to maintain.
- .NET MAUI
- Where the platform went. The migration target for anything with a future.
- MVVM with CommunityToolkit
- The structural pattern both frameworks assume, and what makes a migration tractable.
- Azure App Center or alternatives
- Build, distribute and crash reporting — note App Center’s own retirement timeline.
- Shared .NET libraries
- Models and business rules genuinely reused with your backend rather than reimplemented.
Why Xamarin
Let’s talkShares code with .NET backends
Models and business rules can be genuinely shared with an existing .NET server estate.
Native UI underneath
Xamarin renders platform controls, so existing apps do not look like wrapped web pages.
A supported migration path exists
.NET MAUI is the successor, so an existing investment has somewhere defined to go.
What we get called in to fix
Get a second opinionStore compliance deadlines
Apps failing new SDK or privacy requirements. Usually fixable in place, which buys time for a proper migration.
Custom renderers everywhere
The single biggest driver of migration cost. Worth inventorying before anyone estimates the work.
Dependencies that no longer build
Abandoned NuGet packages blocking the toolchain. Replacing them is often step one of any plan.
No migration plan at all
The most common state we find. A written assessment turns an open-ended risk into a scoped project.
Xamarin or the alternative
The comparisons we are actually asked to make, answered the way we would answer them on a call.
Not a choice — MAUI is the supported path. The only question is sequence and timing.
MAUI keeps you in .NET and shares code with a .NET backend. React Native has a larger community and talent pool. Existing .NET estate usually settles it.
Migrate when the architecture is sound and renderers are few. Rebuild when the app is old enough that its assumptions no longer match the product.
Android
Angular
CSS3
Flutter
HTML5
Ionic
Kotlin
React
SwiftGot an idea? Let’s make it real.
Tell us the short version
This could be the first step towards a new and successful collaboration. A one-line idea and a finished spec are both fine — tell us the problem, the deadline you’re working to and what’s in your way.
Keep looking
Frequently asked questions
No. New .NET mobile work should target .NET MAUI; Xamarin support has ended.
Yes — store compliance, SDK updates and bug fixes, while we plan the migration properly.
It varies with how much custom renderer code exists. We scope it with an assessment before anyone commits to a date.
No — support has ended. Apps continue to run, but new SDK and store requirements will eventually force the move to MAUI.
By inventorying custom renderers, platform-specific code and dependencies. That inventory, not the app’s page count, is what determines the effort.