Samples demonstrating how to use Maps SDK for Android.

This repo contains the following samples:

1. ApiDemos: A collection of small demos showing most features of the Maps SDK for Android.
2. FireMarkers: Demonstrates how to use Firebase Realtime Database to drive synchronized, live animations on a Google Map across multiple devices using a controller/agent architecture.
3. WearOS: Displays a map on a Wear OS device. This sample demonstrates the basic setup required for a gradle-based Android Studio project.
4. Tutorials: Samples associated with tutorials in the developer's guide. See each sample for a link to the associated guide.
5. Snippets: Snippets for code found in https://developers.google.com/maps/documentation/android-sdk

To run the samples, you will need:

• To sign up with Google Maps Platform
• A Google Maps Platform project with the Maps SDK for Android enabled
• An API key associated with the project above ... follow the API key instructions if you're new to the process
• See each sample for pre-requisites.
• All require up-to-date versions of the Android build tools and the Android support repository.

1. Download the samples by cloning this repository
2. In the welcome screen of Android Studio, select "Open an Existing project"
3. Select the root directory of this repository (android-samples)

We provide an interactive web dashboard (MANUAL_VERIFY_CATALOG.html) and live execution API server (test/server.py) that allows stepping through and evaluating all 39 SDK capabilities across both Kotlin and Java live on attached devices.

👉 See the Verification Tool Guide for full instructions on how to start the server, use the UI controls, and automate evaluations via AI agents.

To verify that all samples build and pass tests via CLI, run:

./scripts/verify_all.sh

To run instrumentation tests on a connected device or emulator, use:

# For Wear OS devices/emulators
./scripts/verify_all.sh --connected-wear

# For Mobile (Handheld) devices/emulators
./scripts/verify_all.sh --connected-mobile

Alternatively, use the gradlew build command to build the project directly or download an APK under releases.

This library calls the addInternalUsageAttributionId method, which helps Google understand which libraries and samples are helpful to developers and is optional. Instructions for opting out of the identifier are provided below.

If you wish to disable this, you can do so by removing the initializer in your AndroidManifest.xml using the tools:node="remove" attribute:

<provider
    android:name="androidx.startup.InitializationProvider"
    android:authorities="${applicationId}.androidx-startup"
    android:exported="false"
    tools:node="merge">
    <meta-data
        android:name="com.example.library.utils.attribution.AttributionIdInitializer"
        tools:node="remove" />
</provider>

Contributions are welcome and encouraged! If you'd like to contribute, send us a pull request and refer to our code of conduct and contributing guide.

This sample uses Google Maps Platform services. Use of Google Maps Platform services through this sample is subject to the Google Maps Platform Terms of Service.

If your billing address is in the European Economic Area, effective on 8 July 2025, the Google Maps Platform EEA Terms of Service will apply to your use of the Services. Functionality varies by region. Learn more.

This sample is not a Google Maps Platform Core Service. Therefore, the Google Maps Platform Terms of Service (e.g. Technical Support Services, Service Level Agreements, and Deprecation Policy) do not apply to the code in this sample.

This sample is offered via an open source license. It is not governed by the Google Maps Platform Support Technical Support Services Guidelines, the SLA, or the Deprecation Policy. However, any Google Maps Platform services used by the sample remain subject to the Google Maps Platform Terms of Service.

If you find a bug, or have a feature request, please file an issue on GitHub. If you would like to get answers to technical questions from other Google Maps Platform developers, ask through one of our developer community channels. If you'd like to contribute, please check the contributing guide.

You can also discuss this sample on our Discord server.