Codirity goes live here on Saturday, September 26, at 12:01 AM PT. That's 4:01 AM in C rdoba, where I live, so I'll be up answering comments from the first minute.
We signed a new client at Codirity this week. They're a SaaS company. I'm not naming them until they say it's fine. They came to us with two problems: the app is slow and has a backlog of bugs their users keep hitting, and the landing page gets traffic but almost nobody signs up.
We're starting with the landing page because it's the faster fix. We'll rewrite the copy so the value proposition is clear on the first screen, cut page weight, and rebuild the signup flow with fewer steps. We're measuring conversion before and after.
Twice this year I shipped a defect straight past a check that was supposed to catch it. Both checks ran, both went green, and neither could have gone red.
The first was a "no horizontal overflow" check on a redesign. It passed over a real collision between a price and the note next to it, because the page had body { overflow-x: hidden }. That one line hides intra-grid collisions from the viewport, so the check was measuring a symptom the CSS had already suppressed.
I launched Meshio here in March. It finished the day with 0 points and no comments from anyone outside my own account. That's the honest baseline.
I spent a while assuming the product was the problem. I don't think it was. I launched from an account with no followers, no karma, and no history of having talked to anyone on this site. I posted it and waited. Product Hunt distributes a launch through the maker's network and through the velocity of the first hours, and I had neither, so there was nothing to distribute through.
