Change is inevitable and growth is a good thing. When your API has reached the point of expanding beyond it’s original intent and capacity, it’s time to consider the next version.
Whether that next iteration is a whole number version bump or just a feature expansion, it’s important to consider the pros and cons of how you let your developers know about it. Read more
Most web applications, and many mobile applications, rely on 3rd party APIs like social login, cloud storage, email, messaging, CRM etc. The benefits are obvious, and for some applications the API integration is a core element. However, the API dependency does make applications more vulnerable to change — one small change to an API can break an entire app. Read more
Instagram, the largest photo-only distribution social network, has exploded in usage. With 60 million photos uploaded every day, the app is now cemented as a major social entity.
Third party apps which tied into Instagram were a critical part of originally growing the platform. Read more
In the API realm, one of the most rewarding practices a developer can undertake is to unify their system functionality. Having disparate updates, library versioning, and documentation can harm the user through confusion and obsolescence, can harm the provider with rough updates, and can harm the API itself through low adoption and retention rates. Read more
The definition of an API Platform includes the requirement that the data published via an API should be core to the organization exposing it. That means that it is data critical to the success of the organization. Making that available in any way often takes courage, as it is a relatively new approach to most businesses that are more akin to keeping secrets than to promote openness. Read more