No cost
Free consultation
A call with the engineers who would do the work, not a salesperson. Bring the codebase or the idea and we will tell you what we think, including when the answer is to do nothing.
.NET MAUI · Current release
Cross-platform apps in .NET MAUI
One C# codebase for iOS, Android, Windows and macOS, on the current .NET release with the single-project structure, native controls and Blazor Hybrid where it earns its place.
Start with a free consultation and a written plan you keep. After that, a working build on real devices every two weeks.
How we start
Consultation, plan, then fortnightly builds
Yours to keep
A written plan
Scope, staging, risks and a cost range in writing after the call. You keep it whether or not you hire us, and it is specific enough to take to another firm.
Every 2 weeks
Two-week iterations
A working build on real devices every fortnight, not a status report. You see progress you can install and use, and you can change direction at any boundary.
Xamarin to MAUI migration
Your app still runs. That is not the same as being supported.
Microsoft ended support for Xamarin on 1 May 2024. Nothing broke that day, which is exactly why migrations get postponed. What follows is slower and harder to plan for: no security fixes, new OS releases that change behaviour you cannot patch, store requirements the framework will not meet, and packages that stop publishing updates.
Select a stage
01 / AuditCodebase and dependency audit
We read the solution and every third-party package, and check which have a MAUI release, which have a viable replacement and which are abandoned. This is what decides the estimate, so it happens before we quote rather than after.
02 / PlanStaged migration plan
A sequence with the riskiest dependency first, so unpleasant surprises land in week one rather than week nine. You get a range, not a single optimistic number.
03 / ProjectProject and startup migration
Xamarin projects become the MAUI single-project structure. Dependency injection, app startup and configuration are rebuilt on the modern host builder, and the solution compiles before any UI work starts.
04 / UIUI layer conversion
Most XAML transfers with edits. Custom renderers become handlers, and Xamarin.Forms-specific controls and effects are replaced. Where you already have Razor components, Blazor Hybrid can carry them into the app instead.
05 / NativePlatform and device code
Camera, Bluetooth, location, notifications, background work and storage rewired to current platform APIs and the permission models iOS and Android now enforce.
06 / ShipPipelines and store release
Signing, provisioning, CI/CD, TestFlight and Play Console, then the review process itself. We hand back something your team can build and release without us.
| Usually carries over | Usually needs rework |
|---|---|
| C# business logic, models and services | Custom renderers become handlers |
| XAML pages and most layouts | Xamarin.Forms-specific controls and effects |
| Unit tests and shared libraries | Dependency injection and app startup |
| API and data access code | Packages with no MAUI release |
| Most view models and bindings | Platform projects and build pipeline |
Which side of that table your codebase falls on decides the estimate. If the honest answer is that a rewrite costs less than a migration, we will say so in the plan.
MAUI development
Built for the places the signal drops
Most of our MAUI work goes to people standing up: technicians in plant rooms, inspectors on site, clinicians visiting homes. Those users abandon an app that spins on one bar of signal, so offline is a decision we make on day one rather than a feature added later.
More on sync and conflict handling in offline-first .NET MAUI apps for field teams.
New cross-platform apps
One C# codebase on the current .NET release targeting iOS, Android, Windows and macOS, using the single-project structure and native controls rather than a web view pretending to be an app.
Offline-first field apps
Local SQLite as the source of truth, a sync engine that survives a dropped connection, and honest sync state in the interface. No screen waits on the network.
Device and hardware integration
Camera, GPS, Bluetooth peripherals, barcode and NFC scanning, file capture and signatures, wired to the permissions each platform now enforces.
Back end and systems integration
ASP.NET Core APIs, Azure hosting, and connections into SharePoint, Dynamics 365 or Salesforce where the data already lives.
Blazor Hybrid where it fits
Reuse existing Razor components inside a MAUI shell when you already have a web app and want one team maintaining both.
Release and store submission
Signing, provisioning, CI/CD pipelines, TestFlight and Play Console setup, and the review process handled rather than handed back to you.
Selected work
Shipped and in the store
ComicBase
ComicBase
Cross-platform app · iOS and Android
A mobile companion for managing a comic collection, letting collectors catalogue, search and browse their library from a phone rather than at a desk. One codebase, shipped and maintained on both stores.
- .NET MAUI
- C#
- iOS
- Android
More of our work is in the portfolio.
Why us
A .NET team, not a mobile shop that also does C#
- One language on both ends
- The same engineers write the MAUI app and the ASP.NET Core API behind it. Models, validation and business rules are shared rather than reimplemented twice and drifting apart.
- We work inside running systems
- Most of our work sits in estates that cannot stop while we change them, wired into SharePoint, Dynamics 365 and Salesforce. Integration is the normal case for us, not an add-on.
- Estimates we will stand behind
- We audit before quoting and give ranges rather than a single number chosen to win the work. When the cheaper option is not hiring us, we say that on the first call.
- You can leave at a boundary
- Two-week iterations mean there is always a recent working build and a natural stopping point. No twelve-month commitment before you see the thing running on a device.
Questions
What teams ask before starting
What does the free consultation actually include?
A call with the engineers who would do the work, followed by a written plan covering scope, staging, the main risks and a cost range. It is yours to keep regardless of what you decide, and it is specific enough to take to another firm for comparison. We do this because the assessment is where most of the real thinking happens, and because it is the fastest way for both sides to find out whether the project is worth doing.
Xamarin still works. Why migrate now?
Microsoft ended support for Xamarin on 1 May 2024. Existing apps keep running, but they receive no fixes, and each new iOS and Android release raises the chance of a break you cannot patch. App stores also raise minimum SDK requirements over time, and an unsupported framework eventually cannot meet them. The cost of migrating rises the longer the codebase sits unmaintained.
How much of our Xamarin code can we keep?
For most Xamarin.Forms apps, the large majority of C# business logic, models, services and view models carries over, and much of the XAML transfers with edits. The work concentrates in custom renderers, platform-specific code, packages without a MAUI release, and the build pipeline. We give you a specific answer for your codebase in the audit rather than a percentage from a brochure.
How long does a migration take?
A small single-purpose app is usually weeks. A large app with heavy custom UI, many device integrations and abandoned dependencies is months. The dependency audit is what separates those two cases, which is why it comes before the quote. Either way you see a working build every two weeks, so the timeline is something you can watch rather than wait for.
Can you take over an app someone else built?
Yes, and it is a large part of what we do. We start by reading the code and running it, then tell you honestly whether migrating, rewriting or leaving it alone is the better commercial decision. We have advised all three.
Should we use MAUI or React Native or Flutter?
MAUI is the strongest choice when your back end and team are already .NET, because the models, validation and business rules are shared C# across the app and the API, maintained by one team. If your organisation has no .NET investment and a strong JavaScript team, that calculus changes and we will say so on the call.
Talk to us
Book the free consultation
Send the shape of it: current framework, roughly how large, what it integrates with. You get a call with the engineers who would do the work and a written plan afterwards, yours to keep either way.
Other ways to reach us
- Phone
- +1 832 838 4955
- Where we work
- United States · Australia · Pakistan
Prefer to see the wider picture first? Our custom software development service covers the back end these apps usually need.