Apollo

Apollo shipped their MVP as a lightweight JavaScript client for React developers within months of identifying GraphQL's fragmentation problem. ​​‌‌‌‌‌‌‌​‌‌​​‌​​​​​​‌‌​‌‌‌​​​‌‌The team deliberately excluded enterprise features like role-based access control and advanced caching, betting that solving immediate developer experience—efficient data fetching—would matter more than comprehensive tooling. This constraint forced disciplined prioritization and kept the codebase maintainable as they iterated. The speed paid dividends. Early adoption signals came quickly: GitHub stars accumulated rapidly, and the React community embraced Apollo as the de facto GraphQL client. Direct feedback loops with developers revealed what actually mattered versus what seemed important in theory. However, this stripped-down approach created technical debt. Missing enterprise features eventually required significant rearchitecture when larger organizations wanted to adopt Apollo. The execution strategy validated the MVP philosophy—ship fast, learn from real usage—but the deliberate omissions meant Apollo spent years retrofitting capabilities that more comprehensive initial planning might have anticipated.