These stakepool configuration currently have no visual design to them.
Current UI flow actually uses the same view twice. Will largely stick to that, with some minor changes.
First instance, “Stakepool Succesfully Configured” view, where user adds a stakepool for the first time and receives a success confirmation. Only follow-up interaction is Continue, which directs to the Purchase tickets view.
Second instance is when the user opens stakepool configuration view. In this instance, there can be one or more already configured stakepools, which need to be displayed there. Also there are three different interaction flows: delete stakepool (each), cancel (returns to purchase), add stakepool (directs to variant of add stakepool).
MariaPleshkova
commented
5 years ago
These stakepool configuration currently have no visual design to them.
Current UI flow actually uses the same view twice. Will largely stick to that, with some minor changes.
First instance, “Stakepool Succesfully Configured” view, where user adds a stakepool for the first time and receives a success confirmation. Only follow-up interaction is Continue, which directs to the Purchase tickets view.
Second instance is when the user opens stakepool configuration view. In this instance, there can be one or more already configured stakepools, which need to be displayed there. Also there are three different interaction flows: delete stakepool (each), cancel (returns to purchase), add stakepool (directs to variant of add stakepool).
Workfiles: decrediton - v017 - configured stakepools.xd.zip
Sidenote: VSP terms not addressed yet, but as one go.