In the wallet we currently manage a 'next-task' after claiming. This is to incentivize users to take action / contribute to X / make aware of running campaigns / or anything else relevant to active claiming users.
This functionality needs to be migrated/copied over to gooddapp.
Detailed Description of Functionality
Provide descriptive explanation of the flow. Where does the user navigate from? Where and how does the flow terminate?
(edge cases)
(special considerations / expectations)
(Describe various state a feature/screen could be in)
Technical Implementation
*Outline the technical approach for building the feature. This section is typically filled out by the development team or can contain suggestions.
(dev team: @johnsmith-gooddollar @sirpy @L03TJ3)
[ ] (What api's / sdk's could possibly be used)
Design Reference
Link to Figma reference screens & screenshots of key screens
Acceptance Criteria
Specify criteria that will be used to determine if the feature meets the requirements and functions correctly.
[ ] (Should include a list of testing points for QA how to verify design/functionality)
filled out by the development team or can contain suggestions._
Test Cases
Specify the happy path and unhappy path scenarios to test to verify the feature works as expected.
Business Description
In the wallet we currently manage a 'next-task' after claiming. This is to incentivize users to take action / contribute to X / make aware of running campaigns / or anything else relevant to active claiming users.
This functionality needs to be migrated/copied over to gooddapp.
Detailed Description of Functionality
Provide descriptive explanation of the flow. Where does the user navigate from? Where and how does the flow terminate?
Technical Implementation
*Outline the technical approach for building the feature. This section is typically filled out by the development team or can contain suggestions. (dev team: @johnsmith-gooddollar @sirpy @L03TJ3)
Design Reference
Link to Figma reference screens & screenshots of key screens
Acceptance Criteria
Specify criteria that will be used to determine if the feature meets the requirements and functions correctly.
Test Cases
Specify the happy path and unhappy path scenarios to test to verify the feature works as expected.