Skip to main content
Hat Boy Software

These articles come from reviewing and repairing products that reached real users before they were ready: the patterns we find in apps built fast, moving users off an insecure legacy app without a cutover weekend, testing embedded firmware before the hardware exists, code highlighting that fails accessibility contrast, and the post-mortem of our own contact form. Client names are withheld unless the client agreed to be named.

For the engineering behind the notes, see App Stabilization.

7 articles

App Stabilization & Rescue

An MVP backend you won't have to rewrite

Why we start client MVPs on Postgres rather than Firebase, what Supabase still ties you to, and how to split a mobile MVP from its store launch.

App Stabilization & Rescue

What we find in apps built fast

The failure classes a stabilization assessment keeps finding in apps built quickly, including with AI builders, and how to check your own.

← All articles