# I one-shotted a .NET MAUI 11 upgrade from the beach

> Source: <https://www.ansight.ai/articles/one-shotting-maui-11-from-dee-why>
> Published: 2026-11-20 00:00:00+00:00

**Recommendation:** Give the coding agent runnable UI tests plus session recordings and performance-trend baselines as guardrails, then have it rerun the same journeys after each fix; this surfaced a missing-shader crash and a multi-polygon Mapbox bug.
More in the playbook "Working with AI coding agents": <https://wpnews.pro/playbooks/coding-agents>

I one shotted a .NET 11 upgrade from the beach.

Martin and I had spent several intense months building Ansight through Startmate’s Winter ’26 accelerator. We pitched at Demo Day in Melbourne, did it again in San Francisco, and spent a few weeks chock-full of meetings.

Between meetings in San Francisco, we were cooking up a new idea…

What if Codex or Claude could hand you a running build to try from your phone?

You could open the simulator back on your dev machine, draw on anything that looked off, and send a note back. This pointed the agent to the exact frame in an Ansight recording, where it could check the surrounding screenshots, UI trees, logs and performance data.

This would become the Ansight Companion App.

Startmate was incredible, and I came back to Sydney from SF pretty fried and keen for a slower week. My girlfriend and I went to Dee Why for coffee and a walk around the headland.

After so many months in the trenches, it was time to touch grass. Er, well, sand, I guess.

We’d uploaded a new build of Red-Point that morning as part of a bit of a facelift. Red-Point was well overdue for some love after we’d been furiously focused on building Ansight since July!

At 8:52, App Store Connect emailed to say the upload had gone through and that we’d built it with the iOS 26.4 SDK. From April 2027 we’d need the iOS 27 SDK or later to upload another one. 😱

Coffee in hand, staring wistfully out at the ocean, I wondered if I could do the whole upgrade remotely and test it using Ansight. Hmmmm!

I opened ChatGPT on my phone, connected to my Mac and dropped the screenshot into Codex. I kept the brief pretty short.

Do all of the updates end to end. … run Ansight tests to fix it.

That meant taking Red-Point from .NET MAUI 10 to 11 and bringing the dependencies along on both platforms. I gave Codex a few guardrails in Ansight so it could tell how the upgrade was going while we carried on walking.

- **[UI tests through the Ansight CLI](https://www.ansight.ai/docs/workspace/tests#run-from-the-cli).** Codex had to get through sign-in, map and route search, tutorials, offline downloads and 3D guides on both platforms. It could see which checks passed, fix what failed and run the same journeys again.
- **[Session recordings](https://www.ansight.ai/docs/local-player/session-capture).** When a test got stuck, Codex could pull up the screenshot, UI tree and logs from that run to see what the app was doing at the point of failure.
- **[Trends](https://www.ansight.ai/docs/workspace/trends).** Earlier runs gave us a baseline for frame rate and memory. A 3D guide could open successfully and still stutter, so I asked Codex to check the numbers as well.
- **[Companion handoffs](https://www.ansight.ai/docs/local-player/test-handoffs).** I asked Codex to send me the running build for a smoke test. If something looked off, I could mark it on the live session and send the screenshot and note back to the same Codex conversation.

And, because I’m a very helpful person, I gave Codex one last instruction.

Do it, no mistakes!

And so Codex started beavering away while we wandered along the headland.

As it turns out, “no mistakes” only gets you so far with two mobile toolchains, a 3D engine, a Mapbox integration and extensive offline scenarios!

- One of the early iOS builds launched fine and then crashed on the first frame of a 3D guide. Evergine had generated the shaders, but they’d never made it into the app bundle.
- On Android, our Mapbox adapter was passing a boundary made up of several polygons as a single one, which broke offline downloads. A climbing app with dodgy offline downloads is a particularly annoying thing to bring to a crag.

By the end of the reruns, all 11 enabled UI scenarios had passed on iOS and Android. Hell yeah! 💪

A huge thank-you to the .NET and MAUI teams. There’s a lot of work behind getting a release like this onto both mobile platforms, and I’m glad we get to build Red-Point on top of it.

While Codex was still running those checks, a **Ready to test** notification came through.

Codex had left the upgraded app open on an iPhone simulator back on the Mac and sent me a handoff with a few things to check. I opened it in a pre-release build of the Ansight Companion app. The other test devices could keep going while I poked around on the simulator reserved for me.

I checked that the app was running on .NET 11 and opened a 3D guide. Everything looked pretty good until I went to use the toolbar and saw a few blank buttons. I drew around them in the Companion, added “Icons are missing” and sent it back. It turned out our iOS controls were disposing of shared UIKit images, and the next handoff had the icons back.

That was about as involved as I got.

Every so often I’d pull out my phone, try the app or send a note, then get back to whatever we were looking at. Sea snails in rock pools, a seal lolling in the surf, a darter airing its wings.

By God, it was nice to get some sunshine!

We got home around lunchtime and it still felt like I’d had a morning off. I’d quite happily do the next upgrade from Dee Why too.

**The Ansight Companion app is coming soon.**
