Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> It is interesting to look at it through the lens of what's the social contract between a beta user and a developer?

I think that social contract can be anything you want as long as you communicate it clearly and in advance (they did neither).

---

What "beta" means and its timeline varies widely. Mimestream was technically in public beta this whole time but quality-wise has been production-grade software most of that time. Gmail was in public "beta" for 5+ years.

Of course, many apps hit 1.0 eventually... but then a lot of those migrate their beta program to TestFlight to continue to help fix bugs and as a thank you for helping get the software to 1.0.

But the most important things if you do decide to kill the beta track post-1.0 (i.e., take away features from your users) are to: (1) give your users a timeline and sufficient heads up in advance (e.g., 30–60+ days), and (2) solicit feedback from and listen to your users. If Mimestream had done either of those, this launch would have gone a lot better.

Mimestream also offered beta testers a first-year discount code, which seemed like a nice gesture. But then upon reading the press release, they offered everyone basically the same discount. So that cheapened the offer and made the connotation go from "they're thanking their beta testers" to "they're just trying to convert as many people as possible".



Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: