[Feature request]: Support Runtime Dynamic API Key Configuration for Google Navigation SDK for Android

[AlexLoveZ]

Is there an existing issue for this?

• I have searched the existing issues

Use case

Summary
Request support for setting Google Navigation SDK API keys dynamically at runtime instead of requiring static configuration in AndroidManifest.xml.

Business Problem: Multiple Google Cloud Billing Accounts

Our organization operates with multiple separate Google Cloud billing accounts (different business units), and we need navigation API usage to be charged to the appropriate account based on the user.

Current Limitation:

<!-- AndroidManifest.xml - Static configuration only -->
<meta-data
    android:name="com.google.android.geo.API_KEY"
    android:value="AIzaSy..." />

Impact:

• ❌ One APK can only use ONE API key
• ❌ All navigation costs bill to ONE Google Cloud account
• ❌ Cannot route charges to appropriate billing accounts per user/region
• ❌ Forces us to build and maintain multiple APKs just to separate billing

Use Case
Scenario:

• Organization with 3 Google Cloud Organizations (separate billing accounts)
• Single mobile application used by users across all organizations
• Need navigation API costs to bill to the correct account automatically

Proposal

Current Limitation:

<!-- AndroidManifest.xml - Static configuration only -->
<meta-data
    android:name="com.google.android.geo.API_KEY"
    android:value="AIzaSy..." />