Building in Public #17: React, nearly everywhere
By Peter Coppinger
We're now two weeks into the switch from Vue to React. You'd think that with 20+ AI agents working 24/7 the switchover would be quick, but alas, this project is a bit of a beast.
A week ago I said that next week I'd have React back at the Vue quality levels. Honestly, we're close but not there yet. It was more work than I expected.
I was still on holiday with family in Portugal this week, so I wasn't at the keyboard as much as usual. If I'm honest, things didn't move as fast because of it. More on that below, when I found out the agents had started running the full test suite on every single PR. Another WTF moment, and I'd have caught it a lot sooner if I'd been sitting there managing things.
Good news: React is the default now, finally
Every new project has been built in React since 22 October. And since the 26th they've used the copy-Vue approach from last week, the one that got my pottery shop test down from 651 seconds to 150.
New websites, apps, internal apps and paid apps all build in React by default now. Docs sites are the last type of site still moving over. You can still pick Vue if you want it.

I may be insane, but I'm going to try to support both going forward: React by default, and Vue for anyone who wants it.
We replayed 50 old first builds through the live system to make sure nothing was sneaking through to Vue. All 50 came out as React. They were our own test prompts though, not real customers, so I want to see the same thing on real traffic.
Bad news: some projects still build in Vue
We're not at 100% yet. There are still four kinds of project that build in Vue. Landing pages with a backend that you start in Plan mode are fixed, and that goes out in the next release. Landing pages where you don't pick a type are nearly there. Docs sites have a React template ready, we just need to try it on a real build first. And docs sites started in Plan mode? Haven't touched those yet.
Once those four are done, it's React everywhere.
A React build from this week. I asked for "An internal app for tracking inventory for a IT company. Must support multiple level of users and stock control":


Costs and build times
React website builds on our test bench cost $1.35, $1.68, $2.00 and $2.24 this week. That's a lot more than last week's 46 cent pottery shop. To be fair these are full multi-page websites, so it's not apples to apples. But it's still more than I want to be paying.
Build times: over the last two weeks, a first build took about 8 minutes on average (median), and the slowest one in ten took over 15 minutes. That's 34 first builds, nearly all of them our own test builds. Too slow. Getting that number down is a big part of this week.
The full test suite on every PR
From Portugal I could feel the fleet moving slower than usual.
When I dug in, it turned out every change, however small, was running our entire test suite before it could be merged. That's a 20 to 25 minute run every time, and with the fleet opening changes around the clock, it all added up to a massive slowdown.
So I told the Chief of Staff:
It's ridiculous to run the full test suite per PR.
Of course, I got the usual "You're absolutely right, and that's on me…" response. I need that on a t-shirt.
So now each change only runs the tests it could actually break, and the risky areas still get their full set. Then once a night the whole suite runs, and anything that fails gets sent to an agent along with the change that probably caused it.
We're pre-launch, so I'm happy to take a bit more risk for a lot more speed. The nightly run is a good enough safety net for now.
I guess a human in the loop is still handy. Each agent was doing the "right" thing, but none of them stopped to ask what it was doing to our speed.
A few screenshots from this week:






This week
I'm back in Ireland. Holiday's over, and I'm going to work like a dog this week.
I need to get this bloody thing live and being used by humans.
So I'm going to really focus on getting React building great websites and apps, at a speed and quality that's better than the market leader. That means getting React back to Vue quality and beyond, getting first builds well under 8 minutes, and moving those last four kinds of project over to React.
Everything else waits, including shiny new features. Focus, focus, focus. I'll let you know next week how I got on.
Stay updated: one founder, an army of AI agents, building this in public.
Get each new diary entry by email: the wins, the failures, and the one number we're chasing. No spam, unsubscribe any time.
Shipped this week 27 Oct – 2 Nov
- AI: Add to an update while it is still running
- Platform: A shortcut to hide the chat
Comments