
Good API Design Principles: Building Lasting Interfaces
API design principles: Twitter's API built an ecosystem from 2006, then restrictions in 2012 and 2023 broke thousands of apps overnight.
The exact change
A 2018 empirical study by Titus Barik and colleagues at Microsoft Research validated this principle by analyzing Stack Overflow questions related to 40 popular Java and .NET APIs. | APIs rated as "easy to misuse" by Bloch's criteria generated 3.2 times more Stack Overflow questions per unique user than APIs rated as "hard to misuse," directly measuring the developer effort cost of poor design.
Removed. | Removed.
Suggested change
Removed 2 unsourced claims.
Why this is better
Each study and survey figure in the article was checked against the published source. Claims for which no published source could be located were removed.
Everyone who worked on this page
More by Emir Baycan in Programming Development
- Correction Technical Debt Explained: Managing Code Quality Over Time
- Correction What Is Version Control and Why Every Developer Needs It
- Correction What Is Technical Debt and How to Manage It
- Correction Understanding REST API: Communication in Web Services