Services
Four rungs, in the order most apps need them.
Most of the apps we are called about are in one of two states. Either a release has already been rejected and there is a date attached to the problem, or somebody has read that Xamarin support ended in May 2024 and has been asked what that means for the app the field team uses every day.
The ladder below is built for both. It is deliberately possible to stop after the first rung and take the document elsewhere.
Xamarin App Assessment
A read of the repository and the pipeline, not a questionnaire. Framework and SDK versions, custom renderers and effects, third-party controls and NuGets with no maintained successor, native bindings, platform-specific code, test coverage, and the state of build and signing. The output is a written migration plan: a sequenced work order, a keep, rewrite or retire call per screen and dependency, and the risks that could stall a release.
Store-Compliance Release Rescue
For when the deadline is closer than the migration. Targeted work to get one more compliant build out of the existing app where that is still possible, or to stand up the minimum .NET MAUI shell that satisfies current App Store and Google Play SDK and target-API requirements. Includes the build pipeline, provisioning and signing, crash and regression triage, and a submission dry run.
Store-Compliance Release Rescue
Xamarin.Forms to .NET MAUI Migration
The move itself, delivered incrementally. Project and dependency restructuring, renderers converted to handlers, shared business logic preserved and covered by characterization tests, unmaintained controls replaced, platform code moved forward, and parity verified screen by screen against the app currently in production. Each slice ends with something you could release.
Xamarin.Forms to .NET MAUI Migration
Post-Migration Maintenance and Release Engineering
Ongoing senior capacity after the move: annual OS and SDK upgrades, store policy changes, crash and performance work, dependency hygiene, CI maintenance, and pairing with your in-house .NET team.
How engagements are billed
Hourly, on a time-and-materials basis, staffed by senior US-based engineers, as project work or as staff augmentation. Scope, staffing and timeline are agreed in an initial conversation. There are no fixed-price packages and no published rates, because neither survives contact with an undocumented mobile codebase.