Get an email when we publish a new article or ship something noteworthy. Prefer to read in your own feed reader? Subscribe via RSS.
After ten years and three versions, we shipped a new Happo logo. Here's the story behind it: the rushed 2016 original, the smiling hippo that stuck, and a quiet typographic detail in the new wordmark that almost nobody will notice — and why caring about that kind of detail is exactly how we think about building Happo.
Happo coverage often stalls when teams worry about snapshot bills growing with their component count. Happo's new `--only` flag renders only the stories affected by a PR — dropping our own builds by 40% — so you can keep adding coverage without the cost anxiety.
When a major social media platform's in-house Android snapshot testing hit scaling limits with hundreds of developers, Happo built a Gradle plugin bridge. It preserved their existing Roborazzi setup while offloading storage, diffing, and reporting — showing that build vs. buy isn't always binary.
Screenshot testing is well-established on the web, but mobile developers often face different challenges: bloated repositories, slow builds, and scaling pain from storing PNGs directly in the repo. This interview with Henric explores how Happo solved these problems for one large social media platform.
In this interview, Happo co-founder Henric explains how <A11y/> makes accessibility testing continuous rather than one-time. The tool integrates with Storybook, Playwright, and Cypress to surface WCAG violations on every pull request — Happo’s own product started with over 1,400 violations before using it.