Developer lifecycle definitions

A Practical Overview

Zoom creates tools for developers—like APIs, SDKs, or webhooks—each of which may follow its own developer lifecycle. This lifecycle generally outlines how long a product is supported, when updates occur, and when older versions are retired. Knowing the definitions behind these stages may help developers plan maintenance, manage integrations, and avoid service disruptions if a tool moves into a new stage of the lifecycle.

1. Initial release

The initial release is when a new tool (e.g., API, SDK) becomes publicly available. It's considered stable and ready for developers to use in production. Documentation, sample code, and version numbers (like v1 or v2) are often provided.

Common Developer Impact:

• You can likely begin building or upgrading your integration.

• It's important to track the version number you're using—future updates will refer to it.

2. Deprecation

Deprecation signals that an existing version or feature is expected to be replaced or removed in the future. It's often still functional, but developers are encouraged to migrate to the newer version. Zoom may provide a deprecation notice, which often includes:

• The date the feature was deprecated

• The recommended alternative (if any)

• The expected timeline for sunset

Common Developer Impact:

• Existing integrations generally continue to work, but you should begin migrating.

• Deprecated versions may stop receiving bug fixes or new features.

3. Sunset

During the sunset phase, the deprecated version often begins to lose functionality or availability. Zoom may limit new app registrations, restrict certain endpoints, or disable new API keys for the old version.

Common Developer Impact:

• You should finalize your migration during this period.

• API responses may start returning warnings or partial data.

• Support from Zoom's developer platform may be reduced.