Feature - In-app
- Bandoch dos Santos, Diego (Deactivated)
- de Sousa Santos, Rodrigo
- Paula Winter (Unlicensed)
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
- 1 Table of contents
- 2 Definition
- 3 Open questions
- 4 Requirements
- 4.1 Problem statement
- 4.2 Acceptance criteria
- 4.3 Success metrics
- 4.4 Assumptions
- 5 Solution
- 5.1 Scenarios
- 5.1.1 Scenario 1: xxx
- 5.2 Design
- 5.1 Scenarios
- 6 Development
- 7 Release
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 current in app solution does not allow the configuration of dynamic links in the in app and this is necessary for this functionality to be more effective
Acceptance criteria
Acceptance Criteria:
The solution will available to configure dynamic links, deeplink to access a specific area in the app or web
The solution will available to configure external links to access a specific area in the app or web
The solution should be compatible with Android platforms and devices, ensuring a consistent experience for users across different environments.
Verify redirect with dynamicLink
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]