A good deprecation strategy involves a lot of forward thinking and an awareness of how developers or end users are currently leveraging your capabilities, and how a given API deprecation will affect them. The hard-earned trust that you’ve built and maintained with these individuals is at risk with any type of deprecation.

Executing on a clear, trustworthy deprecation strategy is a multi-faceted initiative which requires input from several departments, an understanding of industry standards, and clear versioning throughout your product lifecycle. Knowing which voices to have in the room, what the industry standards are, and formulating appropriate communication timelines will ensure a world class policy is curated before it’s needed.

Join Will as he dives into the nuances of this process and covers how to avoid the common pitfalls that come from lacking a strategic approach to deprecating your APIs, from both a technical and business perspective.

Key Takeaways:

• Deprecation of APIs or features doesn’t have to be painful
• Deprecation is the first step towards retirement
• A good plan requires a multi-faceted strategy across departments
• Deprecation and Versioning go together