Places SDK for Android lets Android apps access Google's database of place and business information through Place Autocomplete, Place Details, Nearby Search, Text Search, and Place Photos. Places SDK for Android (New) is the current version and depends on Places API (New).
Places SDK for Android: key facts
- Product: Places SDK for Android
- Also known as: Places SDK for Android (New)
- Category: Places
- Platform: Android
- Runs on: Client (app or browser code)
- Launch stage: GA
- Lifecycle: Active
- Overview: Places SDK for Android overview
Places SDK for Android: when to use it
Use Places SDK for Android when:
- You need place details, photos, Nearby Search, or Text Search results inside a native Android app.
- You need a ready-made autocomplete widget or Places UI Kit components that return place predictions as users type in an Android app.
- You need to build location-aware Android features based on businesses and points of interest near the user's device.
Don't use Places SDK for Android when:
- You need to call Places from a server or backend over HTTP instead of from an Android app. Use Places API (New) instead.
- You're building a native iOS app. Use Places SDK for iOS instead.
- You're building a web page in the browser. Use Maps JavaScript API instead.
Places SDK for Android: setup
- Service to enable:
places.googleapis.com - Authentication: API key
- Usage attribution: Call
Places.addInternalUsageAttributionId(String)when initializing the SDK to send a usage attribution ID; delete the call or pass an empty string to opt out. - Get started: Set up Places SDK for Android
- Reference: Places SDK for Android reference
- Pricing: Places SDK for Android usage and billing
- Policies: Places SDK for Android policies
- Release notes: Places SDK for Android release notes
Official Places SDK for Android packages:
- maven:
com.google.android.libraries.places:places
Places SDK for Android: related products
- Often used with: Maps SDK for Android
Places SDK for Android: common mistakes
- Problem: Nearby Search requests without a field list (field mask), or with an empty one, return an error. Fix: Pass at least one
Place.Fieldin theSearchNearbyRequestfield list. See /maps/documentation/places/android-sdk/nearby-search. - Problem: Place Details (New), Nearby Search (New), and Autocomplete (New) fail when the API key lacks Places API (New), or on SDK 5.x and earlier when the app calls
Places.initialize(). Version 6.0.2 removedPlaces.initialize(), so code calling it doesn't compile after upgrading. Fix: Enable Places API (New), add it to the API key's allowed APIs, and initialize withPlaces.initializeWithNewPlacesApiEnabled(). See /maps/documentation/places/android-sdk/legacy/migrate-overview. - Problem: The
Placereturned byfetchPlace()has noPhotoMetadata(so there's nothing to resolve) when the field list omitsPHOTO_METADATAS. Fix: IncludePlace.Field.PHOTO_METADATASin the field list. BecausefetchResolvedPhotoUri()is deprecated, use the Places UI Kit Place Details component to display photos. See /maps/documentation/places/android-sdk/place-photos. - Problem: Apps that show place details, photos, or reviews without the returned third-party and author attributions violate the policies. Fix: Display the attributions returned with
Place,PhotoMetadata, andReviewobjects. See /maps/documentation/places/android-sdk/policies.
Places SDK for Android: legacy and deprecated features
- Places SDK for Android (Legacy) / Places API (Legacy) features (Autocomplete, Current Place, Place Details, Place Photos legacy): Legacy since 2025-03-01. Replacement: Places SDK for Android (New) features backed by Places API (New), initialized with
Places.initializeWithNewPlacesApiEnabled(). Symptom: As of October 2026, new Cloud projects can't enable Places API (Legacy) (existing projects remain supported). SDK 6.0.2 removed the legacy methods, which exist only in 5.x and earlier. See the migration guide. Places.initialize(): Decommissioned since 2026-09-30. Replacement:Places.initializeWithNewPlacesApiEnabled(). Symptom: Method removed from the SDK in 6.0.2; code that calls it no longer compiles. See the migration guide.PlacesClient.findCurrentPlace()andawaitFindCurrentPlace()(Current Place, legacy): Decommissioned since 2026-09-30. Replacement:PlacesClient.searchNearby()(Nearby Search (New)). Symptom: Methods andFindCurrentPlaceRequest/FindCurrentPlaceResponseclasses removed in 6.0.2. See the migration guide.PlacesClient.fetchPhoto()andawaitFetchPhoto(): Decommissioned since 2026-09-30. Replacement: Places UI Kit Place Details component (PlacesClient.fetchResolvedPhotoUri()is deprecated). Symptom: Methods andFetchPhotoRequest/FetchPhotoResponseclasses removed in 6.0.2. See the migration guide.- Places API (Legacy) autocomplete widget (
Autocomplete,AutocompleteSupportFragment,AutocompleteActivityMode): Decommissioned since 2026-09-30. Replacement: Place Autocomplete (New) widget (PlaceAutocomplete) orPlacesClient.findAutocompletePredictions(). Symptom: Classes removed from the SDK in 6.0.2. See the migration guide. - Places compatibility library (
com.google.android.libraries.places:places-compat): Deprecated since 2022-03-31. Replacement: Places SDK for Android (com.google.android.libraries.places:places). Symptom: Frozen at v2.6.0; no new features or bug fixes. AutocompleteFragmentclass: Decommissioned since 2025-09-25. Replacement: Place Autocomplete (New) widget (PlaceAutocomplete). Symptom: Class removed from the SDK in 5.0.0 (AutocompleteSupportFragmentwas also removed in 6.0.2).
What you can do with Places SDK for Android
See the guides linked below for each task, or compare across products in the Capabilities Explorer.
Places SDK for Android: Generative AI
- Return an AI-powered summary of user reviews for a specified Google Place identifier.
- Return an AI-powered place summary of the area and amenities surrounding a specified Google Place identifier for an electric vehicle charging station.
Places SDK for Android: Places
- Return a list of places and place details based on a query string.
- Return a list of places and place details near a specific location.
- Return autocomplete results about places based on a query string.
- Return detailed information about a specific place.
- Return photos of a specific place. Note: Display each photo's author attributions (the author's name, linked to their profile URI) with the photo. The Places policies for each platform require this, for example /maps/documentation/javascript/policies#photo-attributions and /maps/documentation/places/web-service/policies#photos-and-review.
- Resize place photos.
- Return ratings and reviews for a specific place. Note: In Places API (New) web service, Place Details is an HTTP GET request to https://places.googleapis.com/v1/places/{placeId} with X-Goog-FieldMask (for example, rating,userRatingCount,reviews); Text Search, Nearby Search, and Autocomplete use POST. On Android, pass Place.Field.RATING, USER_RATING_COUNT, and REVIEWS to PlacesClient.fetchPlace(). On iOS, pass GMSPlacePropertyRating, GMSPlacePropertyUserRatingsTotal, and GMSPlacePropertyReviews in GMSFetchPlaceRequest.
- Add an autocomplete widget to a web page or app that returns results about places based on a query string.
- Specify the data fields included in place information responses.
- Specify the place types to include in place information responses.
- Return the URI to open the place details page in Google Maps for a place.
- Return information about the place where the user's device is currently located. Note: Legacy Current Place methods were removed in Places SDK for Android v6.0+ and Places SDK for iOS v11.0+; retrieve device coordinates from platform location services and call Nearby Search.
- Return an AI-powered overview summary for a specific place.
- Return an AI-powered area summary describing places in the area around a specific place.
- Return information about places based on a query string that are located along a predefined route.
- Return distance, travel time, and directions URI to text-search places from a set of latitude/longitude coordinates.
- Return distance, travel time, and directions URI to nearby places from a set of latitude/longitude coordinates.
- Return distance, travel time, and directions URI between the origin for a predefined route and each of the places returned based on a query string, that are also located along the route.
- Return distance, travel time, and directions URI between each of the places returned based on a query string, that are also located along a predefined route, and the route destination.
Places SDK for Android: Places UI Kit
- Apply CSS styling to a place data UI element. Note: CSS custom properties apply to Maps JavaScript API Places UI Kit elements; Places SDK for Android and Places SDK for iOS style Place UI Kit views programmatically using theme and style attributes. EEA COMPLIANCE REQUIREMENT: For showing place data on a map in the European Economic Area (EEA), do not call Places API web services from a backend server. Use client-side Places UI Kit components on the target platform (Maps JavaScript API on web, Places SDK for Android on Android, or Places SDK for iOS on iOS). Full requirements and FAQ: https://developers.google.com/maps/comms/eea/faq
- Customize place data UI element styling and configurations with a UI element customization tool. Note: EEA COMPLIANCE REQUIREMENT: For showing place data on a map in the European Economic Area (EEA), do not call Places API web services from a backend server. Use client-side Places UI Kit components on the target platform (Maps JavaScript API on web, Places SDK for Android on Android, or Places SDK for iOS on iOS). Full requirements and FAQ: https://developers.google.com/maps/comms/eea/faq
- Add a UI element that displays information about a specific place to a web page or mobile app. Note: EEA COMPLIANCE REQUIREMENT: For showing place data on a map in the European Economic Area (EEA), do not call Places API web services from a backend server. Use client-side Places UI Kit components on the target platform (Maps JavaScript API on web, Places SDK for Android on Android, or Places SDK for iOS on iOS). Full requirements and FAQ: https://developers.google.com/maps/comms/eea/faq
- Add a UI element that displays a list of places based on a query string to a web page. Note: Supported on both web pages (Maps JavaScript API) and mobile apps (Places SDK for Android and Places SDK for iOS). EEA COMPLIANCE REQUIREMENT: For showing place data on a map in the European Economic Area (EEA), do not call Places API web services from a backend server. Use client-side Places UI Kit components on the target platform (Maps JavaScript API on web, Places SDK for Android on Android, or Places SDK for iOS on iOS). Full requirements and FAQ: https://developers.google.com/maps/comms/eea/faq
- Add a UI element that displays a list of places near a specific location to a web page. Note: Supported on both web pages (Maps JavaScript API) and mobile apps (Places SDK for Android and Places SDK for iOS). EEA COMPLIANCE REQUIREMENT: For showing place data on a map in the European Economic Area (EEA), do not call Places API web services from a backend server. Use client-side Places UI Kit components on the target platform (Maps JavaScript API on web, Places SDK for Android on Android, or Places SDK for iOS on iOS). Full requirements and FAQ: https://developers.google.com/maps/comms/eea/faq
- Add a basic autocomplete UI element to a web page or app that returns Google Place identifiers based on a query string. Note: EEA COMPLIANCE REQUIREMENT: For showing place data on a map in the European Economic Area (EEA), do not call Places API web services from a backend server. Use client-side Places UI Kit components on the target platform (Maps JavaScript API on web, Places SDK for Android on Android, or Places SDK for iOS on iOS). Full requirements and FAQ: https://developers.google.com/maps/comms/eea/faq