1. Deep Link from Fire TV to your app
Fire TV displays featured content, which refers to sponsored tiles or promotional material shown on the Fire TV home screen. These are essentially advertisements designed to help users discover new streaming content, apps, or services. When a user clicks a featured content tile, the deep link launches the app and navigates directly to the relevant content or promotional page. For information on how to to implement Feature Rotator deeplinks in Vega apps, see Handle Featured Content Deep Link in Vega Apps. For more information about featured content, see Deep Linking to Featured Content from the Fire TV UI in the Fire OS documentation.2. Deep link from your app to amazon clients
You can deep link from your app to the Amazon Appstore or retail website to direct users to specific apps, search results, or developer pages. For example, you can initiate a forced update for your app on Fire TV using a deep link that directs the user to the app’s detail page in the Amazon Appstore. This deep link includes the app’s ASIN and anintent=app_update parameter. For information about supported links for deep linking to Amazon clients within your app, see Deep Linking from within Your App.
3. App to app deep links
App to app deep links allow an app to send a deep link to another app using a custom URI. Apps commonly use this to open specific content such as a movie, TV show, or live channel, in another app based on the contract between the apps.Implementing Deep Links in Vega
Message addressing schemes
Vega Messaging primarily uses a URI based system. However, to maintain compatibility with existing Fire OS apps, limited support for intent style URIs is available. To provide backward compatibility with featured content, Vega supports the same deep link URIs used by Fire OS apps. Particularly the Fire OS based intent style scheme. For information about the messaging addressing schemes that Vega supports, see Message Addressing Schemes. Define the URI using supported schemes such as custom URIs (myapp://…) or HTTPS links (https://…). Avoid query parameters in the URI, just define the base path. For information about defining URIs, see Message Addressing Schemes. Example URIs:Step 1: Add manifest entries
Step 1.1: Add messages and privileges
For each supported URI, add a corresponding[[message]] block in your app’s manifest. To restrict who can send or receive a message, attach sender and receiver privileges to the message section. For information about setting sender and receiver privileges, see the “Add Security Rules” section in the Message User Guide.
Step 1.2 Map messages to the launch component
Deep links use thepkg:// scheme followed by the name of the component to launch Lifecycle components by name.
Other URI schemes don’t directly identify the component to launch. You must specify additional information in the manifest in the offers.message-target section and define which component to launch for each deep link.
Step 1.3 Define module
Define a module and list all of the messages associated with it. For information on the correct format and guidelines for accepted module IDs, see the “[[offers.module]]” section of Manifest [offers] Section.Step 2: Receive messages in your app
Vega uses react-native linking to send and receive messages. The following procedure shows how to to receive a deep link message and process it in your app.Step 2.1 Import the linking library
Step 2.2 Receive message when App is already open
If the app is running in the foreground or in the background when the deep link is triggered, the app receives aurl event. To listen for the event, use Linking.addEventListener().
Step 2.3 Receive message when App is not open
If the app is not running when a deep link is triggered, useLinking.getInitialURL() to get the URL that launched it. Call this on app launch (for example, inside ()) to check if a deep link was used to start the app.
handleDeepLink() function to parse the URL and perform the required action.

