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
- My Discussion Today With 6 Hypermedia Leaders At API-Craft in Detroit
- Getting To Know Jørn Wildt For The API Craft 2014 Detroit Hypermedia Panel
- Hypermedia Feels Like We Are Still Learning To Communicate With APIs
- Getting To Know Markus Lanthaler For The API Craft 2014 Detroit Hypermedia Panel
- Getting To Know Kevin Swiber For The API Craft 2014 Detroit Hypermedia Panel
- Getting To Know Steve Klabnik For The API Craft 2014 Detroit Hypermedia Panel
- New Indix API KickStart Program Reduces Costs For Developers
- Getting To Know Mike Kelly For The API Craft 2014 Detroit Hypermedia Panel
- A Shared, Distributed Experience(Metrics) Layer For The API Driven Application Stack
- Showcasing Your API Integrations With Other Platforms
- Increasing The Focus On APIs In Higher Education Is Important
- Getting To Know Mike Amundsen For The API Craft 2014 Detroit Hypermedia Panel
- The New StrongLoop API Server Provides A Look At Future Of API Deployment
- Models For API Driven Startups Built Around Public Data
- 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 18F's, 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