Getting to 2M users as a one woman dev team [video]

Original Article ↗ Hacker News Discussion ↗

Scale with Tiny Teams

  • Many examples cited of very small teams serving millions: early Instagram, WhatsApp, various mobile and indie games (Stardew Valley, Minecraft, Flappy Bird, Among Us, Nebulous), Plenty of Fish, Lichess, small Facebook apps, solo or near‑solo mobile apps, and FOSS projects like SQLite.
  • Some web products hit hundreds of thousands to millions of users on a single dev plus minimal ops, often with CDNs and managed infra.
  • Ratios like Craigslist and Valve (few employees per million users) are highlighted as benchmarks, though not one‑person teams.

Tech Debt, Refactoring, and Team Size

  • Small teams (or one dev) benefit from a single mental model of the codebase; this can keep complexity and debt low.
  • Several commenters argue that “delete bad code, replace with good code” is far easier in small teams; large orgs discourage this via risk aversion, incentive structures, and coordination overhead.
  • Debate over what “technical debt” even is: some blame rushed management; others emphasize inevitable debt from pivots, age, and team turnover.
  • Strong theme that all code is liability and that deletion/simplification is heavily undervalued in big companies.

StoryGraph as Product and Business

  • Widely praised as an “Amazon‑free Goodreads” with active development, better UX, stats, and mood‑based recommendations. Migration from Goodreads via CSV is described as workable but sometimes slow/onerous.
  • Some users find the app janky with occasional downtime, but are forgiving given the tiny team versus Amazon’s neglect of Goodreads.
  • Freemium model: anecdotal estimates in the thread place revenue around low‑ to mid‑six figures; many believe even a small paid percentage is enough for a few salaries. Some think too much is free.

Competing Book Platforms and APIs

  • Other book‑tracking competitors (e.g., API‑first and more community‑oriented ones) are mentioned; StoryGraph’s lack of public API is a frustration for some, though an API is on its long‑term roadmap.
  • Goodreads is criticized for poor UX, toxic review culture, and intrusive ads; readers like supporting independent alternatives.

Bibliographic Metadata Problems

  • Getting book data is described as a mess: multiple commercial providers (Nielsen, Ingram, Bowker) with inconsistent, dirty data and archaic genre taxonomies.
  • Open sources (OpenLibrary, national libraries, Crossref, WorldCat) help but have gaps, quality issues, or access limits.
  • Collaborative filtering and mood‑based recommendations are seen as promising, but underlying metadata remains a hard problem.

Gendered Title Debate

  • The phrase “one woman dev team” triggers a sub‑discussion.
  • One side argues gender is irrelevant and titles should say “one person” or simply highlight the achievement.
  • Others point out that only gender‑highlighting of women provokes this kind of meta‑debate; “one man dev team” rarely gets challenged.
  • Some see the framing as celebratory and normalizing; others see it as subtly patronizing. No consensus.

Miscellaneous Notes

  • Seasonal usage spikes around New Year reading goals are noted.
  • Some users report password‑length truncation issues on StoryGraph as a security/UX concern.
  • Several links are shared to talks and podcasts for deeper dives into the app’s story and technical decisions.