How an API was designed and implemented is usually of little interest to consumers of the thousands of APIs available today. What matters most is that an API works, is easy to integrate and solves a real problem. But for the growing number of companies looking to take advantage of the booming API economy and considering developing APIs, design is an important subject.
Apigee acquires InsightsOne for deeper analytics. Cloud elements connects documents via one API. Plus: Genuitec customizes APIs for apps across web, mobile, cloud and desktop, PubNub and Ford’s vehicle dispatch app, and 8 new APIs.
Claiming.com.au is set to launch an Australian Medicare API that should drastically improve eClaiming processes for developers working with the state funded and run healthcare system. Although Medicare has served as the primary healthcare system in Australia for almost 30 years, the system has run into major bottlenecks as its technological infrastructure has not always kept up with demand. The API allows software vendors to integrate online claiming with Medicare and the Department of Veteran’s Affairs.
There’s no shortage of controversy when it comes to healthcare these days, but from a developer perspective, the increased usage of electronic medical records (EMR) represents a potential boon. The challenge is that a lot of those records are locked up in proprietary systems that for the most part are fairly inaccessible.
There’s nothing quite as adventurous in all of IT as spending months building an application that depends on a third-party API for its success. For the most part, developers usually don’t know for sure how much stress the IT infrastructure supporting any given API can stand. If their application is wildly successful, it could suddenly slow to a crawl when that third-party API gets overwhelmed by requests.
In the very early days of APIs, when John Musser founded ProgrammableWeb, the default for every new API was open–wide open. As the industry has matured, companies have become more careful to enter the open, public API waters. Though the number of APIs is still growing rapidly, most new APIs look very different from those of a few years ago. Popular services used to launch with public APIs, or perhaps have them soon after. Now the popular services are more likely to hold out for awhile, perhaps learning from those before. This wariness of openness has perhaps gone too far, ignoring the positive potential of embracing the ecosystem.
Gartner has added a two-day Learning Lab dedicated to API management to its upcoming Application Architecture, Development & Integration Summit (AADI). Plus, Ford hosts its first AppLink hackathon in Australia.
As the amount of processing power that can be affordably invoked via the cloud continues to increase, applications that were once thought too impractical to build are suddenly quite feasible. A good example of that is AppStream, a new service that Amazon is beta testing that allows graphically and resource-intensive applications to be extended out to any number of devices that previously would not have had the processing capabilities to run them.
In the final part of our series looking at the strategies businesses are using to engage with developers (B2D), we summarize three Developer Experience (DX) models from Brian Koles (ChallengePost), Pamela Fox (Khan Academy), and Ronnie Mitra (Layer 7).