Mobile App Development

Cross-platform mobile and desktop applications on C# .NET 10 with MAUI — one shared codebase, four platforms (iOS, Android, Windows, macOS), three storefronts (Apple App Store, Google Play, Microsoft Store), submitted and shepherded by the same engineer who built the app. One language, one toolchain, one staffing plan.

The honest tradeoff: MAUI is not the right answer for a consumer-grade UX-heavy app where platform-native polish is the differentiator. It is the right answer for enterprise, regulated, Microsoft-shop, and B2B field-force buyers — anywhere the staffing plan, the parity across platforms, and the long Microsoft service horizon matter more than millimeter-perfect platform-native gestures. I will say so on day one. For an Instagram-class consumer app, hire Swift and Kotlin teams. For a field-inspection app that runs on iPads, Android tablets, and Windows handhelds, MAUI collapses the staffing plan by two thirds.

I do not claim AAA-game-quality 3D rendering. I do not promise App Store approval — that is Apple's call, not mine. What I do is build the app, ship it through all three storefronts, manage the review cycle, respond to reviewer feedback, and run the post-launch update cadence. The same engineer who wrote the MAUI handler also responds to the App Review reply at 11pm.

James Henderson is a computer scientist with 25-plus years as an architect, engineer, and application designer. The .NET 10 / MAUI stack on this page maps to the kinds of buyers he engineers for — enterprise, regulated, Microsoft-shop, and B2B field-force organizations that need cross-platform clients without staffing three native teams. He pairs disciplined engineering with current AI tooling — Claude Code, Codex, and a working judgment about when to trust them — to ship products faster and at higher quality than traditional staffing allows. There is no offshore team behind the page. The principal carries the work end to end: scope, build, deploy, store submission, support. A B.S. in Computer Science from the University of Houston and service in the U.S. Army ground the tone — evidence over assertion, plans before code, verification before delivery. The Apple App Review reply at 11pm comes from the same person who wrote the MAUI handler.

Why MAUI on .NET 10, and where it is the wrong answer

MAUI on .NET 10 collapses the staffing plan. One language (C#), one toolchain, four target platforms (iOS, Android, Windows, macOS). Cheaper to staff, easier to keep feature parity, and on a long Microsoft service horizon for regulated buyers planning multi-year application lifecycles. Compared to native (three teams, three release trains) or React Native (a JavaScript bridge, a different runtime culture, a different identity story), MAUI is the path of least friction for enterprise, regulated, Microsoft-shop, and B2B field-force buyers.

I will not recommend MAUI for a consumer-grade UX-heavy app where platform-native polish is the differentiator. If the buyer's competitive moat is gesture-perfect interaction or AAA-class 3D rendering, MAUI is not the right answer and I will say so. The honesty is structural: scope per buyer, not per ideology.

What the four breakdown services cover

Cross-platform app design and architecture

The architecture, UX, and platform-strategy decisions made before the first line of MAUI code — so the build does not get refactored in month three. UX across phone, tablet, and desktop form factors; MVVM with dependency injection, messaging, and persistence; theming, accessibility, internationalization, platform-handler surface.

C# / .NET MAUI implementation

The actual build — shared business logic, view models, and platform-agnostic services; per-platform handlers for camera, geolocation, file system, biometrics; offline-first data layer with conflict resolution; test coverage with the .NET test runner.

Apple App Store submission and lifecycle

Apple Developer Program enrollment, provisioning and certificates, App Store Connect listing, TestFlight beta, App Review submission and response, post-launch release cadence. The unfamiliar storefront for most Microsoft-shop buyers.

Google Play and Microsoft Store submission

Google Play app signing, internal / closed / open testing tracks, content rating, data-safety form. Microsoft Store partner center enrollment, package signing, certification submission. Update cadence and rollback procedures for both stores.

• The three storefronts I submit to: Apple App Store (iOS, macOS), Google Play (Android), Microsoft Store (Windows). Named explicitly so there is no ambiguity about what "ship to the stores" means.
• The four platforms one codebase reaches: iOS, Android, Windows, macOS. Parity is a build configuration, not a separate native team.
• The cloud side, where the buyer needs it: ASP.NET Core on .NET 10, OIDC / JWT auth, OpenAPI documents, optional gRPC, Azure App Service or Container Apps deployment.
• What I do not promise: App Store approval (Apple's call), AAA-class 3D rendering (the wrong stack), Instagram-class consumer polish (hire native teams).

The principal carrying the work is described on the about page; patterns from prior .NET engagements live in the research notes. To scope a MAUI build or a Xamarin-to-MAUI migration, get in touch.

What I ship

• Cross-platform app design and architecture. UX across phone, tablet, and desktop; MVVM patterns; dependency injection; theming, accessibility, internationalization mapped before the first sprint.
• .NET 10 MAUI implementation. Shared business logic, view models, and services; per-platform handlers; offline-first data layer with conflict resolution; CI test coverage.
• Apple App Store submission and lifecycle. Developer Program enrollment, provisioning, TestFlight, App Review submission and response, post-launch release cadence.
• Google Play and Microsoft Store submission. Play app signing, testing tracks, content rating; Microsoft Store partner center, package signing, certification.
• ASP.NET Core backends where needed. Web API on .NET 10, OIDC / JWT auth, OpenAPI documents, optional gRPC.
• Azure-native deployment. App Service, Container Apps, Key Vault, Application Insights, infrastructure-as-code a second engineer can read.
• Xamarin-to-MAUI migration. SDK conversion, handler and renderer rewrites, NuGet trim, CI pipeline updates.

Engagement model

Discovery runs two weeks: form-factor scoping, architectural decisions, platform-handler surface, storefront-readiness review, and a written plan with milestones. Implementation runs in two-week sprints with a working build on every platform at the end of each, a Git history you can read, and tests that actually run in CI. Storefront submission runs in parallel with the final sprint — provisioning, signing, listing copy, screenshots, and review submission to Apple, Google, and Microsoft. Handover includes the running application on every platform, the test suite, the IaC, the runbook, and a 30-day support window after launch covering review responses and post-launch update cadence. To scope a build, get in touch.