Linked by Thom Holwerda on Fri 14th Dec 2012 11:51 UTC
Permalink for comment 545311
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
More Features »
Sponsored Links



Member since:
2005-11-29
The Google Plus API is an API in name only: It only supports access to a read-only public feed of data. In other words, shit that nobody implementing a client cares about.
However, you'd know that if you looked at the links you throw around to try to prove people wrong.
That, and the Google Voice APIs are a complete shitfuck, and they're not even APIs, they're screen scraping solutions half the time, and the other half the time some lucky XML feed Google felt gracious enough to expose.
None of it is enough to make a client which isn't brain dead.
So this becomes a case of A) Google grandstanding, because they will eventually write a Windows Store application. Mark my words, in a years time they'll have Metro clients for their services, and B) Google taking the decision out of everyone's hands by having a poor developer story to compliment their services.