<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Building in public — Vorx blog</title>
    <link>https://www.vorx.com/blog/category/building-in-public</link>
    <description>Posts in Building in public from the Vorx blog.</description>
    <language>en</language>
    <atom:link href="https://www.vorx.com/blog/category/building-in-public/feed.xml" rel="self" type="application/rss+xml"/>
    <lastBuildDate>Mon, 16 Nov 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Building in Public #19: Catching the market leader</title>
      <link>https://www.vorx.com/blog/building-in-public-19-catching-the-market-leader</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-19-catching-the-market-leader</guid>
      <pubDate>Mon, 16 Nov 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Last week I said I hoped this post would be called &quot;Catching the market leader&quot;. It nearly wasn&apos;t. From 0 of 8 to 8 of 8, with a lot of doubt in between.</description>
    </item>
    <item>
      <title>Building in Public #18: Chasing the market leader</title>
      <link>https://www.vorx.com/blog/building-in-public-18-chasing-the-market-leader</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-18-chasing-the-market-leader</guid>
      <pubDate>Mon, 09 Nov 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>A few weeks ago we were ahead. Then the switch to React set us back. This week we chased the market leader down: ahead on app speed and edits, not yet on design.</description>
    </item>
    <item>
      <title>Building in Public #17: React, nearly everywhere</title>
      <link>https://www.vorx.com/blog/building-in-public-17-react-nearly-everywhere</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-17-react-nearly-everywhere</guid>
      <pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Two weeks into switching from Vue to React. It&apos;s the default now, but we&apos;re not done, and I found the agents running the full test suite on every PR.</description>
    </item>
    <item>
      <title>Building in Public #16: 651 seconds to 150: how copying ourselves made React fast</title>
      <link>https://www.vorx.com/blog/building-in-public-16-651-seconds-to-150</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-16-651-seconds-to-150</guid>
      <pubDate>Mon, 26 Oct 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Our first React builds took 651 seconds. Copying the steps our Vue builder already does well got the same test to 150. What we check before it goes live, and what&apos;s still rough.</description>
    </item>
    <item>
      <title>Building in Public #15: Battling for Websites &amp; Switching to React</title>
      <link>https://www.vorx.com/blog/building-in-public-15-battling-for-websites-and-switching-to-react</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-15-battling-for-websites-and-switching-to-react</guid>
      <pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Apps on engine 004 are looking great, and websites were a disaster. Blind taste tests against Lovable, why an info site isn&apos;t a showcase, and why we&apos;re moving to React.</description>
    </item>
    <item>
      <title>Building in Public #14: It Felt Like a Slow Week. But Stats Show Otherwise.</title>
      <link>https://www.vorx.com/blog/building-in-public-14-it-felt-like-a-slow-week</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-14-it-felt-like-a-slow-week</guid>
      <pubDate>Mon, 12 Oct 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>It felt like a slow week, but 613 changes went live. Launching Workforce at RebelCon, why everything was moving so slowly, Engine 004 one week on, and the boring bits of starting a company.</description>
    </item>
    <item>
      <title>Building in Public #13: The Blind Taste Test</title>
      <link>https://www.vorx.com/blog/building-in-public-13-the-blind-taste-test</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-13-the-blind-taste-test</guid>
      <pubDate>Mon, 05 Oct 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>We built the same apps on Lovable, Base44 and Vorx and had four judges rank them blind. Lovable won both. Here&apos;s what we missed, which cells on the Gap Map moved, and the four build engines it took to get here.</description>
    </item>
    <item>
      <title>Building in Public #12: I Won&apos;t Rest Until We&apos;re There</title>
      <link>https://www.vorx.com/blog/building-in-public-12-i-wont-rest-until-were-there</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-12-i-wont-rest-until-were-there</guid>
      <pubDate>Sun, 27 Sep 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Honestly, I&apos;m disappointed we&apos;re not moving faster. But I have a high bar for this, and I won&apos;t release a mediocre product. Here&apos;s where we really stand against the best two, and the map I&apos;ll update every week.</description>
    </item>
    <item>
      <title>Building in Public #11: One Hell of a Frustrating Week</title>
      <link>https://www.vorx.com/blog/building-in-public-11-one-hell-of-a-frustrating-week</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-11-one-hell-of-a-frustrating-week</guid>
      <pubDate>Sun, 20 Sep 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>A database bill of around $723 I didn&apos;t see coming, an agent that killed my database from a school car park, and 3,496 databases created by a bit of code that had gone blind. Also: Vorx AI Ltd is real, I started a second product by accident, and tonight I&apos;m moving the whole database.</description>
    </item>
    <item>
      <title>Building in Public #10: I Wouldn&apos;t Give This to My Friends Yet</title>
      <link>https://www.vorx.com/blog/building-in-public-10-i-wouldnt-give-this-to-my-friends-yet</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-10-i-wouldnt-give-this-to-my-friends-yet</guid>
      <pubDate>Fri, 11 Sep 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>The bar isn&apos;t a number on a dashboard. It&apos;s whether I&apos;d give Vorx to friends and family. This week: we&apos;d been measuring the wrong thing, a $185 day, and build errors down from over 50% to 12.9%.</description>
    </item>
    <item>
      <title>Interlude: The 133-Second Problem</title>
      <link>https://www.vorx.com/blog/building-in-public-9-the-133-second-problem</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-9-the-133-second-problem</guid>
      <pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>A build that works but takes over two minutes is a build most people never see finish. Here is what we found when we actually measured it.</description>
    </item>
    <item>
      <title>Building in Public #9: I Got Mad at My Own CMO</title>
      <link>https://www.vorx.com/blog/building-in-public-9-i-got-mad-at-my-own-cmo</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-9-i-got-mad-at-my-own-cmo</guid>
      <pubDate>Fri, 04 Sep 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>I asked my CMO agent to review and enhance 36 existing templates. Instead it rebuilt them from scratch, cost real money, and nearly threw away a good one. Also this week: the AI catching its own hallucination before publishing, a Supabase outage I wrongly blamed us for, a head-to-head build against the category leader, and the honest build-failure number.</description>
    </item>
    <item>
      <title>Interlude: Running a Company From 30,000 Feet</title>
      <link>https://www.vorx.com/blog/building-in-public-8-running-a-company-from-30000-feet</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-8-running-a-company-from-30000-feet</guid>
      <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>The fleet shipped hundreds of things this week and almost every problem left is a coordination one. A database migration that passed every check and broke anyway, work piling up at gates only I could open, an AI bill explained by failed builds, and the growing suspicion that the agents are managing me as much as I&apos;m managing them.</description>
    </item>
    <item>
      <title>Building in Public #8: The Day I Took the Fleet Off My LAN</title>
      <link>https://www.vorx.com/blog/building-in-public-8-the-day-i-took-the-fleet-off-my-lan</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-8-the-day-i-took-the-fleet-off-my-lan</guid>
      <pubDate>Fri, 28 Aug 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Three of my twenty AI agents quietly stopped working and nothing told me. So today every agent got a guardian watching its pulse, the whole fleet moved off my home Wi-Fi, and I can now run the company from my phone. But the real story is the one number still standing between Vorx and its first users.</description>
    </item>
    <item>
      <title>Interlude: The Week I Went on Holiday</title>
      <link>https://www.vorx.com/blog/building-in-public-7-the-week-i-went-on-holiday</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-7-the-week-i-went-on-holiday</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>No big engineering story this week. I took the family away, mostly stayed off the laptop, and found out what happens to a company of AI agents when the founder disappears: it keeps shipping. Plus one confession involving a phone, a sun lounger, and 2:32am.</description>
    </item>
    <item>
      <title>Building in Public #7: 188 Builds Later, and the Week I Invented a CTO</title>
      <link>https://www.vorx.com/blog/building-in-public-7-188-builds-later</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-7-188-builds-later</guid>
      <pubDate>Fri, 21 Aug 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>The testing marathon and its numbers, how one person runs fourteen workstreams, and the sixty finished pull requests nobody was shipping. So I hired a CTO.</description>
    </item>
    <item>
      <title>Interlude: The logo that took 1,000 tries</title>
      <link>https://www.vorx.com/blog/the-logo-that-took-1000-tries</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/the-logo-that-took-1000-tries</guid>
      <pubDate>Wed, 19 Aug 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>A two week design competition, 978 entries whittled down to one, an animated mark I did not have to draw, and the week I decided to back this myself after the two people who were joining me stepped away.</description>
    </item>
    <item>
      <title>Building in Public #6: Measure, reject, keep</title>
      <link>https://www.vorx.com/blog/building-in-public-6-measure-reject-keep</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-6-measure-reject-keep</guid>
      <pubDate>Fri, 14 Aug 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>A new north-star metric, the A/B tests that said no, payments in generated apps, and a week of honest dashboards.</description>
    </item>
    <item>
      <title>Building in Public #5: The need for speed</title>
      <link>https://www.vorx.com/blog/building-in-public-5-the-need-for-speed</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-5-the-need-for-speed</guid>
      <pubDate>Fri, 07 Aug 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Declaring war on a twenty-minute build: profiling, one big win, and the discipline of measuring before believing.</description>
    </item>
    <item>
      <title>Building in Public #4: Publish</title>
      <link>https://www.vorx.com/blog/building-in-public-4-publish</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-4-publish</guid>
      <pubDate>Fri, 31 Jul 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>The first Vorx app published to the open internet, plus billing, custom domains, plan mode, and email in one enormous week.</description>
    </item>
    <item>
      <title>Building in Public #3: Going online, the hard way</title>
      <link>https://www.vorx.com/blog/building-in-public-3-going-online-the-hard-way</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-3-going-online-the-hard-way</guid>
      <pubDate>Fri, 24 Jul 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Containers, cloud storage, a bug that failed every single online build, and the grind to the other side.</description>
    </item>
    <item>
      <title>Building in Public #2: Chasing Quality, and Becoming vorx.com</title>
      <link>https://www.vorx.com/blog/building-in-public-2-chasing-quality</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-2-chasing-quality</guid>
      <pubDate>Fri, 17 Jul 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>Sixty landing pages, a lucky find, and a quality bar I could actually test against. Then the rename across five repositories, real backend features, and previews in the cloud.</description>
    </item>
    <item>
      <title>Interlude: How I got here</title>
      <link>https://www.vorx.com/blog/introducing-vorx</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/introducing-vorx</guid>
      <pubDate>Wed, 15 Jul 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>The long version, for anyone who wants it. Writing software since I was eight, eight years running an agency, twenty at Teamwork.com, the day Linear ruined normal software for me, and why I started again. Skip it if you are here for the build.</description>
    </item>
    <item>
      <title>Building in Public #1: The Dreamer</title>
      <link>https://www.vorx.com/blog/building-in-public-1-the-dreamer</link>
      <guid isPermaLink="true">https://www.vorx.com/blog/building-in-public-1-the-dreamer</guid>
      <pubDate>Fri, 10 Jul 2026 00:00:00 GMT</pubDate>
      <category>Building in public</category>
      <description>I tried the top ten AI app builders and found three good ones and gaps everywhere. So: what if apps went the extra mile by default, and what if they were instant, offline and alive? Week one, from a flat mockup to the first prompt that worked.</description>
    </item>
  </channel>
</rss>
