AI changes the cross-platform decision matrix for .NET apps
Microsoft’s .NET Blog says AI coding agents have made it cheaper to try platform-specific UI for .NET apps, even though the maintenance cost has not disappeared. The post compares .NET MAUI Controls with platform UI on iOS and Android and says the new trade-off is now practical enough to measure.

- Microsoft says AI coding agents have changed the build-time cost of trying platform-specific UI in .NET app development.
- The post’s author says a second UI is now cheaper to create, but keeping it maintained still requires work and testing.
- The comparison in the post is between .NET MAUI Controls and platform UI over a shared library, with platform UI using UIKit on iOS and Android Views on Android in C#.
- The author says Android default builds traded startup speed against package size, so the best choice still depends on the app’s priorities.
Microsoft’s .NET Blog says AI coding agents have changed how developers should think about cross-platform app design. In a post published on 20 November 2026, the company argues that the old trade-off has shifted: team knowledge and capacity still matter, but AI can make it practical to build and measure a second UI before committing to it. Microsoft .NET Blog
What Microsoft says changed
The post says cross-platform decisions have always depended on a familiar set of constraints: what the team already knows, how many codebases it can support, the cost to build and maintain them, app size and performance, and the health of the surrounding ecosystem. Microsoft now adds AI coding agents to that list. According to the author, a well-configured GitHub Copilot can write UIKit or Android Views even if nobody on the team already knows those frameworks, which lowers the cost of trying platform-specific UI. Microsoft .NET Blog
The author also says that lower build cost does not remove the ongoing work. In their words, agents made a second UI cheap to build, but owning it still took work. That matters because the new decision is not just “can we build it?” but “can we afford to test, support and maintain it on each platform we own?” Microsoft .NET Blog
The comparison Microsoft measured
The post compares two approaches: .NET MAUI Controls, and platform UI over a shared library. Microsoft says “platform UI” here means UIKit on iOS and Android Views on Android, written in C#. The author says this gives a more direct comparison with current .NET MAUI than switching to SwiftUI or Jetpack Compose. Microsoft .NET Blog
| Approach | What Microsoft says | Practical implication |
|---|---|---|
.NET MAUI Controls |
Still the starting point for most apps | One shared UI keeps fewer screens to own and test |
| Platform UI over a shared library | Now practical to try and measure before committing | You can prototype per-platform UI and see whether the trade-offs are worth it |
Why it matters
For teams deciding whether to stay fully cross-platform, the practical change is that platform-specific UI is less of a one-way door. Microsoft says the cost to build changed enough to make a rewrite practical as an experiment, not just a long-term architectural bet. That is the useful part for developers: you can now test the idea with real code, not just debate it. Microsoft .NET Blog
The post’s own experiment points to a familiar split. The author says Android default builds showed faster startup for platform UI, but with a larger package than the .NET MAUI default. They also say the route taken can change navigation results, so the choice is not a single universal winner. Microsoft .NET Blog
A simple decision table
| If you prioritise | Microsoft’s post suggests |
|---|---|
| Fewer screens to own | Start with shared UI in .NET MAUI Controls |
| Faster startup on Android defaults | Consider platform UI and measure the size trade-off |
| A lower-risk experiment | Use AI to build a second UI, then test and compare before committing |
What to watch next
Microsoft’s post does not say AI eliminates the maintenance burden, and it does not claim platform UI is always better. It says the economics of trying it have changed. The remaining question for teams is whether the startup and size gains on a given app outweigh the extra testing and support work. The best next step, according to the post’s logic, is to prototype both paths and measure them on your own app rather than assume the older decision matrix still applies. Microsoft .NET Blog
`.NET MAUI Controls`
Microsoft says this is still the starting point for most apps because it gives teams less UI code to own.
Platform UI over a shared library
Microsoft says AI coding agents make it practical to build, measure and compare a second UI before committing.