Maps 3D SDK for Android quick reference

The Maps 3D SDK for Android lets Android apps display interactive 3D maps built from Google's 3D imagery. It provides markers, popovers, polylines, polygons, glTF 3D models, camera path animations, and controls for user interaction and camera movement.

Maps 3D SDK for Android: key facts

  • Product: Maps 3D SDK for Android
  • Also known as: Maps 3D Android SDK
  • Category: Maps
  • Platform: Android
  • Runs on: Client (app or browser code)
  • Launch stage: GA
  • Lifecycle: Active
  • Overview: Maps 3D SDK for Android overview
  • Regional availability: Limited. Availability varies by country and region; see the Maps 3D (JavaScript, Android, iOS) column on the Google Maps Platform coverage page. (coverage details)

Maps 3D SDK for Android: when to use it

Use Maps 3D SDK for Android when:

  • You need to show an interactive, photorealistic 3D map of real-world locations in an Android app.
  • You need markers, popovers, polylines, polygons, or glTF 3D models placed on a 3D map in an Android app.
  • You need predefined camera animations (fly-to, fly-around) that guide users between points on a 3D map.
  • You need to control which camera movements and UI controls users can use on a 3D map in an Android app.

Don't use Maps 3D SDK for Android when:

  • You're building a web app that needs 3D maps. Use Maps JavaScript API instead.
  • You're building an iOS app that needs 3D maps. Use Maps 3D SDK for iOS instead.
  • You need a production-ready standard 2D street map in an Android app (ROADMAP mode in this SDK is Experimental). Use Maps SDK for Android instead.

Maps 3D SDK for Android: setup

Official Maps 3D SDK for Android packages:

  • maven: com.google.android.gms:play-services-maps3d

Maps 3D SDK for Android: common mistakes

  • Problem: If the map mode isn't specified when the map loads, the map fails to load. Fix: Always set a Map3DMode (SATELLITE, HYBRID, or ROADMAP) in layout XML (map3d:mapMode) or with setMapMode/Map3DInitConfig. See /maps/documentation/maps-3d/android-sdk/map-modes.
  • Problem: Click listeners (map and marker clicks) don't run on the main UI thread, so direct UI updates from the handler fail. Fix: Switch to the main thread before updating UI, for example with lifecycleScope.launch(Dispatchers.Main). See /maps/documentation/maps-3d/android-sdk/add-a-marker.
  • Problem: Map state is shared across Map3DView instances, so markers, overlays, and camera position from an old view carry over to a new one. Fix: Keep only one active Map3DView; call onDestroy() on the old instance and manually clear markers, overlays, and reset the camera through GoogleMap3D. See /maps/documentation/maps-3d/android-sdk/add-a-3d-map.
  • Problem: By default, tapping a basemap point of interest shows the Places UI widget, which also requires the Places SDK dependency. Fix: Add the Places SDK for Android dependency, and return true from onMap3DClick in OnMap3DClickListener to suppress the default widget if you don't want it. See /maps/documentation/maps-3d/android-sdk/points-of-interest.

What you can do with Maps 3D SDK for Android

See the guides linked below for each task, or compare across products in the Capabilities Explorer.