4. Apps and
the current
experience
Today, users interact with a Smart Contract on the Blockchain in
several ways. Check out https://www.stateofthedapps.com/ and
https://dappradar.com/ if you want to play with some examples
Entered directly via a
command line
Rich front endDapp browsers via
Wallets (e.g. Mist)
5. It’s all
about
users
“Giving users easy access to many kinds of digital
assets and, particularly, tokens that are linked to
assets in the real world, is crucial to seeing
blockchain adoption reach the next level”
- Vitalik Buterin, Co-Founder - Ethereum
“The most successful startups focus relentlessly on
connecting with their users and making something
that people want. That doesn’t change just because
some of the code or data lives on a blockchain. We
will only achieve mainstream adoption of
blockchain if we deliver great user experiences.”
- Kevin Kim, Product - Facebook Messenger
11. The
problem
Let’s imagine the
everyday user on a
DAPP.
How would users know
which information is
actually stored on the
blockchain? Peepeth - decentralised ‘twitter’
12. The
problem
On the flip side,
let’s look at user
onboarding.
How would users
know which of their
data will be stored
on the blockchain? WeTrust - lending circles
13. Your
design
challenge:
HMW give users clarity on which
data is sourced from the
blockchain when viewing dapps?
AND/OR
HMW give users clarity on which
data will be stored on the
blockchain when ‘signing up’ for
dapps?
14. Who are
our users?
“In the long run, the
users who will choose a
#dapp and it's
(currently) clunky
limitations, rather than a
flaming fast centralized
version, will do so
because of the value
proposition of
#decentralization”
- Beltran
@lyricalpolymath
15. On-chain
“It will utilise blockchain features like
immutability”
“Is this a public or permissioned
blockchain? Do I really want my data
stored here?”
“Is the data hashed? How can I easily
check and verify?”
Off-chain
“I have to trust a central authority to store
my data safely.”
“The data’s probably not public.”
“It’s not immutable. I know they can
change it if I need them to.”
“It’s not immutable, and can be changed it
or manipulated without my knowledge.”
Dapp designers and developers often make decisions on which elements are on or off
chain, but what does this mean for users? What questions and assumptions do they have?
16. Some
inspiration
Twitter introduced the ‘blue-tick’ or ‘blue
verified badge’ to let people know an
account is authentic.
In their battle to design against misinformation,
Facebook introduced ‘Related articles’.
Interestingly in their testing, they found that
animating the button was 80% more likely to drive
attention and action.
17. Your
design
challenge:(you have 50mins so use time wisely)
HMW give users clarity on which
data is sourced from the
blockchain when viewing dapps?
AND/OR
HMW give users clarity on which
data will be stored on the
blockchain when ‘signing up’ for
dapps?
18. Rule &
Constraints
1. Work in pairs! You have 50 minutes, so plan your time!
2. Take the design prompt any way you want — no further
explanations
3. Your users: Blockchain hobby-ist with some exposure.
Interview at least one user about their needs prior to
design and user-test your solution afterward. Your
research plan is up to you!
4. Final output: 2 minute shareback include supporting
visuals (e.g. user feedback and what you learned
Recommended process:
Empathise
Define
Ideate
Prototype
Test + Refine
10 min
10 min
10 min
10 min
10 min
19. Tools! Ready for a bigger challenge?
Look out for Gen for
‘Advanced-level wildcards’
Need some support?
Look out for Josh for
‘Design-thinking toolkit’
21. Emerging
best
practices
Web3 UX Design Principles by Beltran
1 — (Reading Data) Transparency of
Data Provenance
● Clarify which data comes from
the Blockchain and which
doesn’t
● Clarify the address of the
contract(s)
● Link all Blockchain data to
independent Blockchain
explorers
● Clarify which data comes from
oracle samples
24. 1. Mechanism design meets UX If you're familiar with mechanism design, learn how to
apply concepts from UX like personas, journeys and usability testing. And if you're familiar with UX,
gain insight into what game theory, protocols and tokens mean in the context of users.
2. Onboarding experience for blockchain dapps For anyone who has bought
crypto you’ll know it’s a strange and unfriendly land and you’ve gotta be pretty motivated to get
through those barriers. Look at the user journey and identifying the main barriers as well as identifying
solution for non-coiners not only the crypto savvy
3. Language and metaphor and icons. Coins, tokens, wallets, seed phrases, gas, gwei,
smart contracts, public addresses, block confirmations: this is all new language that new users must
confront and learn to be able to interact confidently with these applications. Famously, the internet had
some of these problems with things like the “@” symbol, “email”, URL, not to mention the introduction
of usernames and passwords to the general public.
Other
design
challenges.
What’s your
fave?
28. Pick them one or pick them all. Not for the faint-hearted!
Small and mighty
How would you design DAPPs
on small Wearable interfaces
(e.g.FitBit, Apple Watch)
Loud and proud
26% of the world population
today are illiterate. Literacy
remains a real problem today.
How would you design DAPPs
for Voice interactions?
It’s natural
Chatbots, conversational UI and
natural language processing are
some of the most exciting areas
of tech today. How would DAPPs
work with these interfaces?
30. HMW give users clarity on which data is sourced from the
blockchain when viewing dapps? Let’s start by gaining empathy...
Empathise 10 min
1. Interview (8 min)
Notes from your interview
“Can you tell me about your last experience using a DAPP?”
“Was it clear which data was from the blockchain? How did that make you feel? What did you do?
Prompts:
Try to dig for stories,
feelings and emotion.
What were their
frustrations? Can you
map our their journey?
Dig deeper - ask WHY
31. Define the opportunity10 min
2. Capture findings (4 min)
Goals and Wishes: what was the user trying to achieve? *use verbs
Insights: New learnings about your user’s behaviours, feelings and
motivations. What’s something you see about your user’s experience that
maybe s/he doesn’t see? What are his/her habits or behaviours when using a
DAPP? *Make inferences and assumptions!
Define 10 min
3. Have a Point of view (6 min)
____________________________________________________________ NEEDS A WAY TO
User’s name
____________________________________________________________ USING
User need or goal
____________________________________________________________
User opportunity / behaviour / habit
(e.g. Jane needs a way to easily verify the data source of a dapp while using her
mobile)
32. Come up with ideas to test!10 min
3. Sketch 8 crazy ideas each to meet your user’s needs, then share with each other (8 min)
Define 10 minIdeate 10 min
33. Make it real for testing10 min
4. Reflect and generate a single idea to test (10 min)
Define 10 minIdeate 10 minPrototype 10 min
Sketch your big idea to test! Make it interactive if possible. Remember to make it VISUAL so users can understand your idea!
34. All feedback is good feedback10 min
5. Share your solution and get feedback (5 min)
Define 10 minIdeate 10 minPrototype 10 minTest + Refine 10 min
What worked...
Questions...
What could be improved...
Ideas..
35. Refine + Shareback10 min
5. Refine your idea and prepare to share your ideas and learnings! (5 min)
Define 10 minIdeate 10 minPrototype 10 minTest + Refine 10 min
Your idea! Your learnings and reflections!
