Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Note

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

Table of Contents

Definition

Status

Status
titleNOT STARTED
Status
colourBlue
titleIN DESIGN
Status
colourBlue
titleIN DEVELOPMENT
Status
colourGreen
titleCOMPLETED

RBIberia Owner

RBI Owner

❓ Open questions

Info

We need to constantly make this section empty.

Requirements

Problem statement

The current configuration lacks an effective In-App message system to guide users through the auto Sign-in and Sign-up flow within the application. This absence of clear and concise messaging creates confusion for users, resulting in a suboptimal user experience and potential drop-offs during the authentication and registration processes. There is a need to configure an In-App message system that provides informative and contextual guidance to users, ensuring a smooth and seamless Sign-in and Sign-up experience while improving user engagement and retention.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:

  1. The solution should be user-friendly, and intuitive, and require minimal effort from the user to complete the Sign-in and Sign-up processes.will available to configure dynamic links, deeplink to access a specific area in the app or web

  2. The solution will available to configure external links to access a specific area in the app or web

  3. The solution should be compatible with Android /iOS platforms and devices, ensuring a consistent experience for users across different environments.

  4. Verify redirect with dynamicLink

Success metrics

🤔 Assumptions

Solution

Scenarios

Info

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