Shared publicly  - 
Google Play services

At Google I/O we announced a preview of Google Play services, a new development platform for developers who want to integrate Google services into their apps. 

Today, we’re kicking off the full launch of Google Play services v1.0, which includes Google+ APIs and new OAuth 2.0 functionality.

The rollout will cover all users on Android 2.2+ devices running the latest version of the Google Play store, and will take about a week to complete. Please wait for us to post that the rollout is complete before launching any apps on the store which use Google Play services.

In the mean time, go grab the client library from Android SDK manager, check out our updated documentation, and start coding!
Neil Wilson (melonmotion)'s profile photoGodfrey Duke's profile photoJianfei Luo's profile photoGoogle+ Developers's profile photo
This is so weird, I was looking through and found a reference to this a few hours ago - it still said coming soon. How strange. :)
And OAuth even has a Spring Security Extension! I just wet my pants.
I like the apps , sometimes crash when i use , for example Android give notification about programs ,and sometimes not work estably :example Google + and Panaclips who works sometimes .
No wonder lots app upgrade today.
How does this relate to the google-api-java-client libraries? +Yaniv Inbar It appears the "Google+ Platform for Mobile" is a complete rework or at least a wrapper for the So, will the java libraries be deprecated in favor of new "XXX Platform for Mobile" libraries?  
Does the OAuth 2.0 functionality only work for Google APIs or is it for any service like Facebook's for example, just that the flow goes through a Google account? Should I have my server team implement OAuth 2.0 for our app to take advantage of the new service? Currently, AccountManager works with our session tokens.
I followed the instructions on using it in Eclipse but it can't find it. In "Project > Properties > Java Build Path > Order and Export", no Google Play Services.
I'm going to give this a spin next week. I did some with the google api java client libraries. That worked but this looks even better.
+Danny Roa I had to manually import the lib.  It is in the android-sdk folder under extras/google/google_play_services/libs/google-play-services.jar
can't wait for cloud endpoints and use the two together
can anyone tell me what it exactly in simple it is beneficial for a android user.........
I would say Play services has greatly helped the user experience. It has brought google maps v2 , better oauth2 authentication and other benefits all without the user doing anything. Think of it as an update to the android OS. By distributing this way it can be delivered much quicker to users instead of waiting for carriers and manufacturers to update the phones(which takes months!) 7 MB is a drop in the bucket of 8-32 GB
What's the difference between waiting for carriers to update devices and handling it separately? The end result in both cases is the device has the update. This is the "another way". 
Do carriers use user preferences? I don't understand how a carrier doing it is proper, and Google doing it is not proper. I'm not going to argue what is done, I just have a Nexus7 so I can't possibly have experience of dealing with different carriers or older devices, I was trying to get a better explanation for what you were stating.

Do you deem being unforgivably slow to upgrade (or not upgrading at all) acceptable? It hampers everyone, because it generally means either a lot of users don't get an app because it was built for a later version, or apps are crippled to remain capable with other versions. There are improvements that help performance and security even before you consider app development changes. I don't believe it is acceptable for any device capable of handling these changes to not receive them. I don't think it is necessary, or even correct, to give a general user control over was is and is not in a framework, as that should be largely irrelevant from the user's point of view. Their focus should be on how they use it.
Thanks Pete, it is good to get constructive feedback. Since you want that to be your last comment, I guess I should avoid continuing the discussion with you. 

Given the nature of the openness of Android, users feel take on the feeling of wanting to have control over everything they can see (trying to condense the mindset of the users you described). However, they don't have control over what is or is not part of the framework, and this is important for developers and users. The problem seems to be that a part of the framework (Google Play Services) was forced - by the nature of the openness of Android - to be exposed to the users in a manner similar to things they have complete control over. This results in the feeling that they can't control something that the should be able to control. I believe that sentence is your point. Nevertheless, I believe it is the case that Google Play Services is an essential part of the framework, not merely a core app like any of the other Google provided apps. It's like there being an EditText, or ContentProvider, or LoaderManager in the framework. It provides a consistent implementation of a feature and guarantees that developers can use it without (much) worry of a device not supporting it, which helps provide consistency across apps from the user's point of view.

So, if it can be considered a part of Android itself, then I believe the reactions from the users are incorrect, but understandable. Otherwise, it is as you said, and users will feel like there's something that is circumventing their command. 
Add a comment...