►
Description
Decentralized apps are still apps but there are key differences as well which any app designer needs to understand. Onboarding into a token-based ecosystem. Requesting permission for transactions. Handling wait times and confirmation finality. All of these are unexpected for users and, thus, represent key friction points in their interactions.
In this event, we covered the full spectrum of what a designer or product person or developer needs to understand the unique world of creating decentralized applications. We'll start high level and then make our way into more specific case studies of design interactions.
**About the Blockchain Onramp Series**
Blockchain Onramp is a series of events covering the full spectrum of knowledge necessary to operate effectively within the blockchain ecosystem as a designer, developer or product person. After participating in these events, you should be able to take your functional expertise in any of these areas and apply them to blockchain projects.
We are doing this to provide a key -- and currently missing -- plain-English onramp for people of all functional experience who are interested in building real businesses on this new technology.
The format of each event may differ slightly, but they will be a combination of expert talks and discussions with industry practitioners.
The rough Blockchain Onramp Series roadmap is:
+ Product Series: Ecosystem, DApps, and Strategy
+ Design Series: Onboarding UX, Best Practices
+ Development Series: Developer stack, Building on TestNets, Security, Best Practices
+ Startup Series: Marketing, Business Models, and Fundraising
--- ABOUT THE SPEAKER ---
Erik Trautman leads operations at NEAR Protocol, which is a scalable mobile-first blockchain. He has a long history in technical education: he started in market analysis on Wall Street in 2007, created the popular Odin Project in 2012 and ran Viking Education as its CEO until its acquisition in 2017.
Follow the latest from NEAR Protocol on,
Discord: https://near.ai/discord
Medium: https://near.ai/medium
Twitter: https://near.ai/twitter
GitHub: https://near.ai/github
A
A
So
for
today,
basically
we're
talking
about
design-
and
this
is
really
designed
to
be
an
overview
of
the
design
of
applications.
I'll
try
not
to
overuse
the
word
and
so
basically
what
what
a
users
actually
care
about.
They
don't
care
about.
Blockchain
at
all.
We
were
talking
about
this
a
little
bit
beforehand:
users
don't
care
other
businesses,
don't
care,
nobody
actually
cares,
and
so,
if
there's
one
thing
that
that
you'd
walk
away
with
it's
probably
it
should
be
the
knowledge
that
that's
that
that's
the
truth.
A
The
fundamental
truth
is
that
you
know
remember
everything
is
about
the
user.
It
doesn't
actually
matter
what
platform
we're
talking
about.
It
doesn't
matter
what
app
we're
talking
about.
They
don't
care
if
they
have
a
problem,
they
want
to
get
it
solved
fast
and
cheap.
So
why
is
it
worth
actually
talking
about
this?
Because,
where
we
are
in
the
industry,
right
now
is
we're
still
very,
very
early,
we're
still
in
the
innovators
face.
You
know
we're
still
in
the
phase
where
people
are
willing
to
go
through
all
kinds
of
difficulty.
A
You
need
to
really
focus
on
design
thinking
to
begin
moving
across
that
gap,
certainly
to
get
to
the
big,
be
quote
big
scary
chasm.
That
gets
you
into
the
into
the
early
majority,
but
we
aren't
even
close
to
that
I
mean
that's
yours,
that's
years
away.
The
other
reason
on
the
human
side,
so
Sarah,
Baker
Mills,
is
the
design
lead
at
consensus,
which
is
the
etherium
product,
studio
and
venture
studio,
and
one
of
the
things
that
that
she's
talked
about
is
that
Trust
is
very
important
and
I'll
talk
about
that
a
little
bit
later.
A
One
of
the
reasons
why
it's
so
valuable
is
it's
not
just
a
commodity
compute
for
them,
but
it's
a
it's
a
it's
a
compute
platform
that
actually
provides
access
via
primitives,
two
very,
very
important
things
to
users
right
their
money,
their
identity,
their
data
and
their
their
health
information,
and
you
know,
there's
a
lot
of
stuff
that
you
can
put
on
the
blockchain
that
that
we
need
to
be
stewards
of,
and-
and
this
is
even
more
so
unboxing
than
most
other
other
industries
or
most
other
areas.
And
so
that's
why
this
is
also
really
important.
A
So,
as
far
as
today
goes
there's
a
lot
of
actually
a
lot
of
different
scopes
that
we
could
talk
about
when
we
say
design
so
I
kind
of
want
to
kick
off.
Just
just
just
get
everyone
on
the
same
page,
so
user
facing
design
is
sort
of.
What's
maybe
considered
traditional
design
right,
it's
its
users
using
your
apps.
We
also
obviously
design
is
use
in
a
technical
context
too,
because
you
have
technical
systems
design
and
then
you
know
in
both
of
these
contexts.
A
You
have
design,
we
talked
about
design
patterns
and
things
like
that
today
is
much
more
about
the
user
facing
side
than
the
technical
side
and
but
they're
not
actually
they're.
Not
she
completely
separate,
especially
in
something
as
technical
as
blockchain,
where
your
user
facing
design
should
actually
be
informing
your
technical
design
and
your
technical
design
should
be
informing
your
user
facing
design.
I
mean
it's
it's
a
feedback
cycle
in
the
end
of
the
day.
A
What's
going
to
win
is
what
the
user
wants,
but
obviously
we
have
to
operate
within
constrained
environments
that
are
governed
by
the
technology
along
the
way,
and
we
need
the
designers
to
carry
the
carry
the
standard
and
and
push
forward
with
what
the
users
actually
wanted
to
be.
The
voice
of
those
users.
A
So
just
kind
of
a
note
of
this
is
specifically
addressing
maybe
lower-level
platforms,
so
less
on
the
DAP
side
more
on
the
platform
side.
But
you
know
there
really
are
two
constituencies
for
platforms
as
well.
You
have
the
the
app
builders
and
then
you
have
the
app
users,
so
we
talked
about
you
know,
basically,
there's
a
difference
between
developer
experience
and
user
experience
and
it's
great
to
design
for
end-users.
Everyone
loves
that
designing,
for
developers
is
much
more
challenging.
There's
a
lot
more
text
involved,
but
it's
equally
important.
A
There
is
a
there's,
a
talk
that
I
gave
a
number
of
weeks
ago
about
developer
experience,
which
is
maybe
worth
checking
out
if
you're
interested
in
that,
but
for
today
I
will
stick
with
the
sexy
stuff,
uh-huh
and
specifically
again
talking
about
end-user
design
with
with
a
lot
of
sort
of
using
kind
of,
in
the
same
way,
user
experience
as
well
again
that
there
is
a
difference,
but
that's
you
know
kind
of
the
way
that
I'm
gonna
be
framing
things.
So
what
is
actually
user
experience?
In
the
end
of
the
day?
A
It's
actually
the
entire
experience
of
the
person
who's
using
the
applique
and
some
of
the
metrics
that
we
tend
to
use
are.
Is
it
easy
and
is
it
pleasing?
Is
it
is
it?
Is
it
fun?
Is
it?
Is
it
enjoyable
to
use,
there's
a
difference
between
the
interface
and
the
experience,
so
they
often
get
conflated
UI
versus
UX
user
interface
is
actually
generally
just
the
page
or
or
the
screen,
or
the
thing
that
you're
interacting
with
in
the
moment,
whereas
the
experience
again
is
an
entire
journey.
A
So
one
of
the
typical
examples
is
that
you
know
you
have
a
user
interface.
You
have
the
old
Heinz
ketchup
bottles
are
optimized
for
user
interface,
they're
beautiful
they
don't
work,
you
tip
them
upside
down.
Nothing
happens
unless
you
know
the
trick
where
you
hit
the
number
and
then
that
now
they
have
the
the
new
squeeze
bottles
which
don't
look
like
anything
in
particular,
but
you
know
they
in
theory,
work
unless
you've
tried
to
squeeze
them
really
hard,
and
then
it
all
shoots
out
the
bottom,
and
then
it
doesn't
matter
anyways
there's
also.
A
We
talked
about
a
lot
about
usability
and
usability
is
a
little
bit
more.
Let's
call
it
the
science
of
the
science
of
UX.
Maybe
again,
these
terms,
I'm
gonna,
be
kind
of
using
them
fast
and
loose
here.
Purists
will
take
me
to
task,
but
in
the
end
of
the
day
you
can
kind
of
think
usability
is
this?
Is
the
science
it's
it's?
What
we
put
metrics
on,
we
track
it
in
the
end
of
the
day
we
want
to
have.
We
want
to
let
the
user
achieve
their
goal.
A
You
know
with
with
measurable
effectiveness,
efficiency
and
satisfaction
and
user
experience
again.
There's
this
element
of
joy.
This
is
you
just
a
qua
that
that
often
comes
with
it
that
that
we
also
want
to
pay
attention
to,
because
you
know,
if
you're,
only
focusing
on
the
the
type
metrics.
Sometimes
you
miss
what
actually
makes
apps
truly
enjoyable
to
use
so
again,
UX
is
in
fact
the
full
journey.
A
So
as
far
as
the
industry,
today,
it's
not
great
so
this
this
tweet
was
from
middle
of
the
year,
and
you
know
it's
the
user.
Experience
is
just
it's
hard
and
it's
not
necessarily
some
of
it
is
a
technologically
constrained,
and
some
of
it
is
designer
constraint.
You
know
there
are
a
lot
of
technical
projects
that
haven't
been
prioritizing
design.
A
We
were
talking
about
the
prioritization
of
design
before
this,
and
you
know
there's
there's
a
lot
of
room
to
move
forward,
so
for
me
in
particular,
especially
for
today
everything
that
I'm
describing
I
didn't
make
up
any
of
this.
This
is
really
relying
on
a
lot
of
the
information
that
some
of
the
real
the
visionaries
in
the
industry
have
put
forward.
We
have
we
have
a
number
of
these
folks,
theorem
has
been
big.
Consensus
has
been
begging.
A
Coin
lists
have
been
big
and
Sarah
Gregory
actually
from
coinbase
was
with
us
and
maybe
a
couple
months
ago,
giving
a
fantastic
talk
on
user
experience.
So
I
want
to
I
want
to
acknowledge
that
there
there
are
some
diagrams
and
things
like
that
as
well.
That
I'm
gonna
show
that
that
are
actually
from
these
folks
as
well,
so
just
want
to
give
them
upfront
credit
for
what
they've
done
and,
in
the
end,
I'll
be
encouraging.
A
You
guys
to
follow
them
as
well,
but
in
the
end
of
the
day,
what's
kind
of
cool
about
this
is
there's
so
much
white
space
right
now
that
everybody's
trying
to
figure
it
out.
Nobody
has
this
nobody's
nailed
this.
There
are
so
many
new
patterns
that
we
have
to
walk
through
that
we
have
to
figure
out
that
we
have
to
test.
The
technology
is
changing
so
fast
that
it
isn't
like
this.
Is
you
know
all
the
medium
posts
have
been
written?
A
All
the
guides
have
been
written,
everything's
been
figured
out,
it's
totally
the
opposite
and
what's
cool
about
that,
is
that
everybody's
really
open
to
collaboration.
So
if
you're
interested
in
participating
in
design
or
if
you're
just
interested
in
learning
about
design,
it's
actually
it's
a
two-sided
conversation.
It's
not
people.
You
know
on
the
stage
talking
down
it's
very
much
a
collaborative
thing,
a
lot
of
it
takes
place
on
Twitter
and
and
on
medium
and
on
the
podcasts
and
at
conferences.
But
it's
it's
definitely
an
open
conversation.
A
So
what
I
wanted
to
cover
today
is
basically
just
kind
of
the
high
level
of
what
what
is
this
decentralized
app
space
talk
about
some
general
principles
of
design,
I
won't
I,
won't
belabor
everything
that
most
of
you
might
be
familiar
with.
Talk
about
designing
on
blockchain
in
particular,
as
I
mentioned
a
little
bit
about
designing
for
trust
and
then
kind
of
wrap
things
up
and
then
at
the
end.
Actually,
what
I'd
like
to
do
is
you
know
if
we
with
the
folks
who
are
here
is
sit
down
and
have
a
bit
of
a
chat?
A
And
you
know
you
guys
are
welcome
to
stick
around
for
sure.
So,
just
just
again,
quick
benchmarking.
What
is
a
regular
app?
We've
all
used
them,
it's
an
interface,
it's
a
front-end
that
gets
served
from
a
server,
that's
usually
probably
cloud
hosted
on
Amazon
or
Microsoft
or
Google
cloud,
and
it's
it
sits
on
top
of
the
database
where
the
data
gets
stored.
A
These
are
all
things
that
we're
hopefully
well
familiar
with,
and
then
the
question
is:
what's
the
difference
when
you
begin
to
decentralize
something,
what
does
it
mean
to
put
it
on
the
blockchain
and
ultimately,
the
the
blockchain
still
gets
accessed,
typically
through
the
browser,
because
this
is
where
the
users
are,
but
it
takes.
The
typical
interactions
with
the
blockchain
requires
some
sort
of
user
permission
about
a
little
bit
through
the
wallet
and
in
it.
A
So
the
other
thing
I
want
to
note,
give
a
talk
about
on
this
one
last
week,
which
is
basically
that
decentralization
is
not
pure
or
it
can
be
pure,
but
it
doesn't
have
to
be
pure.
It
is
a
spectrum
and
we
talked
about
it
very
binary,
but
it's
not
it's.
It's
definitely
a
spectrum
on
one
end
of
the
spectrum.
A
You
have
the
the
adapts,
the
true
decentralized,
you
know,
decentralize
all
the
things
apps
and
on
the
other
side,
you
have
this
centralized,
but
there's
this
big
middle
ground
in
the
middle,
where
really
it's
just
businesses
want
to
use
things
that
work
and
they
might
actually
the
best
solution
might
actually
be
on
a
blockchain.
It
might
not
be
on
the
blockchain
half
the
solution
might
be
on
the
blockchain
half.
The
solution
might
not
remember.
A
So
what
what
actually
do
you
get
when
you're
on
a
blockchain
based
app?
So,
in
the
end
of
the
day,
users
they
own
their
data,
that's
one
of
the
key
fundamental
things:
it's
not
in
your
database.
It's
on
the
blockchain
and
the
blockchain
is
everybody's
database.
In
order
to
access
that
information,
we
have
to
ask
their
permission,
and
this
is.
This
is
one
of
the
biggest
bedeviled
factors
which
we'll
talk
about
the
the
other.
A
One
is
that
actions
have
costs,
so
we're
not
really
used
to
operating
in
this
world,
where
everything
actually
has
a
cost
to
it,
where
you
have
to
pay
for
every
step
that
you
want
to
do
right,
we're
kind
of
used
to
the
like.
You
know,
build
me
$7
a
month
and-
and
you
know
I'll-
think
about
that
later.
If
you've
interacted
with
Amazon,
you
know
with
the
Amazon
Cloud
you're
probably
used
to
getting
a
metered
bill,
that's
much
more
much
more
fine-tuned,
but
still
it's
not
as
fine-tuned
as
this.
A
This
is
this
is
you're
actually
paying
for
every
single
little
thing
that
you
do
and
then,
of
course,
and
and
often
times,
and
somebody
has
to
pay
that
and
so
often
times
we
end
up
pushing
that
up
to
our
users,
at
least
in
today's
world.
But
the
ideal
world
is
probably
that
we
do
something
very
similar
to
what
we
what
we
do
on
web
2,
which
is
more
hide
that
as
much
as
possible
and
then,
of
course,
there
are
some
new
interactions
and
things
like
that
that
are
being
experimented
with
you
have
token
curated
registries.
A
You
have
sticking
mechanisms
that,
basically,
you
know
people
put
their
money
where
their
mouth
is
the
bet
on
something
or
to
claim
something
or
whatever
it
is
these
in
governance
voting
as
a
part
of
the
protocol.
These
are
all
things
that
users
aren't
really
used
to
paying
attention
to,
and
we're
kind
of,
as
an
industry
I
think
trying
to
push
them
into
some
of
these
new
patterns
and
we'll
and
we'll
see
what
actually
becomes
successful.
But
it
is
a
lot
of
a
lot
of
these.
A
So
what
I
want
to
talk
about
is
is
specifically
some
of
those
things
walking
through
what
the
users
experience
looks
like
in
a
blockchain
based
app
and
basically,
what
the
walls
are,
that
those
put
in
front
of
users
that
maybe
they
didn't
have
in
traditional
apps,
so
one
of
the
key
ones
is
is
is
knowledge.
It's
I
mean
almost
every
decentralized
app
that
whatever
it
is
that
that
you
use
that
you'll
run
into
out
there.
They
have
to.
They
have
some
sort
of
education
problem.
A
Users
have
some
kind
of
knowledge
problem,
because
users
go
in
expecting
nothing
different.
They
go
to
a
website,
they
expect
a
website.
They
expected
the
you
know
e-commerce
sites
to
operate
on
the
same
principles.
They
expect
games
to
operate
on
these
same
freemium
principles
that
they're
used
to,
and
we
have
to
actually
figure
out.
How
do
we?
How
do
we
educate
them?
A
You
know
like
what's
different,
what
does
that
intrinsically
valuable
about
this
thing
that
they
have,
which
is
the
core
value
proposition
of
the
entire
app?
So,
no
matter
what
there's
always
an
education
component,
that's
associated
with
this
and
education
is
really
difficult
for
users,
because
unless
they
are
literally
going
in
asking
to
be
educated,
what
they
really
want
to
do
is
is
the
thing
that
they
wanted
to
do
not
like.
A
They
want
to
learn
as
little
as
possible
to
get
to
that
thing,
and
so
a
lot
of
apps
will
provide
way
too
much
education,
lots
of
big
walls
of
text
and
and
trying
to
inform
the
user
of
all
the
things
that
are
about
to
happen
all
the
time
and
a
and
then
on
the
other
side.
You
have
apps
that
that
don't
really
do
a
good
job
of
that
or
are
optimizing
for
power
users
at
the
expense
of
new
users.
A
A
You
know
it's
it's
almost
every
blockchain
based
app
is
going
to
eventually
ask
the
user
for
their
wallet
and-
and
you
know
typically
what
they'll
do
is
they'll,
detect
that
there's
a
wallet
or
well,
the
app
will
usually
need
a
wallet
for
one
of
the
activities
that
they
want,
that
they
want
to
create.
Usually
that
involves
like
creating
a
user's
account
or
signing
a
transaction
of
some
sort,
and
so
users
need
wallets,
and
this
is
totally
new.
A
This
is
not
something
that
users
are
used
to,
and,
and
so
the
very
first
thing
that
you
do-
they
I
took
the
screen
cap
here
from
one
of
the
popular
games.
I,
don't
remember
what
it
was
called,
but
you
know
it's
again.
The
very
first
thing
that
a
lot
of
these
apps
require
you
to
do
is
to
go
and
download
meta
box
or
which
is
it,
which
is
a
wallet
app
and,
and
this
is
a
huge
wall
for
for
lots
of
these
users.
The
other
one
is
ok
great.
A
You
have
a
wallet
now,
what's
inside
of
it
usually
to
interact
with
one
of
these
apps.
You
need
to
have
tokens
how
the
hell
do
you
go
out
and
find
tokens
what's
a
token.
This
is.
This
is
a
huge
pain
for
for
users
if
you've
convinced
them
that
they
want
to
use
your
app
enough
to
download
this
other
apps.
You
know.
Sometimes
this
is
a
reasonably
familiar
pattern.
It's
a
you
know.
Sometimes
you
need
to
download
your
the
zoom
app
to
use
it.
You
have
to
use
video
conferencing
or
something
like
that
right.
A
We're
kind
of
used
to
this
this
this
modality
of
like
ok.
Well,
maybe
we
have
to.
Maybe
we
have
to
download
something
new,
but
then
it's
wait.
What
do
you
mean
and
we
have
to
I-
have
to
like
pay
money
first
to
go,
buy
a
bunch
of
tokens
right.
This
is
a
huge
wall
for
users
and
then
managing
keys.
What
does
it
mean
to
be
a
wall?
Well,
what's
inside
my
wallet,
I
I
have
keys.
What
does
it
mean?
A
What
is
a
key-
and
you
can
kind
of
you
know,
there's
a
little
nugget
of
something
familiar
and
and
keep
your
your
password
secret.
But
what
is
it
key?
What
is
the
difference
between
a
private
key
and
a
public
key
I
mean
I,
didn't
know
what
it
was
for
for
a
long
time.
It
just
didn't
seem
to
make
any
sense.
I
had
no
I
had
no
no
way
of
figuring
out
what
the
actual
difference
was
and,
of
course,
what
happens
if
you
lose
your
keys.
A
What
happens
if
you
have
your
keys
on
your
iPhone
versus
your
your,
your
your
Mac,
you
know
it's,
it's
it's
a
hugely
complicated
barrier
and
then
what
the
fifth
wall
is
permission
its
transactions
right,
because,
okay,
so
now
you
let's
say
you
have
the
wallet,
you
have
the
the
tokens
and
now
the
app
wants
to
do
something.
Well,
the
app
is
gonna.
Ask
you
for
permission
to
do
it
and
a
lot
of
times.
Actually
the
first
thing
that
the
app
will
ask
you
is
is:
can
I
can
I
access?
A
All
this
constant
asking
and
and
and
then
of
course,
when
you
have
transactions
when
you
actually
need
to
do
one
of
these
things,
whether
it's
creating
an
account
or
or
again
having
a
transaction
happen
on
the
blockchain.
You
you
end
up
having
to
ask
permission
for
that.
So
these
are
all
hurdles
for
users
who
they
don't
know
what
the
heck
is
going
on
like.
Why
do
I
have
to
give
you
permission
to
do
these
things,
and
then
gas
is
a
specific
subset
of
these
transactions
right.
So
great
you're
asking
me
for
permission.
A
What
are
all
these
things
that
you're
throwing
at
me?
What
is
the
kid?
What
is
gas,
what
is
the
gas
price
and
the
gas
limit,
and
what
does
it
mean
to
be
faster
or
fast
or
fastest?
This
doesn't
make
any
sense.
So
again,
these
ideas
of
gas
and
speed,
which
this
by
the
way
is
a
very
aetherium,
focused
lens,
but
again
I.
Do
that,
just
because
it's
a
very
common
paradigm
that
people
are
pretty
aware
of.
Newer
blockchains
are
generally
starting
to
try
and
figure
out.
How
can
we
reduce
users
ability?
A
How
can
we
reduce
these
deeper?
You
know
how
can
you
make
even
developers
not
think
too
much
about
these
kind
things,
but
this
is
the
world
we
live
in
right
now
and
then,
of
course,
the
seventh
wall
you've
gone
through
all
this
stuff.
You
finally
done
a
thing,
and
now
you
have
to
wait,
you
have
to
wait
for
it
to
happen.
What
and
how
long
do
you
even
wait?
A
I,
don't
know
why
I
selected
fastest,
but
why
am
I
sitting
there
with
with
this
spinner
on
the
screen
just
going
and
going
and
going
what
does
it
even
mean
to
submit
a
transaction?
Does
that
mean
the
thing
happened,
or
does
it
mean
that
it's
going
to
happen
again?
This
is
not
a
patent
users
are
not
used
to
waiting,
so,
let's,
let's
figure
out
how
to
let's
figure
out
how
to
how
to
address
these
problems
and
scale
the
walls
these
are.
A
This
is
from
a
book
on
medieval
siege
warfare
methods
of
attack
on
the
castles
of
England.
If
you're
curious,
so
I
want
to
back
up
a
little
bit
and
just
just
kind
of
start
from
the
top
again
on
on
design
principles
before
moving
back
into
the
blockchain
specific
stuff,
I
think
you
know
again,
just
the
benchmark.
People
tend
to
tend
to
say
design,
thinking
and
design
process
or
a
kind
of
synonymous
design.
Thinking
has
become
this
very
buzzword,
II,
sort
of
enterprise-e
consultancy
thing,
but
I
like
to
think
of
it
a
lot
more
about
just.
A
What's
your
state
of
mind
when
you're
approaching
these
problems,
are
you
actually
approaching
them
in
a
very
deliberate
user,
focused
manner
or
not?
And
then,
of
course
you
have
a
process,
which
is
what
are
you
doing
to
address
those
problems
in
a
much
more
tangible
way?
And
finally,
you
have
the
toolkit
of
tactics
and
patterns,
and
things
like
that
that
you
can
that
you
can
access
while
you're
trying
to
solve
these
problems
and
process
matters.
A
How
do
you
find
the
users
that
you
think
are?
Maybe
the
user
personas
for
the
app
that
you're
going
to
build
finding
them
as
hard
scheduling
them
as
hard
sitting
down
in
front
of
them
is
hard
and
awkward
and-
and
so
all
of
this
is
super
easy,
especially
for
a
technical
team
to
just
go
out
and
execute
right.
A
A
But
again,
the
next
wave
is
trying
to
bridge
the
gap
into
consumers
or
businesses,
and
things
like
that-
and
you
just
can't
get
away
with
that
anymore,
because
developers
might
you
know
they're,
just
not
the
consumer
so
who
are
our
users?
This
is
one
of
my
favorite
slides
from
Alex
mandus
and
he
gave
it
a
give
it
a
talk.
A
I
think
it
was
in
Toronto,
but
users
do
not
care
about
ether,
they
don't
care
about
backing
up
private
keys
seed
phrases
why
they
can't
use
standard
two-factor,
authentication,
huge,
hex,
strings,
non
simple
user
names
why
they
can't
use
their
credit
card,
why
they
can't
use
the
App,
Store
and
blue,
etc,
etc,
etc.
Right
again,
it's
just
another
flavor
of
users,
don't
care,
and-
and
there
are
multiple
different
types
of
users
as
well-
that
we're
kind
of
thinking
about
that.
We
have
to
serve.
A
There's
there's
the
newbie
on
one
side,
then
there's
the
hardcore
technologists
and
there
are
the
the
decentralize
everything
folks
and
each
one
of
them
is-
is
going
to
come
in
with
a
very,
very
different
frame
of
mind.
And
so
you
know
generally
it's
a
good
practice
to
be
designing
for
the
newbie
first
and
then
providing
some
sort
of
swimlanes
where,
where
the
more
advanced
users
can
actually
siphon
themselves
off,
maybe
turn
off
certain
certain
flows,
certain
you
know
onboarding
type,
stuff
and
and
begin
it's.
You
know
a
fairly
common
practice
and
product
right.
A
Where
you
have
your
power
users,
you
begin
to
you
sort
of
allow
them
to
opt
into
that
process,
but
you
know
the
newbies
don't
care
if
they
don't,
they
don't
care,
but
they
also
don't
know
and
that's
one
of
the
hardest
things
to
balance
so
general
design
principles.
I
would
expect
that
everyone's
heard
about
these
types
of
things
on
the
right.
We
have
dieter
Rams.
A
As
ten
principles,
but
in
the
end
of
the
day,
you
know
follow
expectations
make
sure
that
the
users
expectations
are
met
and
if
you
can't
meet
them,
make
sure
that
you're
setting
them
as
much
as
possible
in
the
right
direction.
Minimize
cognitive
load,
don't
make
me
think,
there's
a
really
good
book
and
I
think
a
series
of
talks
around
don't
make
me
think.
A
That's
one
of
the
fundamental
things
about
users,
don't
make
them
think
don't
make
them
do
anything
that
requires
the
brain
to
turn
on
or
they
will
do
everything
in
their
power
to
avoid
it,
and
then
they'll
act
like
drunk
toddlers
be
consistent,
obviously,
across
across
your
interfaces,
and
also
be
consistent
with
the
patterns
that
they're
used
to
so
you
know
again:
web
2,
we
still
operate
in
a
web
2
world.
We
can't
build
this
thing
from
scratch.
A
Users
are
coming
in
with
their
own
frames
and
you
have
to
kind
of
operate
within
those
frames
and
guide
them
gently.
Don't
let
them
make
mistakes
is
another
one.
Do
whatever
you
can
and
again
we're
we're
dealing
with
sensitive
stuff,
and
it's
very
easy
for
users
to
make
mistakes.
Do
everything
in
your
power
to
make
sure
that
they
can't
make
those
2
mistakes
and,
of
course,
being
unobtrusive
is
one
of
the
hallmarks
of
design
light
touch.
Light
touch
is
worth
a
lot,
so
a
few
things
I
wanted
to
actually
specifically
call
out.
A
A
He
didn't
originate
the
concept,
but
it
kind
of
I
think
because
that
book
was
so
popular
it
kind
of
took
off
from
him
and
then
the
the
HCI
crew
actually
extended
it
beyond
what
he
what
he
originally
intended
it
to
be,
but
anyways
in
human,
human
computer
interaction,
an
affordance
is
really
considered
to
be
kind
of
like
when
you
look
at
something.
What
do
you
expect
to
be
able
to
do
with
it?
A
So
one
of
the
examples
that
they
give
is,
if
you
walk
into
a
room
with
a
chair
and
a
softball,
how
do
you
know
which
one
to
do
what
I
want
to
throw
and
which
one
to
sit
on?
You
know
what
that
kind
of
extends
to
in.
In
practical
terms,
it's
a
very
it's
a
really
really
valuable
concept
because
right
it's.
A
This
is
harder
than
it
actually
sounds,
and
then
the
other
is
don't.
Let
them
do
something
bad,
so
so
I
guess
I
can
think
of
a
developer
example
the
top
of
my
head,
but
did
you
know
there
are
things
like
api's
that
have
that
have
really
problematic
interfaces
where
they'll
bill
sort
of
expose
methods
to
developers
that
actually
have
no
business
being
exposed?
And
it's
like
well,
you
shouldn't
expose
them
in
the
first
place
and
and
I
think
that
applies
in
some
of
these
experiences.
A
Like
don't
let
users
do
something
stupid,
it's
kind
of
what
it
comes
down
to
don't
let
them
do
things
that
they
shouldn't
be
able
to
do
another.
One
is
controlling
guidance.
Users
always
want
people
want
to
feel
like
they're
in
control
and
the
way
they
feel
like
they're
in
control
is
that
they
know
where
they
are.
They
know
where
they
can
go
and
they
have
a
sense
of
where
you
want
them
to
go
right.
That's
those
are
kind
of
the
three
components,
and
that
applies
to
navigation.
A
That
applies
to
you
know
the
progress
of
things
that
are
going
on.
Like
I
said
you
know
the
waiting
that'll
come
up.
Is
you
know
you?
You
will
always
want
to
know
what
status
like
what's
the
status,
where
am
I
right
now
relative
to
where
I
could
go
and
where
you
want
me
to
go,
it's
really
important
and
that
actually
is
one
of
the
concepts
that
I
don't
see.
A
lot
in
in
a
lot
of
apps
right
now
is
I.
Think
people
tend
to
get
a
little
bit
lazy
around
that
because
it
it
it's
it's.
A
You
said
in
sort
of
the
agile
approach.
People
tend
not
to
put
them
in
stories
because
they
don't
really
make
very
sexy
stories
to
have
a
little
progress,
status,
bar
or
or
a
little
pop-up
notification
with
with
with
network
status,
and
things
like
that.
But
it's
super
important,
because
if
people
feel
lost
then
then
they
get
very
unhappy
and
they
leave
don't
make
me
think
we
were
talking
about
that
again
worth
it
worth
it.
It's
worth
like
painting
on
the
wall
in
front
of
you.
So
so
you
know
it's
great.
A
If
and
I
actually
want
to
emphasize
it's
good
to
be
opinionated
too,
you
can
be
opinionated.
Providing
users
with
with
options
to
dig
deeper
is
great,
but
it's
okay
to
pare
back
the
interface.
It's
okay,
not
to
explain
every
little
thing
to
them:
it's,
okay,
not
to
give
them
all
the
choices.
It's
okay,
to
bury
some
of
those
choices.
Sometimes
simplicity
is
ultimately
going
to
be
a
better
option
for
you
in
general.
A
So,
let's
move
into
actually
the
high-level
general
principles
of
design
are
wonderful
but
but
well,
how
does
that
apply
to
blockchain?
So
again
we
have
the
wall.
Winter
is
coming
and
in
April
and
yeah
so
knowledge,
while
it's
acquiring
the
crypto
managing
the
keys
asking
people
for
permission
talking
about
gas
and
speed
and
then
of
course,
waiting
around
so
the
first
wall
is
educational
content.
Again
our
ways
that
we
can
get
beyond
that,
so
one
of
the
one
of
the
easiest
ones
is
to
educate
slowly
instead
of
fast.
A
You
bury
it
in
one
of
these
little
one
of
those
little
little
eye
circles
right.
So
in
the
picture
there,
it's
basically
you
you
kind
of
have
one
of
those
little
circles
and
you
hover
over
it,
and
then
it
pops
up
a
little
bit
more
information.
So
so
again,
it's
allowing
people
to
opt
into
the
education
as
much
as
possible,
well-well-well
hiding
them,
hiding
it
from
them
in
the
critical
flow
of
the
application,
and
then,
of
course,
educating
plainly
is
is
obvious
to
say
but
hard
to
do
in
practice.
How
can
we?
A
How
can
we
change
these
concepts
into
language?
That's
familiar
to
them
and
there's
a
we're
all
trying
as
hard
as
we
can
it's
great
to
say
really
hard
to
do
so,
of
course,
the
second
wall
is
wallets
and
if
you're
a
wall
developer,
you're
gonna
be
paying
a
lot
of
attention
to
this.
If
your
ad
app
developer,
you
just
have
to
be
very
aware
of
what
does
it
look
like
when
your
user
is
moving
into
and
out
of
a
wallet
flow?
So
what
just
a
few
quick
things
up
front
are:
allow
multiple
wallets.
A
If
you
can
write
your
users,
aren't
all
gonna
be
using
that
a
mask
your
users.
Aren't
all
gonna
be
using
the
default
wallet
for
your
right.
The
you
want
to
have
options
that
are
going
to
support
the
proportion
of
users
that
are
gonna,
make
you
successful
engineering
resources
versus
users,
always
a
challenge,
but
you
know
you
want
to
give
people
options.
A
Priming
is
something
that's
actually
gonna
come
up
a
lot,
and
so
this
is
this
is
the
idea
that,
when
you
move
into
a
new
flow
that
the
user
hasn't
seen
before
or
or
or
or
if
you're
leaving
the
garden
of
your
user
experience
right,
you
have
control
within
your
app.
You
don't
have
control
outside
the
app
for
the
most
part.
Today's
web
experiences
are
all
within
the
app,
so
you
have
full
control.
A
Crypto
experiences
are
almost
inverted
in
the
sense
that
you
have
to
send
the
user
all
over
the
place
before
they
the
before
they
circle
back.
The
wallet
is
one
of
the
biggest
examples
of
that.
So
if
your
wallet
is
a
web
extension
and
a
Chrome
extension,
for
instance,
for
instance,
like
meta
mask,
do
you?
How
do
you
prime
them
for
what's
about
to
happen?
A
Because
if
they,
if
the
window
just
pops
up-
and
it
says
you
know-
does
the
app
have
permission
for
that-
leh
mean
that
that's
basically,
a
pop-up
people
are
trained
to
avoid
pop-ups
people
are
trained
to
hate
pop-ups,
and
so
what
you
can
do
basically
and
in
the
example
that
that
that's
here
is
something
that's
in
an
iOS
app,
which
is
basically
first,
it's
asking
the
user.
Do
you
want?
A
So
a
lot
of
apps
seem
to
actually
be
very
aggressive
about
getting
in
front
of
you
with
the
wallet
and
saying
hey,
you
need
to
have
a
wallet
hey,
you
need
to
have
an
account.
What
can
you
do
to
actually
push
that
back?
What
can
you
do
to
do
as
much
as
possible
for
the
user
before
they
actually
have
to
have
a
wallet,
because
the
more
value
you
can
provide
them
ahead
of
time?
A
So
again
as
part
of
this
idea
that
you're
handing
off
the
user
experience
to
someone
else,
there
are
things
that
you
just
you
kind
of
want
to
do
with
a
wallet
like
you,
you
would
love
to
have
the
wallet
pop
up
and
say
something
nice
about
your
and
from
your
app
that
says:
hey!
Don't
worry
like
we're
just
we're
just
here
to
help
and
like
you
know
that
this
transaction
is
gonna,
do
XYZ,
but
there
are
some
security
reasons
why
they
don't
allow
that.
So
again,
it's
just
the
sort
of
like
you
know
it.
A
This
kind
of
relatively
cold
meta
mask
style
pop-up,
which
is
which
is
in
front
of
them
and
again
so
your
users.
You
just
have
to
be
aware
that
your
users
are
gonna,
have
that
jarring
experience
so
as
far
as
acquiring
crypto
this
this
one's
tricky,
because
this
is
probably
the
furthest
that
your
users
are
going
to
go
away
from
you
and
the
least
likely
that
they're
going
to
find
their
way
through
it
and
come
back,
and
we
don't
really
have
very
good
solutions
for
this
again.
A
What
one
thing
that
you
can
do
certainly
is:
is
you
can
at
least
allow
multiple,
multiple
currencies?
If
this
is
super
app
dependent,
but
obviously
users
will
have
multiple
currencies
in
their
wallet.
They
might
have
Bitcoin
and
ether
they
might
have
like
coin
and
dogecoin
they.
You
know
who
knows
and
the
more
that
you
can
do
to
support
them,
and
this
is
something
that
would
come
up
in
user
testing
and
user
research.
How
many
coins
do
you
have?
Do
you
have
coins
things
like
that?
A
Allow
multiple
again
priming
comes
up,
which
is
just
pretty
clear
as
much
as
you
can
like,
like
give
them
that
on-ramp.
Let
them
know
that
you're
about
to
slingshot
them
through
the
through,
through
it's
kind
of
a
weird,
difficult
experience
which
might
actually
take
them
a
long
time,
and
you
have
to
figure
out
how
do
you
hook
them
and
snag
them
and
bring
them
back
and
give
them
value
and
I
don't
mean
snag
them
in
like
a
negative
way.
A
I
mean
snag
them
with
with
something
that
they
want,
because
you're,
adding
them
value
and
then
again
in
the
bottom
is,
is
stepping
back
and
saying:
do
you
do
you
need
this?
Do
you
need
crypto?
How
long
can
you
wait?
How
can
how
much
can
you
push
off?
How
much
can
you
foot
the
bill,
for
instance,
if
you're
able
to
if
you
know,
you're
able
to
monetize
a
user
later
through
some
other
means?
A
You
footing
the
bill
on
any
of
this
stuff,
because
if
you,
if
you
aren't
careful
about
you,
know
that
the
the
development
side
you
can
have
people
just
you,
know,
boss
your
server
and
basically
run
down
all
your
balances.
And
then
you
have
no
money
left
so
so
they're
real
things
you
have
to
keep
track
of.
But
again
they
welcome
to
the
world
right.
This
is
we're
all
world
we're
all
grown-ups,
that's
how
it
works.
You
have
to
be
careful,
but
I
mean
what
matters
most.
Is
your
users
experience?
Oh,
and
then
there
was
a.
A
There
was
a
service
that
I
found
out
about
the
other
day
called
wire
wood,
which
is
basically
I.
Think,
basically,
what
they're
trying
to
do
is
is
provide
as
much
of
an
aggregation
of
the
going
out
and
getting
crypto
experience
as
possible.
It
seemed
pretty
interesting,
so
there
are
people
who
are
converging
in
on
this
problem
space
of
trying
of
trying
to
create
as
good
of
an
experience
as
possible.
You
know,
if
you
want
you,
can
you
can
look
them
up?
A
I'm,
not
I
only
had
a
brief
brief
bit
of
time
to
check
them
out,
but
so
people
are
people
are
starting
to
figure
that
out,
but
it's
still
a
hard
problem.
I
mean
it'll,
be
wonderful
if
you
just
had
a
pop-up
that
was
just
enter
your
credit
card
information
at
the
very
least
enter
your
credit
card
information
and-
and
you
know
like
by
some
crypto
right
now,
right,
obviously,
and
so
I
think
we're
trying
to
get
as
close
as
possible,
but
we're
just
not
there.
Yet
key
management
is
another
difficult
one.
A
In
a
lot
of
these
cases,
which
is
you
know,
your
users
are
gonna-
have
to
deal
with
keys
and
you
want
to
try
and
abstract
as
much
as
you
can
away
from
them,
and
how
do
you
do
that
in
a
way
that
also
make
sure
that
they're
secure
that
they're
aware
of
what
they're
doing-
and
this
is
going
to
be
just
a
fundamental
struggle
that
you're
going
to
have
so
you
know,
analogies-
are
useful.
There's
there's
an
interesting
post
from
IDEO,
where
they're
talking
about
different
analogies
for
the
wallet.
A
That's
what
some
of
those
some
of
those
little
icons
are.
You
know
is
a
wall
in
a
trophy
case:
does
it
provide
kind
of
a
backstop?
Is
it?
Is
it
a
spellchecker?
Wear
kind
of
it
would
be
sort
of
spell
checking
people's
hashes
and
things
like
that
again,
it's
just
a
design
pattern.
Preventing
stupidity,
though,
is
your
job.
Like
your
users
will
do
dumb
things,
they
will
try
to
do
every
dumb
thing.
That's
in
that's
possible.
They'll
they'll
do
deliberately
dumb
things.
A
They'll
do
drunk
toddler
things
and
they'll
lose
their
keys,
and
so
everything
possible
that
you
can
do
to
make
sure
that
it's
just
not
actually
an
option
for
them
that
the
more
successful
they're
going
to
be
because,
as
we
all
know,
if
one
user
out
of
a
thousand
has
a
rotten
experience,
they're
gonna
torpedo
your
app
with
with
you
know
bad
reviews,
and
things
like
that,
and
it's
just
gonna
take
you
down.
So
you
know
you're
yeah.
A
Showing
consequences
is
another
one
where
it's
it's
a
lot
of
users
come
in,
not
knowing
what
these
things
are
right.
So
what
does
it
mean
if
they
have
a
non-functional
token
on
their
wallet,
and
you
know
I
leave
it
up
to
you
guys
to
figure
out
how
do
you
educate
them
with
the
idea
that
you
should
try
to
minimally
educate
people?
A
But
you
know
they're
gonna,
wonder
when
they
log
in
on
their
computer,
why
they
don't
have
the
thing
if
they
have
it
they're
not
super
familiar
with
the
fact
that
wallets
are
generally
local,
so
you're
you're
gonna
have
to
figure
out
how
do
we?
How
do
we?
How
do
we
show
that
and
then
also?
How
do
we
show
that
that
there's
value
in
that
too,
so
it's
consequences
on
one
side,
it's
the
carrot
in
the
stick,
but
also
what
the
value
is
of
having
these
of
having
these
individual
things
permissions.
A
So
priming
priming
is
one
of
the
most
useful
tools
that
you
have
again
try
to
on
ramp
them
when
it's
in
your
when
it's
in
your
experience
before
get
their
consent
before
using
your
words
and
then
they're,
much
more
likely
to
actually
step
their
way
into
the
into
a
successful
transition.
And
then,
of
course,
you
know
in
any
case,
where
there's
permissions
being
asked
there
were
things
like
that.
Just
do
the
minimum,
it's
very
easy
to
get
to
go
to
get
developer
sloppy.
You
know
where
you
kind
of
permissions
equal
all
whatever
it
is.
A
That's
the
ultimately
that's
going
to
be
a
problem
so
as
much
as
you
can
try
to
keep
the
stakes
low
and
try
to
let
the
users
know
when
the
stakes
are
low
and
when
the
stakes
are
high,
gas
and
speed
is
hard
and
we're
still
trying
to
figure
out
what
the
right
patterns
are
again.
This
is
a
very
aetherium
centric
view
of
the
world,
but
it
sort
of
applies
in
a
lot
of
different
ways
to
different
chains.
A
You
know
in
the
end
of
the
day,
usually
the
more
gas
you
pay
for
something
or
the
more
you
pay
for
something
the
faster
it
could
get
done,
or
it's
both
the
faster
end
with
the
highest
highest
likelihood.
It'll
get
done.
Users
aren't
really
used
to
that
paradigm.
There
used
to
well,
everything
is
free
and
it
works.
I
mean
it's
free,
it
works
and
it
works
immediately,
and
so
one
way
that
you
can
do
that
is
actually
you
could
just
hide
gas
I
mean
you
could
literally
just
not
allow
them
to
enter
gas.
A
Like
imagine
imagine
if
there
was
a
world
where
it
was
just
there
was
a
default
amount
of
gas
and
it
just
happened
behind
the
scenes.
Maybe
that's
less
realistic
for
gas,
but
more
realistic
for
something
like
speed
where
it's
like.
Why
do
I
care
like
what
is
this
low
average
fast
speed
actually
mean?
Maybe
try
hiding
that
try,
try
seeing
if
users
care
and
making
that
an
optional
thing
you
know
hey.
A
Would
you
like
to
adjust
your
speed
sort
of
thing
if
it's
not
necessary,
it's
not
necessary
and
then
waiting
waiting
icons
are
becoming
an
art
in
this,
but
they're
not
enough.
One
of
the
key
key
things
is:
is
any
asynchronous
process
or
semi
asynchronous
process?
Don't
block
the
UI?
We
still
do
it.
We
still
block
me.
We
still
make
the
user
sit
there
staring
at
an
icon
with
no
idea
how
much
longer
it's
supposed
to
happen.
A
So
this
goes
right
back
to
you
know
what
I
was
talking
about
originally
about
giving
your
users
control
and
making
them
feel
like
they're
in
control,
make
sure
that
they
always
know
what
the
status
is
of,
where
they
are
relative
to
where
they
should
be
relative
to
where
you
want
them
to
be.
You
know
again
1
2
3
it
should.
It
should
be
every
single
page,
every
single
possible
path,
the
user
has.
They
should
always
have
those
three
lifelines,
and
one
of
those
is
also
showing
liveness.
A
That's
that's
something
that
maybe
they're
the
users
are
used
to.
Maybe
not
you
have
to
figure
out
how
to
how
to
fit
that
into
the
frame
that
they're
expecting,
but
the
worst
thing
that
you
can
have
as
a
user
is
sit
there
and
ask
yourself
that
question
like
so.
Did
it
work?
Do
I
refresh
the
page?
Do
I
refresh
the
page?
Is
a
really
dangerous
thing
for
you,
so
the
more
that
you
can
do
to
say:
hey,
yes,
we're
working!
This
is
roughly
how
long
we're
expecting
it
to
take.
A
It's
taken
this
long
networks,
good
we're
cool.
You
know
like
the
more
that
you
can.
You
can
make
sure
the
user
hat
is
comfortable
and
is
able
to
wait.
The
better
off
you're
gonna,
be,
but
even
better
is
don't
make
them
wait
at
all
right.
So
so,
if
it's
an
asynchronous
thing
figure
out,
how
can
you?
How
can
you
get
them
doing
something
else,
and
then
circle
back
and
one
of
the
things
crypto
kiddies
will
do
you
know
if
you're
doing
a
transaction,
they'll
they'll,
send
you
an
email
when
the
transaction
is
ready?
A
A
We
have
their
their
data,
their
identity,
their
wealth
in
our
hands,
and
so
it's
it's
on
us
to
use
that
responsibility
and
make
sure
that
they
don't
make
bad
decisions,
but
also
that
they
learn
through
not
making
bad
decisions
that
you
don't
encourage
them
to
do
things
like
copy
paste,
private
keys
and
stuff
like
that,
because
then
you're,
creating
bad
behavior
for
from
users
for
all
sorts
of
other
scenarios
right
as
stewards.
There
are
a
lot
of
things
that
you
can
do.
One
of
them,
for
instance,
is
just
acknowledging
the
consequences
of
things
where
possible.
A
A
They
will
expect
the
undo
button,
always
they'll
expect
if
they
lose
the
thing
they
can
yell
at
you
and
you'll,
give
it
back.
This
is
how
the
world
works
right
now,
so
they
need
to
know
again.
Ideally
you
figure
out
how
to
how
to
mask
these
things.
The
same
way
we
have
in
in
today's
world,
but
second
best,
is
to
make
sure
that
they're
darn
sure
when
something
is
going
to
be
permanent.
A
They
can
link
it
together
and
and
they
can
find
out
who
I
am
or
even
even
if
it's,
even
if
it's
not
literally
the
same
Keys,
it's
they
can
actually
still
use.
It
takes
very
few
data
points
to
actually
correlate
somebody's
behavior
literally,
you
can
look
at
at
you
know
what
time
of
day
you
log
in
and
what
time
of
day
you
did
certain
things
or
you
know,
geography.
You
know
two
or
three
of
those
points
and
you
have
an
enormous
lehigh
likelihood
that
you
found
the
same
person
using
multiple
different
accounts.
A
So
that's
one
of
them
actually
they're,
really
core
privacy
issues
that
we
have
here
and
so
the
more
that
you
can
make
sure
that
you're
not
actually
that.
But
you
have
to
kind
of
think
through
those
things
for
the
user
and
make
sure
that
you
know
a
ideally
they're,
not
possible,
so
you're
allowing
them
to
use
multiple
keys
on
multiple
apps
or
things
like
that.
But
again,
sort
of
third
best
is
at
the
very
least.
A
They
should
be
aware
of
when
they're
stepping
near
these
land
mines
and
and
when
these
things
are
happening
and
and
that's
again,
sort
of
that
that
design
versus
ethical
security
sort
of
angle,
where
you
just
want
to
make
sure
it,
because
if
they
have
a
bad
experience,
they're
gonna
blame
you
whether
it
is
or
is
not
your
fault
and
then
zooming
out
a
little
bit
so
a
lot
of
times.
It's
easy
to
get
lost
in
the
minutiae
of
specific
interfaces.
A
Specific
toys
toolboxes
things
like
that
and
I
deliberately
tried
to
stay
away
from
tools
and
tool
boxes
in
this
in
this
chat,
but
also
it's
worth
thinking
again
just
zoom
out
a
little
bit.
Sometimes
the
biggest
games
aren't
tactical
they're
they're
strategic
and
what
that
means
is
of
course
process
process
is
worth
it.
If
you
have
the
right
process
in
the
right
mindset,
you
will
you
will
iterate
your
way
properly
in
the
right
direction.
A
Eventually,
and
interoperation
is
something
where
you
know,
maybe
maybe
you
can
solve
some
of
these
issues
by
interoperating
with
different
applications
or
contracts
or
chains,
or
things
like
that,
so
you
don't
always
have
to
do
it
all
yourself.
So
that's
that's
something
that
nobody
else
is
necessarily
going
to
own,
knowing
what's
out
there
to
solve
a
given
experience
problem.
So
knowing
that
there's
a
team
in
consensus
working
on
a
library
that
actually
does
the
thing
that
you're
kind
of
trying
to
do,
but
but
maybe
a
little
bit
better,
is
it's
on
you.
A
So
so
that's
important
to
think
about,
and
then
of
course,
do
you
even
need
a
token?
Is
there
really
any
member
that
might
be
number
one
always,
but
it's
it's.
Do
you
need
a
token
for
your
app?
Do
you
need
a
token?
Do
you
need
to
interact
with
tokens?
Is
crypto
even
the
right
solution,
because
in
a
lot
of
cases
you
know,
ask
the
hard
question:
we've
all
we've,
we've
all
been
done,
that
that
idea
may
is
to
some
degree
or
another
and
and
bounce
away
from
it
yeah
so
I
always
rethink
the
token.
A
A
A
Where
we're
not
throwing
a
bunch
of
stuff
at
the
user
upfront
which
is
funny
because
if
you're
in
a
web
to
designer
you're
like
these
are
obvious,
but
then
you
look
at
crypto
apps
and
you
realize
that
maybe
they're
not
quite
so
obvious
and
then
on
the
third
one
again.
It's
think
about
think
outside
think
think
think
outside
the
the
box
on
the
business
side
right
avoid
foot
the
bill.
A
If
you
can
make
sure
that
the
user
doesn't
have
to
go
through
this
stuff,
and
sometimes
you
magically
solve
experience
problems
with
you
get
to
throw
money
at
solving
experience,
problems
which,
actually,
in
the
end
of
the
day,
should
ultimately
pay
off.
If
you
have
hopefully
done
the
LTV
calculation
properly.
So
as
far
as
you
guys.
A
So
next
week
we
have
a
workshop,
so
it's
gonna
be
a
little
bit
different
I'll
provide
some
context,
but
basically
we're
gonna
be
doing
a
workshop
where
you
actually
get
hands-on.
You
work
in
small
teams
and
you
solve
a
design
problem.
So
it's
something
that
we
can
talk
about
after
this.
But
one
of
the
easiest
ways
to
get
involved
is
to
do
something
like
that
is
to
actually
just
get
your
hands
dirty
and
participate
so
come
to
next
week's
workshop.
A
But
designers
actually
do
have
options
that
the
crypto
space
people
are
actually
putting
out
bounties
for
solving
design
problems
and
even
even
doing
design
research,
so
I
think
it
was
consensus
had
and
and
I
think
status,
which
I
think
it's
part
of
consensus
had
a
number
of
bounties
for
doing
UX
research
for
them.
So
basically,
if
you
did
app,
tear
downs
for
them
and
and
wrote
it
up
in
a
really
nice
way,
they
would
give
you
money.
So
you
can
do
things
like
that.
A
You
can
go
on
the
Explorer,
bounties,
Network
and-
and
you
have
things
like
these
design
contests
or
stuff
like
that,
so
you
can
get
involved.
Even
if
you
don't
know
crypto,
even
if
you
don't
whatever
it
is
right,
there
are
ways
to
get
involved.
Another
one
is
build.
An
app
yourself
do
a
tutorial
like
just
to
get
your
hands
dirty.
It
doesn't
matter
if
you're
technical,
just
you
struggling
to
figure
things
out
and
asking
silly
questions
or
what
you
think
are
silly
questions
have
a
ton
of
value
for
you,
understanding
and
appetizing
for
your
users.
A
Another
one
is
of
course,
more
more
macro.
There's
checking
out
just
web
to
design
systems
are
quite
useful,
so
you
know
you
can
always
go
in
and
envision
has
a
bunch
of
design
systems
listed.
You
know
they.
They
have
like
the
IBM
design
system
and
things
like
that.
But
then
again
you
can
also
go
in
to
get
coin,
which
is
which
is
right
back
in
the
idea
of
of
the
last
one.
I
was
talking
about
the
Explorer
bounties
network.
A
I,
don't
actually
know
what
it's
called,
but
you
can
go
on
this
and
they
also
have
these
sort
of
design
contests
type
deals.
So
there's
a
lot
of
stuff
that
you
can
do
to
dip
your
toes
and
get
ready
for
it
and,
of
course,
follow
people.
You
know
again,
the
conversation
really
takes
place
in
this
space
on
Twitter
on
medium
I
mean
really
I'd,
say:
Twitter
and
medium
are
the
two
big
ones
virtually.
A
Then
you
have
meetups
meetups
and
conferences,
and
you
know
friends
of
friends,
emailing
things
around
and
open
Google
Docs
that
that
people
are
commenting
on
and
random
telegram
groups
that
are
buried
six
hundred
groups
deep,
that
occasionally
service
I,
think
we've
all
been
there
and
three
three
organizations
to
really
take
a
look
at
and
follow
definitely
consensus
and
coinbase
and
then
I
do
a
collab
also
is
doing
work
in
in
the
design
space.
So,
as
mentioned
in
the
beginning,
but
it's
not
over,
we
haven't
solved
it.
We
need
your
voices,
we
need
your
help.