Building an HTML-first site doubled our users overnight
Points and comments are a snapshot, not live.
HTML-first form design doubled completion rates for a UK utility company's service application.
A contractor rebuilt a failed React-based service application using Astro with HTML-first principles for a regulated UK utility company facing customer satisfaction penalties. The previous React app, online for three days, failed due to inaccessible design, loading spinners, and image uploads stored in localstorage's 5MB limit. The new version submitted form data to the backend at each step, worked without JavaScript, and functioned on outdated browsers and poor connections. Form validation used a lightweight web component wrapping native HTML validation rather than client-side libraries. On launch, form completion doubled; analytics packages hadn't previously tracked users bouncing from JavaScript failures. The author notes one user completed the form a month after starting it, attributing success to persistent backend session storage.
What commenters are saying
Top comments challenged whether the result reflected framework choice versus developer skill, noting crappy sites can be built in any stack. Deeper discussion centered on architecture trade-offs: server-rendered forms preserve browser defaults (back button, progress indication, keyboard navigation, error handling) that SPAs must rebuild manually. Commenters noted most React developers don't test forms without JavaScript and that framework defaults matter. One contributor highlighted the practical irony of a defensive-SPA article that itself failed to load, suggesting the effect is real. Minor debate over Remix's role in the renaissance versus Next.js popularity, with consensus that defaults and opt-in/opt-out patterns influence outcomes more than pure technology choice.