Articles

Interface discovery is a search and guess game that we’ve all learned out of necessity. Because of a lack of strategic perspective, different interface types keep being published in their historically evolved discovery mechanisms (for example address, phone number, social media, app, support/docs sites and so on). As communication channels proliferate this is causing unnecessary friction. In this article we explain why interface ambiguity becomes especially troublesome if you look at it from an accessibility perspective.

This article is part of APIFutures, a distributed, creator-led effort to identify the most significant opportunity and/or the greatest challenge facing the API community in 2024.

LLMs are about to drastically increase the volume and apparent quality of automatically generated messages. Some communication will be generated on behalf of a valuable customer or partner, but a lot will be low value attempts from third parties that are exploring opportunities at the expense of their receivers. How will we deal with all these - at first sight - ‘legitimate’ interactions?

In this article, John Doyle (CEO, Drupal Architect at Digital Polygon) explains why creating APIs is no longer enough, and organizations must effectively market their APIs to developers and product owners if they want to gain traction. In this post, John Doyle will explain what it takes to achieve business success with your API projects. 

A shortened transcript from the panel discussion at the API The Docs conference in Amsterdam. At the event, John Daffern (BT Group), Jack Bambury (Shell), Koen Adolfs (ABN AMRO), and Suzanne Daniels (Port) answered Carla Teixeira's (Miro) and the audience's questions.

A summary of the panel discussion at the APIDays New York conference. Ashni Mehta (MongoDB), Joshua Markham (Verizon), and Michael Hibay (WSFS Bank) shared their thoughts on the concept of developer success and exchanged ideas about the future of APIs with Kristof Van Tomme.