Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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

Definition

Status

NOT STARTED IN DESIGN IN DEVELOPMENT COMPLETED

RBIberia Owner

RBI Owner

❓ Open questions

We need to constantly make this section empty.

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

  1. SDK Integration:

    1. The Firebase Dynamic Links SDK must be successfully integrated into our platform following the guidelines provided in the official documentation (https://firebase.google.com/docs/dynamic-links).

    2. The integration should be compatible with the latest version of the SDK and maintain backward compatibility with previous versions to ensure a smooth transition and functionality across different app versions.

  2. Dynamic Link Generation:

    1. The platform should be able to generate Firebase Dynamic Links programmatically for different content pages, such as product details, promotions, or specific app screens.

    2. The generated Dynamic Links should include relevant parameters, such as campaign details, source, medium, and any additional custom parameters required for tracking and analysis.

  3. Deep Linking:

    1. The integration should enable deep linking functionality, allowing users to be directed to specific content within the app when clicking on a Firebase Dynamic Link.

    2. Deep links should accurately navigate users to the intended content, ensuring a seamless and intuitive user experience.

Success metrics

🤔 Assumptions

Solution

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

Do this

Expect that

Design

Figma design here: [insert link]

Development

Release

  • No labels