Posted on 12-08-2012
There are over 8100 in the ProgrammableWeb API directory. We are at a point where aggregating common, popular APIs into single, standardized interfaces is emerging as the next evolution in web and mobile app development.
To support common patterns in web and mobile app development like user management, object storage, image management, social integration and analytics, API aggregation platforms are emerging. Examples of aggregation of APIs are across business sectors like:
These API aggregation platforms are looking to take multiple API resources and aggregate them into a single, common API interface that developers can use across multiple platforms. These common API interfaces may possess the best features across aggregated APIs as well as introducing in new design features.
API copyright would prevent API aggregators from emulating the best API design patterns in the industry. Even if individual API owners didn’t enforce copyright and the industry sent signals that APIs were able to be copryrighted, it would prevent aggregators from standardizing access across common APIs.
The aggregation of common API resources such as images, provides opportunities for increasing developer efficiency when building web and mobile applications. Consider accessing images across multiple platforms such as Flickr, Facebook, Instagram and Picasa--each API could take days to integrate with, and API aggregators like Singly allow integrate with multiple image platforms in single interface.
API copyright would prevent the reuse and remix of common or successful API patterns within a space. API aggregation would either not exist in this environment or be unable to emulate existing, successful characteristics of APIs and create new, possibly inferior approaches.
API aggregation and interoperability are essential ingredients in the fast growing API economy, where elements like cloud computing, cloud storage, social integration, photos, videos and other resources need to flow, exchange and aggregate freely. Copyright would restrict the organic aggregation needed across all business sectors.
Other reading on this subject:
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- Hipster Coffee Shop Interface
- Separating The Layers Of The API Operations Onion While Thinking About API Copyright
- Implementation Of An API Design Should Never Require Permission From The API Designer
- What Would API Copyright Have Done To The Birth Of Cloud Computing
- The Machine Readable Questions We Should Ask Of Terms Of Service
- Retrieve My Data Like Retrieving Video Surveillance Photos From CCTV
- Restaurant Menus As Analogy For API Copyright
- The Future Of Public Private Sector Partnerships Being Negotiated At The API oAuth Scope Level
- One Of The Problems With API Terms of Service Is That There Is No Negotiation