Adding new layers of complexity within a digital service without sacrificing user experience is a difficult endeavor. Especially for platforms that accept online payments and subscription formats, maintaining support for an increasing number of payment methods is deceptively complex.
Users don’t want to think too much about the payment process. Read more
For many companies, providing an API is seen as an IT matter exclusive to internet giants like Twitter, Facebook and Google, startups like Algolia, Wit.ai and Context.io, or for government agencies to open data to the public. But are APIs really limited in that way? Read more
APIs are as vast and varied as the systems that depend on them; while some systems may handle client data, payments, and collaborative research, other APIs may handle less important data such as social media and image sharing.
Due to the variations in application and usage, APIs face a unique set of considerations and issues arising from their availability that no other system faces – the difference between having an API for public consumption or one intended for internal use, in certain circumstances, can mean the difference between megalithic success and catastrophic failure. Read more
Over the last week we followed the API blogosphere discussion surrounding API nomenclature. Steven Willmott does a good job of summing up the recent debate in a 3Scale post, Public Vs. Private APIs.
Interesting timing… we have been compiling an eBook that not only defines a taxonomy for API types but offers insightful business strategies for each variation. Read more
Most of the time when APIs are discussed it is actually Public APIs that we talk about. Public APIs are the ones that are available to everyone (even if it might cost some money) and that opens up an organisations data to outside developers. Read more