I was happy to see Google launch an API for Google + this week. I’m not chomping at the bit to build anything social on it, but I’m glad they made it public.
I wanted to take some time to review the API from a technology standpoint, and look at what possibilities it opens up for developers.
The Google + API provides a RESTful interface for the newly launched Google social network, Google +, and provides access to profile data and activity streams. The API uses OAuth for authentication and JSON for its request and response formats.
That’s it. Pretty underwhelming from a developers perspective. I’ll be able to make some badges or widgets, maybe stream my activities in the sidebar of my Wordpress blog. Where is my photo access (wait that is in Picassa), or my video access (wait that is in Youtube), or my social events (wait that is in Google Calendar)?
Ok, forget about about other content, what about my write access? I want to be able to write to my activity stream and update my profile. I want other apps that I authorize to be able to publish to my activity stream.
I'll stop there. Without write access, there is no use railing about lack of application platform, access to circles, and true data portability and ownership via the API.
In short, I think Google could have come out of the gate with a little more. Maybe linking up some of my other Google systems via my Google + profile, like Picassa images, and Youtube video. But more importantly developers should have write access. OAuth, plus write access to my social profile and activity stream should have been part of this release. It would have sent the right message to developers.
I also understand how hard all of this is for them. They have a lot to consider, and pleasing developers are only one piece of the puzzle. But as we’ve seen with Twilio and Twitter, your developer ecosystem can help make your platform have the applications and features users are looking for, making it a desirable place to be.
Platform success seems to come based upon the adoption of three key user groups: early adopters, developers and end-users. With Google + we’ve just experienced the early adopter phase, what sort of environment will Google provide for developers during the next phase of growth.
|Developers, Google, Google+ API, OAuth, Platform, Social, Social Network|
blog comments powered by Disqus
Latest Blog Posts
- APIs in DFW
- Adding API Broker Under Monitoring for API Aggregators
- The Dark Matter That Make APIs Work
- Potential for API Aggregators to Provide Valuable Industry Data
- My Talk Tomorrow Night at the Dallas-Forth Worth API Professionals Meetup
- The White House Releases An Open Data Strategy
- When API Success Signals Begin Working Against You
- Get To Know Which Languages Your API Developers Are Using
- Twitters Developer Area is More Embeddable Than API
- Overview Of Backend as a Service (BaaS) White Paper
- Make Sure And Have Multiple KPIs For Your APIs
- API Enabled Toys For Our Children
- I Am Speaking At The Dallas-Forth Worth API Professionals Meetup May 14th
- How Much Do You Spend Attracting and Supporting Freemium API Developers?
- What Does The API Evangelist Do?
- Startups Need To Work Together on API Definitions
- Parse Is Successful By Truly Solving Problems for Mobile Developers
- API Commandment: Thou Shalt Not Forego Talking to a Person
- API Trends
- API Priorities
- Have You Taken A Look At AT&T APis Lately?
- Helping People Understand APIs Through Real World Examples
- Evolving Beyond API Service Providers and Tools to Goal Based API Toolkits
- APIs & The Federal Government
- After Last Couple of Weeks, It's Clear There Is Big Opportunity In The API Space