Google rolled out the version 11 update of Google Play Services earlier this month with a range of changes to the platform. This update focused on ads, app invites, awareness, identity, and much more. So if you are interested in all of the changes in the update, you check out the full release notes. The biggest change with the Google Play Services SDK adds some new APIs for developers who want to access LocationServices.
Some people are curently using GoogleApiClient for these types of tasks, but according to a recent talk about using the new location APIs, Google can actually reduce friction on your end. The new LocationServices APIs have been designed to help developers access to the device location, as well as allow setting up geofences, so that they can prompt users to enable location on their device and much more. Google confidently believes that the new location APIs will give a better experience for developers as they are now simpler and the code is no longer error-prone.
Also read: Google Releases Blockly 1.0 For Android
However, the connection logic of the new APIs are automatically handled, so if you are a developer, you need to attach a single completion listener. Calling the API will also depend on the service connection, which means you won’t have to wait for onConnected before making requests. The new LocationServices APIs is based on the Task API, which makes it easier to create asynchronous operations.
The new APIs will automatically fix the failures of the certain connection as well. That means you will no longer have to implement code that prompts updating Google Play Services. There is also many interesting things that can help the work of developers much easier. Google recommends you to check out for the updated location samples on GitHub.