Skip to content

Determine need for success state when returning to app [Consider] #809

@jason-dehaan

Description

@jason-dehaan

User Story/Problem to be Solved

As a follow-on from the Midpoint Review meeting, ticket 117018 shares the following Consider feedback: During the MPR, it was indicated that engineering was looking at the feasibility of an error state (error messaging) in the app if the Add to Wallet was not successful. Consider if a providing a success state is equally as valuable to users on entry back into the app. This confirmation may be helpful to multiple user types, such as older users, users of assistive technologies, such as screen readers, or users with cognitive disabilities.

Confirm with Michelle and Natalie before implementing to ensure that this feedback aligns with mobile direction for the product.

Tasks

  • Determine if providing a success state is equally as valuable to users on entry back into the app.

Acceptance Criteria

  • If it is determined that a success state is equally as valuable to users on entry back into the app, a success state message has been created.

Info and Resources

Link to this feedback can be found within our Collaboration Cycle ticket.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions