June 10, 2026
Form drama > framework drama
Building an HTML-first site doubled our users overnight
The internet says the real miracle wasn’t code — it was making the form actually work
TLDR: A utility company replaced a broken, complicated online form with a simpler one and says completed usage doubled overnight. Commenters loved the user-first approach but fought over the braggy wording, blamed bad building habits instead of tools, and turned the story into a referendum on bloated websites.
A utility company’s online sign-up process was apparently such a disaster that one flashy rebuild lasted just three days before customers revolted. Enter the unlikely hero: a much simpler, HTML-first website — basically a lighter, more reliable way to build pages so they still work on old devices, weak connections, and even with little or no JavaScript. The result? The company says users doubled overnight after switching to a form that saved progress step by step and didn’t melt down when people tried to upload photos.
But in the comments, the crowd was having none of the easy victory lap. One camp cheered the story as a blunt lesson in basic respect for users, with one commenter practically turning it into a moral commandment: shipping bloated pages is “impolite, if not outright disrespectful.” Another group immediately grabbed the brakes and said, hold on — this isn’t really “doubling users,” it’s more like cutting the number of people who rage-quit halfway through. Same win, less spin.
Then came the tech turf war. Some readers rolled their eyes at blaming React, saying bad developers can make a mess in any tool. Others pounced on a side comment crediting Remix for reviving old-school form handling, arguing that was a stretch and maybe Next.js deserved the nod instead. And yes, there was also a mini flare-up over outsourcing, with one commenter calling out the lazy implication that “contractors in another country” explained the failure. In other words: the site got simpler, the users got happier, and the comments got gloriously messier
Key Points
- •The article describes a utility company replacing a failed customer application system with an HTML-first form flow.
- •A previous React-based implementation was pulled after three days due to customer complaints and technical problems, including inaccessible design and problematic localStorage use for uploads.
- •The replacement was built with Astro and designed to work without JavaScript, using progressive enhancement through web components.
- •Project requirements included backend persistence at every step, unique session IDs, support for outdated browsers, and WCAG AA accessibility compliance.
- •The final form architecture used separate pages for each step with server-side validation and redirects rather than a heavily client-side application model.