Posted on 09-20-2011
The Google+ Hangout API will provide developers with the ability to manipulate the UI, interact with hangout participants and respond to the different events that occur within a hangout. The functionality is reminiscent of the way Google Wave gadgets and robots could interact with a wave and its participants. I wonder if we are seeing some of the Google Wave code being recycled?
To use Google+ you have to register your application with Google, and specify any other Google+ users on your team that will be able to load the application into their hangout. Since the Google+ Hangouts API is only in developer preview, this is temporary requirement.
Once registered, apps behaves like a normal web app, but it also can take part in the real-time conversations within a hangout using the API. Google+ Hangout apps will use whats called a “shared state” among all instances, notifying users of changes by other application users in real-time.
The decision to release the Google+ clearly was a strategic move against Facebook, which I understand, but I still feel strongly that a empowering developers with a fully write enabled API from the beginning, is very important to setting the tone for the Google+ API ecosystem.
Many developers, including myself were not happy with the limited functionality of the initial Google+ API release. However, I could tell that Google was being cautious in their API roll-out, and there is potentially much more behind the scenes. I expect Google will be rolling out new APIs as they feel confident, or maybe when they feel it will give them a strategic advantage, like this week during the Facebook F8 conference.
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