Firebase Dynamic Links

Firebase Dynamic Links is an external tool that facilitates the integration with deeplink and has some features to define the behavior in Apple and Android, such as redirect user to the store when there is no app installed. This tool still can be used, but will be shutdown soon, as stated here.

The WL app will not have integrated firebase dynamic links sdk . What does it mean? The app will not have the firebase dynamic links listener to parse and handle deeplink contents automatically. The following pictures simplifies the main use-cases, but this reference has all details.

• 

  If the mobile customer clicks on it and has installed app, then it goes to the app directly. Otherwise, he/she can be redirected to the store and get the app.

• The web customer accesses the webpage directly in the browser.

Deeplinks

Regular deeplinks (not necessarily firebase dynamic links ) will be enabled in the app, so that when the user has it already installed app and click on deeplink, he/she can be redirected to the app. Otherwise, he/she will go to the browser with the webpage link opened.

Universal Links without path

Universal links are IOS deeplinks. Once the user clicks on links without any path ( e.g.: /menu , /store-locator , /promotion-abc ), it will be redirected to the home page.

Specifically, in IOS, after loading the page in the browser, he/she can decide to open the app, clicking on the right upper corner Open button.

Universal Links with path

The behavior for universal links with path (e.g.: /menu ) are quite similar.

Android App Links without path

In Android, when the customer enters the deeplink address in the browser, there is no automatic redirection to the app. It only happens when he/she clicks on it.

Android App Links with path

In Android, when the customer clicks on a deeplink with path, such as menu, store or promotion, the app should be redirect to the proper path.

The behavior in browser : if he/she enters an address, the webpage in browser is loaded and doesn’t redirect to the app.

Acceptance Criteria:

Paula Winter (Unlicensed) , could you please fill the acceptance criterias

Acceptance Criteria considerations after tech discovery

• SDK Integration:

  • Firebase Dynamic Links doesn’t need to be integrated in Android. It automatically works in this platform for the links generated in Firebase. The main concern here is to redirect user to the play store when the app is not installed in the device. When user has the app, it already opens it in the configured path.

  • Firebase Dynamic Links need to be integrated only in IOS. It requires this dependency to read the url content. This is necessary to redirect the user to the configured url/path in the installed app. However, when the user doesn’t have it the app installed, it automatically need to redirect user to the apple store.

• Dynamic Link Generation:

  • The generation of the Dynamic links must be done in Firebase Console. No efforts are required in terms of implementation.

  • The relevant parameters are part of the url configuration in Firebase Console / Dynamic links.

• Deep linking

  • Implementations of deeplinks must work for both Android (applinks) and IOS (universal links), the configured url is capable to open the app in the configured path. This functionality is not dependent on Firebase Dynamic Links. Any deep links provider can generate the links (even it can be generated manually , e.g.: https://www.popeyes.es/menu and it should be open natively.

Consolidated Acceptance Criteria:

• Dynamic links:

  • If the mobile customer clicks on a dynamic link and has installed app, then it goes to the app directly. Otherwise, he/she is redirected to the store (Apple store or Play store) and gets the app.

  • The web customer (Desktop or mobile devices) accesses the webpage directly in the browser, but:

    • If the user types the dynamic link on Safari on iPhone, a page with a button is displayed, then it goes to the app.

• Deep links:

  • If the mobile customer clicks on a deep link and has installed app, then it goes to the app directly. Otherwise, he/she is redirected to the respective content within the website.

  • The web customer (Desktop or mobile devices) accesses the webpage directly in the browser, but:

    • If the user types the deep link on the browser using a mobile device, he/she is redirected to the respective content within the website. If it is on an iPhone, a banner is displayed indicating to use the app.