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 API 101 Workshop At @APIStrat In Chicago Next Week
- Some Advice For The Enterprise When Beginning Your API Journey
- Machine Readable API Definition Format Swagger Matures to 2.0
- How Do We Continue Moving Green Button Data And APIs Forward?
- 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