> If you launch a new API that's intended to replace older ones, then stop exposing the legacy APIs in the default SDK. They might want to alienate and break t

> If you launch a new API that's intended to replace older ones, then stop exposing the legacy APIs in the default SDK. They might want to alienate and break things for many of their existing clients who use the older APIs. Plenty of companies contract out dev work until they have a working product and keep it as is. They don't have devs on hand to update them if they deprecate older APIs leading to a completely broken app despite all the old functionalities being perfectly adequate for the task.