Oops, I Broke My API

Explore the complexities of API changes in this thought-provoking conference talk aimed at SDK and software library developers. Delve into the arguments for and against modifying APIs, weighing short-term pain against long-term benefits. Learn strategies for introducing new APIs, maintaining user loyalty, and balancing backwards compatibility with technological advancement. Discover the importance of semantic versioning, clear end-of-life strategies, and tools for detecting breaking changes. Gain insights on creating future-proof designs, managing redundancy, and deciding between big bang and early releases. Examine real-world examples from iText Software's experience and understand the impact of marketing and sales on API development decisions.

Intro
Agenda: 5 important questions
Backwards compatibility
Three types of compatibility
Involuntary API breaks
Avoid breaking the API when possible
Redundancy can get painful
In response to advancing technology
Changing the API as a strategy
Why we changed the iText design
Use semantic versioning
A good design to start with is key
Use tools to detect breaking changes
Avoid being a moving target
Ease the pain
Avoid back-porting
Have a clear EOL strategy
It's the fault of Marketing
It's the fault of Sales
Making development future-proof
Big bang release or early release?