Posted on 06-27-2014
I had several folks point me to the Nest API release the other day. I enjoy this, because I’m not always the fastest in finding news—eventually I’ll find it, but I rely on my human API monitoring network, just as much as my algorithmic API monitoring network, to bring stories to my attention. I’m still reviewing the Nest API release, but one thing that stood out to me, was how real-time is baked into the API by default, and specifically using Firebase.
The Nest API documentation states:
Use the official Firebase client libraries (Web, iOS, Java, and Node), which allow you to synchronize your data with a subscription-based, near-real time platform. As you develop your client, you'll find these resources useful: Firebase Data Structure, Reading and Writing data.
Nest also provides options, if you can’t use the Firebase library (not sure why this would be):
In cases where the platform you're developing your integration on has no available Firebase library, you may want to use REST or REST Streaming instead.
I track on real-time technology like Firebase as part of my API trends research, and much like other trends like aggregation and reciprocity, I think we’ll start seeing these trending layers baked into API operations by default. I’ve seen APIs reference default API reciprocity, using platforms like Zapier, and I think we’ll see more APIs adopt real-time frameworks by default in the future.
API providers need to focus on what they do best, providing API access to their valuable data, content and other programmatic resources. It is wise for providers to leverage existing providers to deliver real-time, aggregation, reciprocity, voice, and other complimentary API layers. I will continue to keep my eye out for how APIs are providing a much fuller stack of resources for developers, using their own resources, while also augmenting with other leading technology platforms.
comments powered by Disqus
Winning in the API Economy
|Download as PDF|
Latest Blog Posts
- Beyond Public APIs In Government: Internal Access to Resources
- Can You Show Me The ROI On All Of This API Stuff Before We Commit
- In The Future APIs Will Be Default For All Cities
- No Public APIs Are Not Going Away Just Cause A Few BigCos Fumble At It
- Internal API Search Engine For Everyone At Your Company (Not Just Developers)
- If You Need Assistance With Your Healthcare API Strategy I Have The Person
- Explaining APIs To Senior Leadership: Access To Company Resources Without The IT Hassle
- A Conversation With @ijroth, @dorkitude, @antonyfalco, and @medjawii In The Next Generation API Stack Panel @APIStrat
- API Evangelist Thoughts On The Right To An API Key And Algorithmic Organizing
- Explaining APIs To Your Senior Leadership
- An API Evangelism Strategy To Map The Global Family Tree
- 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