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
- Thank You For Your API Evangelist Blog(s)
- Video From The Hypermedia Panel At API-Craft In Detroit Last Month
- Please Open Source Your API Before Shutting It Down
- Explaining My Work Around APIs In Higher Education To Institutions
- You Can Have An API Just By Choosing Products And Services That Have APIs
- Using Excel As An API Datasource And An API Client For The Masses
- Brewing Up Something Awesome With The Jive Software API
- Relationship Between APIs And Containers
- Real-time and Visualizations Will Be Key in Financial API Deployments
- Notification Focused Startups Within Leading API Ecosystems
- APIs That Do One Thing And Do It Well Like ZipLocate
- Which API Do I Need?
- The Expanding API Conference Landscape
- Ocotoparts Open Source Google Spreadsheet
- Andrew Nacin Of WordPress @APIStrat Chicago
- Push Button API Deployment With The Heroku Button
- WordPress Style API Modules For Government
- The Heroku HTTP API Design Guide
- What I Have Been Calling API Trends, Are Slowly Being Baked Into API Operations
- FDA Finding Their API Mojo With A New Drug Label API
- Adding PokitDok To Healthcare Research And The API Stack (Well They Did)
- Why I Am Continuing To Integrate Zapier In My Business Workflow
- Who Is Going To Build The Uber API Platform For The Sharing Economy?
- The API Focused Dev Shop
- Route SMS Messages To Google Spreadsheets Via Twilio API With TwilioSheet