13 Android apps moved in ten days
No more platform compromise
From Flutter to Kotlin
Why I used Flutter, what I noticed when the first Kotlin apps were on my phone, and moving 13 Android apps across.
Making software development more productive
How I build with AI agents, what it has come to since March 2026, and an app port that took about an hour from asking to running on my phone.
In March 2026 I started building with AI agents full time. This site is me exploring what that means for me, and hopefully for other software engineers. I think productivity will go up, but the harder problems are still going to be harder problems, and you still need someone in the loop who knows how to deal with the code coming out of the AI. Here that person is me.
I set the agents up a bit like a software team. Each project has its own Claude, working in its own folder from a spec that is the source of truth. I tell Control what I want, usually by voice. Control knows every project, and it starts the work in the right one. Anything with a UI or an open UX decision gets 3 to 5 working throwaway prototypes first. I pick one, and the spec describes the winner.
Tools in teal have their own project page.
Every Claude starts with the same rules, injected at session start. What it learns gets written down in docVault, and Lore keeps every conversation. Nothing counts as done until it's proved. Test Gate blocks a push if the number of tests drops, the e2e testers walk the app like a user, and Quality scans for the mistakes AI tends to make. Findings that keep recurring become rules.
Since March 2026 that has come to 76 projects, 6,554 commits and just over 20,000 automated tests, with me as architect and product manager and the agents writing most of the code. Much of it is plumbing, and a lot of it only has one user.
One timed example. Transcriptor takes a video link and gives back what Claude made of it. On 30 October at 16:32 I asked for a Kotlin version of its Android app. The replacement was committed about forty minutes later, and at 17:38 I'd signed in on the phone and the library looked right. About an hour.
What has made the difference for me is the checks around the agents. The prototypes, the tests and the walk-through on a device happen every time, because an agent does the legwork and the gate won't accept the work without them. I think a team bringing AI in would get the most out of putting those checks in place first.
If you'd like to talk about this, get in touch.
13 Android apps moved in ten days
From Flutter to Kotlin
Why I used Flutter, what I noticed when the first Kotlin apps were on my phone, and moving 13 Android apps across.
64 databases backed up
Guards that run without me
The checks that run on timers without me: scanning, patching, the test gate, backups and certificates. And what happened when a certificate authority was compromised.
6 places I look closely
When you no longer read every line
What I look at when I don't read every line: the borders of the code, its shape, and the test count.
1 text box a day
A product designed for people
A demo journal for people rebuilding their working life with a coach. One text box a day, and a report that only uses what the person wrote.
4 prototypes before the spec
For leasehold plots in Addis Ababa
Four prototypes on the first day, then the spec, the valuation engine and a web app in three languages on the second.
5 to 7 directions to aim for at the end
AI advice you can check
My attempt at helping people who are thinking of changing jobs or career direction, without the AI getting stuck on what they already do.