Skip to Content
v1.37.0 · shipped App version · `loadMyReports()` Read the changelog →

Mushi Mushi runs on itself

What Mushi Mushi did on my own apps

I build and run several apps of my own, and every one of them runs Mushi Mushi. These numbers are counted live from its database for those apps only. They are not customer numbers: only totals leave the database, never app names, report text or anything about the people who reported.

So far most of the bugs it fixed were found by my own checks, not reported by people using the apps. The numbers below keep the two apart.

Counting…

What the numbers say so far

A snapshot of my own 9 apps for the 60 days to 2026-11-11.

Most people who hit a bug won't report it: they just leave. So reporting takes one tap for the people who do speak up, and Mushi Mushi also looks for bugs itself.

People sent 34 bug reports, and some of those were my own testing. My own checks (code audits, Sentry, the site watch, the first-time user test) found 2,031. So about 98% of the bugs came from checks, code reviews, error alerts and my own notes, not from people's reports.

Of the 523 fixes merged in those 60 days, two started from a person's report. The rest started from those checks, error alerts and my own notes. The button still matters: a report tells you what a real person was trying to do when it broke.

It is early, and I'm still its main user. If something confuses you, open an issue and I'll read it. — Kenji

Check it yourself

  • A fix the AI review held (pull request #864): the review says why, line by line, and the fix never merged.
  • The source on GitHub: the SDKs are MIT, the server is AGPL. The function behind these numbers is public_scoreboard() in the migrations folder.

See what your own app shows a first visitor

The free Production Check reads your live pages and lists what to fix, in plain English.

Run the free check →