[Archived] Feature - Firebase SDK Integration

This is a template that should be used to document each feature. It’s meant to be easy, not prescriptive - change it at will!

Table of contents

Requirements

Problem statement

The lack of integration with Firebase Dynamic Links SDK can limit the accessibility of the application's content, reduce the effectiveness of advertising and marketing campaigns, and restrict content sharing, which can have a negative impact on our customers, sales, and profitability.

Possible solution:

To implement the integration with Firebase Dynamic Links SDK into our platform.

https://firebase.google.com/docs/dynamic-links?hl=es-419

Acceptance criteria

 

Dynamic Links FAQ:

Firebase Dynamic Links is no longer recommended for new projects. In the future, the Dynamic Links service will shut down, but you will have at least 12 months from the announcement date to migrate. Around the end of Q2-2023, we will announce more information.

We launched Dynamic links about 7 years ago to make URLs more powerful (for example, dynamically changing the destination of a link based on run-time conditions) at a time when there were different degrees of support on various OSes and platforms. We remain committed to the importance of enabling app teams of all sizes to improve their deep linking experiences and are investigating how to help developers adopt technologies such as App Links, and Universal Links. → At least 1 sprint for refinement + 1 sprint for dev

How long will I have to migrate?

We want to make the migration as smooth as possible, so you will have a minimum of 12 months to fully migrate. We will share more details around the end of Q2-2023.

Will new and existing links continue to work?

Yes, your new and existing links will continue to work until the Dynamic Links service is shut down. Around the end of Q2-2023, we will provide more information on the long term plan for Firebase Dynamic Links.

High Level Estimate = 1 dev sprint with technical refinement and QA tests / No UX efforts needed.

Scenarios

Note: these are high-level scenarios that must pass testing before we can release the feature. They should also be used to drive design. Note that we do not specify user interface details in these steps - that is deliberate so that we focus on the process and not on the UI since the UI can change throughout design and development.

Scenario 1: xxx

Steps

Expected results

Steps

Expected results

Do this

Expect that

Design

Figma design here: [insert link]

Development

We have worked to cover all scenarios listed on the acceptance criteria. Currently, we have to implement the remaining items:

https://rbictg.atlassian.net/browse/IBFEC-824

 

Tests

 

Remaining tests:

Status BK PT: Both deep link and dynamic link are working for Android. For iOS, we are waiting for Apple configs to be released to production.

Release

Remaining fix:

Status: A change in the social login feature done by another vendor caused an impact on the APK signature. We are waiting for the fix to have a new version.