Posted on 06-03-2012
Mobile is fueling a lot of API growth right now. Or is it APIs fueling a lot of Mobile growth right now? Either way, APIs and Mobile go together like chocolate and peanut butter (or Nutella as my girlfriend would say).
With this growth in mobile, we are seeing a rise of Mobile Backend as a Service (MBaaS) providers, delivering a basic stack of storage, messaging, notifications, user management and other essential components for mobile developers.
The goal of MBaaS providers is to make it very easy for developers to setup and operate a backend for any application. After delivering the essentials like storage, messaging access, push notifications, etc., it makes sense that now developers will need easier integration with the data and resources available in web APIs.
MBaaS provider Kinvey is doing just that. Using ql.io, a declarative, evented, data-retrieval and aggregation gateway for HTTP APIs, they are bringing web APIs to developers, like GeoPlaces data using Google Places, product data from Ebay’s Product API and social data using Twitter.
Kinvey is baking in the most popular and valuable web APIs right into the Kinvey SDK, making data from APIs as easy to access, as data in your local Kinvey data store. Kinvey will deliver an abstracted layer on top of each API, storing data into tables, making them accessible using common queries like SELECT, FROM and WHERE. They will even let you do JOINS on multiple data sources, allowing you to mashup and improve API data performance.
Kinvey will take on the heavy lifting associated with the differences between APIs and maintain access between different API versions. I’m assuming with the amount of work involved, Kinvey will be only delivering the most valuable of web APIs or at least the most stable.
Sounds like API owners need to start building relationships with Mobile Backend as a Service (MBaaS) providers, as this might be the doorway to the next round of growth in your API adoption. Especially if MBaaS providers can truly make APIs a more local, native experience for mobile developers.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Will You Add Me To API Evangelist And How To Spot The Cool Kids
- When I Remix APIs Using Swagger How Do I Deal With Authentication Across Multiple APIs
- It Takes A Team Of Evangelists To Raise An API
- Support For Only Two Creative Commons Licenses In The API Commons
- Machine Readable Terms of Service Didn't Read Applied To APIs Via APIs.json
- API Deployment For Non-Developers Using Zapier, Google Docs, and APISpark
- State of Hypermedia Today @ API Craft In Detroit
- Need A Formal API Standard For Your Government Agency? Fork 18Fs, And Make It Your Own!
- CORS Makes Your API Portable And Remix-able
- Chief Data Officer Needs To Make The Department Of Commerce Developer Portal The Center Of API Economy
- An API Definition As The Truth In The API Contract
- Look At Existing APIs In The Space Before Designing Your Own
- Libraries Hacked: UK Library API, Data And Technology Hacks
- Financial Data Aggregator Yodlee Looking For A Director of Developer Evangelism
- AutoDevBot Open Sources Their API Monitor
- Low Hanging Fruit For API Discovery In The Federal Government
- Looking At 77 Federal Government API Developer Portals And 190 APIs
- Applying APIs.json To API Discovery In The Federal Government
- The Power In API Discovery For APIs.json Will Be In The API URL Type
- Fixing The Machine Readability in API Commons
- Evolving How We Approach The API Lifecycle With APIMatic
- APIs Can Open Up Your Company To Outside Ideas
- APIs Are Often Just A Facade That Is Covering Up The Legacy View Of World
- A Mobile Developer Toolkit With The University Of Michigan APIs
- Kicking Off Image Manipulation API Work