In development, the term full stack – familiarity with multiple programming languages for both frontend and backend development – is thrown around pretty regularly. Full spectrum is one that’s used from time to time, and may be a better way to describe the techniques required for superior API practice. Read more
When creating an API, it’s all too easy to release something that “just works.” For some developers who aren’t working at an API-first company where the API is a central component to their business, they may see creating an API as a distraction from their core duties and rush to get a product out that does the job it’s supposed to, but little more than that. Read more
When we think of Application Programming Interfaces — APIs — we may not immediately pair them with User Interface design. Implemented as a background tool, APIs are largely in the hands of developers, and technical documentation has a natural reputation of being elusive for laymen. Read more
In a previous article we encouraged every company to join the digital revolution and provide APIs. But when faced with an existing Information System (IS), the steps toward exposing a business process with an API become far more intricate. An IS may be bloated with pre-existing organizational processes and data structures, which, if exposed directly, can make for a very poor user experience, and possibly a complete deadlock. Read more
