Mobile & Cross-Platform
Production .NET MAUI, iOS and Android apps and Xamarin → MAUI conversions — including the background, offline and lifecycle work most teams get wrong. We work with the Microsoft .NET MAUI team, and have since MAUI started.
Mobile & IoT
Mobile and connected devices, from the people who wrote the libraries
The Shiny libraries — Bluetooth, background jobs, push, location and sync for .NET — have passed 40 million downloads, and they are in the project file of apps you have heard of. We wrote them, we maintain them, and we work with the Microsoft .NET MAUI team. When your app has to work on real devices in the field, that is the depth you are hiring.
You are probably here because
- Your Xamarin app is out of support and the port to .NET MAUI keeps stalling on dependencies.
- Background work, Bluetooth or push behaves in the demo and fails in the field.
- You have hardware and need an app that talks to it reliably on both platforms.
- Your MAUI app is slow to start or crashes in ways you cannot reproduce.
What we build
The device side of the business, built on a foundation already in production.
IoT & Bluetooth
BLE central and peripheral, device fleets and hardware integration. We wrote the libraries the industry uses for this.
Fleet & Field Operations
Location tracking, geofencing and telematics for vehicles and crews working where connectivity is not guaranteed.
Wearables & In-Car
Apple Watch, Wear OS, CarPlay and Android Auto apps that extend your mobile product to the wrist and the dashboard — designed for a glance or a voice command, not a shrunken phone screen. The phone-to-watch link runs on a library we wrote.
The return, in plain arithmetic
A budget buys engineering months. The question is what those months are spent on. On a connected product — anything with a device, a background process or an offline story — a large share of the first year goes into infrastructure that has no customer-visible value and that thousands of teams have written before.
Foundation & plumbingYour product
Typical build
With us
Illustrative proportions — the exact split depends on the project. What doesn't change is which side of the line you're paying an engineering team to rebuild.
Sooner
Revenue and feedback arrive earlier, because the schedule doesn't open with a quarter of groundwork.
Safer
The riskiest subsystems — background work, sync, device connectivity — are proven in production before your project starts.
Cheaper to keep
Less code you own outright is less to patch, port and staff for every year after handover.
The corner most projects sacrifice is one we already paid for, in the open, over 25 years — and it comes with the engagement. What that buys you is simple: more of the year goes into the product you set out to build, and less of it into getting to the starting line.
Fixed-scope entry offers
A first step a manager can approve
Every engagement can start with one of these. Each has a name and a scope written down before we start, so the first decision is a small one — and you see how we work before committing to anything larger.
.NET MAUI Health Check
For apps already on .NET MAUI — startup time, crashes that only reproduce on real devices, and background work that stopped firing after an OS update.
What is included
- Startup, memory and rendering profiled on real devices
- Crash and ANR reports triaged to root cause
- Background, push and lifecycle behaviour checked
- Upgrade path to the next .NET release
You walk away with
A ranked list of fixes, the worst of them diagnosed down to the line of code.
Xamarin Dependency Audit
Every plugin and platform dependency in your Xamarin app mapped to what replaces it in .NET MAUI — the step that stalls most ports.
What is included
- Every NuGet package and platform binding inventoried
- Replacement for each one, already in production elsewhere
- What has no equivalent, and what should not survive the move
- Phased, costed migration plan
You walk away with
A migration plan built on a lookup rather than a research phase — and a real estimate.
Bluetooth & IoT Proof of Concept
Your hardware talking to a real app on iOS and Android — scanning, connecting, reconnecting and syncing in the background, on devices, not a simulator.
What is included
- BLE connection, GATT and reconnect behaviour on your device
- Background operation within each OS’s rules
- Data synced to a cloud endpoint
- Findings on the firmware and protocol, if they need changes
You walk away with
Proof the hard part works on real phones, and a costed path to the production app.
Every offer is quoted as a fixed price once we have seen the scope — and a fixed price stays fixed: if it takes us longer, that is our problem, not yours.
Questions buyers ask
How long does a Xamarin to .NET MAUI migration take?
The UI conversion is rarely what decides it — the dependency list is. The two-week dependency audit maps every plugin to its replacement and turns that into a phased estimate.
Do we have to use the Shiny libraries?
No. It usually makes sense, because they are open source, already in production and maintained by the people doing the work. You are never locked into a private shim only the contractor understands.
Can you work with our hardware team or firmware vendor?
Yes. Most Bluetooth problems are found at the boundary between the app and the firmware, and we are used to working across it — including telling a vendor what needs to change on their side.
Do you build native Swift and Kotlin apps?
Our depth is .NET MAUI and .NET for iOS and Android, including the native platform code underneath them. If a native app is the right call for your product, we will tell you.
Building something that has to work in the field?
Tell us about the app, the devices and where they are used. We will tell you where it usually goes wrong — and how we would avoid it.