A shared C# and XAML app
One project targeting Android and iOS, and Windows or macOS where the business genuinely needs a desktop build too, using .NET MAUI’s single project system.
Mobile Development
One C# and XAML codebase shipped to iOS, Android, macOS and Windows, as a dedicated developer, a scoped project, recruitment support or consulting.
A business that wants one team and one codebase across phones and desktops, rather than a separate iOS team and a separate Android team, tends to hire a .NET MAUI developer in Dubai for exactly that reason. Microsoft’s own documentation describes .NET MAUI as a cross platform framework for creating native mobile and desktop apps with C# and XAML, targeting Android, iOS, macOS and Windows from a single shared codebase, so the appeal is straightforward: write the logic and much of the layout once, and let the framework compile it down to a genuinely native app on each platform rather than a web page dressed up as one.
That single codebase promise is real but not unconditional. Microsoft’s own architecture notes state plainly that building for iOS and macOS still requires a Mac, and that platform specific code and resources can be added where a screen genuinely needs to behave differently per platform. A .NET MAUI developer worth hiring in Dubai treats “single codebase” as a target to aim for, not a promise that nothing platform specific will ever be needed, and tells you honestly where a screen needs platform specific work before it becomes a surprise late in the project.
What the role builds
Real cross platform output, not a demo that only runs on one device.
One project targeting Android and iOS, and Windows or macOS where the business genuinely needs a desktop build too, using .NET MAUI’s single project system.
Native code and resources added deliberately where a screen or a device feature does not fit a shared abstraction, rather than forced into one.
Cross platform APIs for things such as the GPS, network state, secure key and value storage, and the system clipboard, wired up consistently across platforms.
Builds prepared and submitted to Apple’s App Store and Google Play, since each still has its own review process regardless of the shared codebase underneath.
Networking code against your existing or new backend, shared across platforms with proper handling for slow or failed connections.
Rebuilding and retesting against new Android, iOS and .NET MAUI releases, since each ships on its own schedule and a stale build quietly drifts out of support.
Skills that matter
Cross platform judgement, checked against Microsoft’s own documentation.
| Skill or tool | What good looks like | Why it matters |
|---|---|---|
| C# and XAML fundamentals | Comfortable in both, including data binding and .NET MAUI’s layout engine, not only one or the other | Most of a .NET MAUI app’s substance sits in these two together |
| Knowing when to go platform specific | Can point to real screens where they used platform specific code and explain why a shared control was not enough | Forcing every screen into a shared abstraction produces an app that feels wrong on both platforms |
| Currently supported .NET MAUI version | Builds against a version still inside Microsoft’s support window, aware of when the current one ages out | A version past its support window stops receiving fixes, including security ones |
| Hot reload discipline | Uses XAML and code hot reload to iterate quickly, but still tests a full rebuild before release | Hot reload sessions can mask issues that only show up in a clean build |
| Testing across platforms | Tests on real Android and iOS devices, not only the platform they personally prefer | A shared codebase can still behave differently per platform in practice |
Microsoft’s own What is .NET MAUI? page sets out how the framework compiles down differently per platform, Android apps just in time compiled at launch and iOS apps fully ahead of time compiled to native ARM code, which is a fair thing to ask a .NET MAUI developer to explain in their own words before you hire them.
Ways to work with us
A dedicated .NET MAUI developer suits a product with an ongoing roadmap across several platforms, working inside your team on a recurring basis. A scoped project suits a defined build, such as a first cross platform release or a specific new module, delivered with source code, app store submissions and a full handover. Recruitment support suits a business that wants to hire a .NET MAUI developer directly onto its own payroll, with us running the technical assessment. Consulting suits a business deciding whether .NET MAUI is the right choice at all against native development or another cross platform framework, before committing budget either way.
Assessing a candidate
Checks that expose real cross platform delivery, not just a working demo.
Live links to real Apple App Store and Google Play listings, not only a project that runs in the simulator or emulator.
A specific screen or feature where they added platform specific code, and why the shared abstraction was not enough there.
Ask to see a real screen’s markup and its data bound view model, not a tutorial project copied from Microsoft’s own samples.
Which physical Android and iOS devices they tested on before release, and what broke on one platform but not the other.
If your project began life on Xamarin.Forms, ask them to explain the migration path honestly rather than promising a trivial swap.
Certifications
Weigh the general .NET credential for what it actually covers.
Microsoft’s own certification catalogue does not list an exam specific to .NET MAUI, so it is not something you can check when you hire a .NET MAUI developer in Dubai. Broader Microsoft Azure or .NET developer credentials touch related skills but do not test cross platform mobile work directly, so they are only a partial signal for this role.
Real apps live on both app stores, XAML and C# you can read, and a clear account of where they deliberately left the shared codebase, tell you more than a general credential. This is the better test before you hire a .NET MAUI developer in Dubai.
UAE considerations
Two areas that come up in real Dubai cross platform projects.
A shared XAML layout still needs testing for right to left Arabic on each target platform separately, since Android, iOS and Windows each apply mirroring slightly differently under the hood, so a .NET MAUI developer should verify it screen by screen rather than assume a shared layout covers every case.
If a .NET MAUI app processes customer or staff data on any of its target platforms, Federal Decree Law No. 45 of 2021, the UAE’s federal data protection law, applies to that processing regardless of which platform the data was captured on, so this is worth raising early with whoever directs the work.
This role sits in our mobile development category, part of the wider hire developers in Dubai section. If your business already runs an existing Xamarin app rather than starting fresh, our Xamarin developer page covers that migration route specifically. For a single native platform instead of a shared codebase, see our iOS developer and Android developer pages, and for a JavaScript based alternative to .NET MAUI, compare React Native developer and Ionic developer. For a full project with design and app store work included, our mobile app development service is the broader starting point.
Straight answers
Microsoft's own description is a cross platform framework for creating native mobile and desktop apps with C# and XAML, letting you develop apps that run on Android, iOS, macOS and Windows from a single shared codebase. It is the direct successor to Xamarin.Forms.
No. Microsoft describes .NET MAUI as the evolution of Xamarin.Forms, with the UI controls rebuilt from the ground up, and Xamarin's own support ended on 1 May 2024. A new cross platform .NET build should start on .NET MAUI, while an existing Xamarin app is a separate, related hire.
Usually not for the shared logic and layout, since one .NET MAUI developer works across both from a single project. Building for iOS or macOS specifically still requires a Mac, as Microsoft's own documentation notes, so plan for that in the setup regardless of who writes the code.
It compiles to native UI controls and native code on each platform, unlike a web based hybrid app running inside a browser view. Android apps are JIT compiled at launch and iOS apps are fully ahead of time compiled into native ARM code, according to Microsoft's own architecture documentation.
Each major version is serviced with monthly updates and stays supported for a defined window after its successor ships, following the Microsoft Modern Lifecycle Policy. A .NET MAUI developer should be building against a currently supported version rather than one already close to the end of that window.
Sources
Fixed price, in writing
Got it. Your quote is being written now.
In business hours you will have it within 45 minutes. Check your inbox for the confirmation.