Open Vickysomtee opened 2 years ago
Good suggestion. The 'change' button currently resets the demo.
However this is not clear to the user. We could change the label from change
to reset
. I would like to keep the ctrl
+ k
menu hidden as it also has some developer options that might confuse the user.
What do you think?
Okay, changing the change
to reset
makes sense but this resets the entire dashboard which in not really a good flow
User experience wise, the change
button should be used to change the demo character, then we can have a reset
beside the start
button of each demo flow to reset that particular flow (If possible).
Changing a character requires you to receive a new set of starter credentials, so that's why it's currently resetting the whole demo in that flow (there is an issue open to fix this #13).
If i understand correctly, you mean reset as in resetting the use case so you can re-do it? Currently, there is an option for this in the ctrl + k menu, but maybe we can change it so you can hover over the checkmark of the use case and than re-do it. It will clutter up the user's wallet with more of the same credentials though as we can't delete them from a user's wallet.
Yes, I mean resetting just a use case. Can there be a work around to avoid the same credentials to be clutterd in the user's wallet? If no, we can leave the usecase resetting and then focus on just resetting the character demo
So this is my point:
Can we make resetting the demo possible without hitting the ctrl + k
because most users are not aware of the ctrl + k
command and as you stated, you want it hidden. Would be better to have something else apart from the change button (Which might soon serve another purpose if issue #13 is worked on) to reset a character demo.
We can have the reset button opposite the text with a red font. Sounds cool?
We can't really do anything about the cluttered credentials in the user's wallet, but its not that big of a problem.
If you complete the use case it currently shows like this:
Maybe we can keep it like this and just add a rewind icon in there and allow users to redo the use case. There is nothing actually prohibiting users from redoing a use case, besides some information in the state about what use cases are completed.
I think we should consider having a reset button for a particular Demo in case a user wants to retake the demo.
My suggestion is either putting a notice of what the
ctrl
+k
command does or simply putting a reset button for easy access.