If you are developing for Android and the Google API you want to use is included in the Google Play Services library, use that library for the best performance and experience. If the Google API you want to use with Android is not part of the Google Play Services library, you can use the Google API Client Library for Java, which supports Android 1.5 (or higher), and which is described here.
Begin by reading the Android development instructions for the Google HTTP Client Library for Java.
As described in the Android development instructions, the best practice on Android (since the 2.1 SDK) is to use the AccountManager class (@Beta) for centralized identity management and credential token storage.
For information about the OAuth 2.0 flow, see the OAuth 2.0 instructions for Android.
ClientLogin is a deprecated authentication protocol used by older Google APIs. For new applications, we encourage you to use the more secure OAuth 2.0 protocol. Support for ClientLogin in the Google API Client Library for Java will be removed.
Older Google APIs that support ClientLogin are well supported on Android. To get
an auth token, call
AccountManager.getAuthToken() with the appropriate
authTokenType for the Google API you are using, for example
cl for the
Google Calendar Data API.
Partial response and update
Google APIs support a partial-response protocol that allows you to specify which fields are returned to you in the HTTP response. This can significantly reduce the size of the response, thereby reducing network usage, parsing response time, and memory usage. It works with both JSON and XML.
The following snippet of code drawn from the Google+ Sample demonstrates how to use the partial-response protocol:
Plus.Activities.List listActivities = plus.activities().list("me", "public"); listActivities.setMaxResults(5L); // Pro tip: Use partial responses to improve response time considerably listActivities.setFields("nextPageToken,items(id,URL,object/content)"); ActivityFeed feed = listActivities.execute();
A good example that uses the generated service-specific library is tasks-android-sample. Another example can be found in calendar-android-sample, which mixes ClientLogin with the service-specific library.
Caution: Some of the code snippets in the video are outdated, although the guidelines are still relevant.