Amazon Developer

as

Settings
Sign out
Notifications
Alexa
Amazon Appstore
Ring
AWS
Documentation
Support
Contact Us
My Cases
Get Started
Design and Develop
Publish
Reference
Support
Skip to main content
The Vega Target Navigator API “targets” screens or sections within an app where users interact with input modes such as Home, Settings, Profile, or Search. Apps implementing the Target Navigator provider interface can do the following.
  1. Query available targets — Discover which screens or sections the app offers for navigation.
  2. Query the current target — Determine which screen or section the user is viewing.
  3. Navigate to a target — Navigate the app to a specific screen or section.
The Target Navigator provider API has three key components.
  • handleGetCurrentTarget — A callback that returns active app targets.
  • handleGetAvailableTargets — A callback that returns supported navigation targets.
  • handleNavigateTargetRequest — A callback invoked when the system requests specific target navigation.
Providers must proactively report state changes by using the following methods.
  • updateCurrentTarget — Notify the system when the current target changes.
  • updateAvailableTargets — Notify the system when the list of available targets changes.

Vega Target Navigator Prerequisites

Before using this API, update your app manifest to declare your intention to use the Vega Target Navigator API. When modifying the manifest entries, replace com.amazondeveloper.media.sample with your app package ID. Your app must be properly configured to interact with the Vega Target Navigator API.

Step 1: Install and set up Vega Target Navigator

To use the Vega Target Navigator API, update your package.json file with the following dependency:

Step 2: Define your available targets

A TargetInfo object represents each target with the following fields:
  • identifier (number, required) — A unique numeric ID for a target within your app.
  • name (string, optional) — A human-readable name for the target.
  • standardId (StandardTargetIdentifier1, optional) — A standard identifier that maps to well-known destinations, enabling the system to understand the target’s purpose.
The available standard target identifiers are: You can define your targets as a map keyed by identifier:
The Target Navigator Interface also supports custom targets without a standardId.

Step 3: Implement the Target Navigator handler

Create a TargetNavigatorHandler object that implements three callback methods.

Handler method details

Step 4: Register the handler

Register the handler using IComponentInstance from useKeplerAppStateManager(). Don’t do this on startup before calling any update methods.

Step 5: Report target state changes

After registering the handler, notify the system of the current state. Call both updateCurrentTarget and updateAvailableTargets on startup, and again if the state changes.

Update current target

Call app initialization whenever the user navigates to a different screen:
Pass undefined to indicate no current target, such as in a transitional state.

Update available targets

Update targets when the any navigable destinations change, such as when the user logs in.

Troubleshooting Vega Target Navigator

API Reference

Classes

Interfaces

Enumerations


Last modified on July 15, 2026