-
Notifications
You must be signed in to change notification settings - Fork 31
Onboarding experience #24
Comments
To start a discussion, I have a general idea how to implement an onboarding that could satisfy the most of our design principles We can create screens like that on every new concept or a complicated UX for users. For instance, if a user sends a message to an offline user we show him a 'blue screen of help' saying that Status is a p2p messenger and works differently. I like this approach because it's flexible and has a simple logic behind. UX flow is like that:
Main disadvantages of this modular onboarding are: sometimes a user can see two screens in a row like I had it here #23 or this approach could feel like braking and interrupting main userflows. |
I like the idea of the "blue screen of help", it would be easy to integrate it in any flow and i like the idea of it being colourful so that it would contrast with the rest of the UI. Was also thinking of how are we going to show the second (third, etc.) recommendation if user decides to spit the first notice. Made a screen with "Security checkup" for that, just a quick draft, open for discussion about that. Also, showing and explaining a certain aspect only when it's relevant, is a great approach, but let's also keep in mind people who want to get the whole picture at once. |
I guess, after all we might consider using a different background colour not to confuse the "screen of help" with wallet. |
This is looking pretty nice :) I would consider Gamification during your on-boarding process. Use some gestures and have some fun with it. Clicking accept every time gets repetitive and boring. Add a 'swipe to accept' feature when confirming the passphrase. Makes things memorable :) Since you are giving 10 ETH credits to learn, why not have this as a 'reward' for completing the tutorial. This would help newcomers to understand Cryptocurrency and your process quicker! I would agree with your different color background too, white would be super clean and allow for you to customize interactions and animations with the gradient colors on the Status landing page. |
want to contribute ~20h/w |
Is this an open offer or you have to work at Status? :) |
Onboarding will be an important part of the upcoming beta release. Currently this is in a preliminary explore phase, and the requirements will evolve as the beta work matures. This swarm is the collaboration of marketing, product, design, and engineering to ensure that users have a consistent brand and product experience. I updated the issue description to reflect this. |
What if we build a separate DApp to put all the educational content in it? This would be a separate piece to be built but outside of the Status app. In the same time "it knows" your address, so if we would add Gamification to it, as @mcivor25 suggested, then it still can be done, so for completing a tutorial user can get some bonus... @andmironov / @flexsurfer would you be interested in designing/building such DApp? |
Closing in favor of the more high-resolution/texture #80 which completely supersedes this. |
Preamble
Summary
Status, Ethereum, cryptocurrency and the decentralized internet are new paradigms for many users. The job of onboarding will need to educate and inspire users about these new technologies, as well as help users get started with Status, create an account, send their first message, explore their first app, and initiate their first transaction.
Onboarding will be an important part of the upcoming beta release. Currently this is in a preliminary explore phase, and the requirements will evolve as the beta work matures.
This swarm will be the collaboration of marketing, product, design, and engineering to ensure that users have a consistent brand and product experience.
Vision
In progress.
Swarm Participants
Swarm channel: #24-onboarding
Requirements
Create onboarding flow mockups
As we define the brand tone of voice, make sure this is reflected in the on boarding experience.
Goals & Implementation Plan
Minimum Viable Product
Goal Date:
Description:
Iteration 1..N
Goal Date:
Description:
Supporting Role Communication
Post-Mortem
Copyright
Copyright and related rights waived via CC0.
The text was updated successfully, but these errors were encountered: