►
From YouTube: UX Walkthrough - Onboarding MVC
Description
Matej Latin walks through the new MVC prototype for User Onboarding.
A
B
A
A
But
since
then
it'll
just
go
through
the
solution
section
here
on
the
issue,
for
it,
I
gave
a
link
attached
a
linked
to
the
document,
so
I
split
the
solution
into
four
parts.
One
of
them
is
the
actual
user
flow
of
what
the
users
will
go
through
when
they
join
the
new
user.
Onboarding
then
another
one
will
be
to
add.
A
How
do
they
get
back
to
it
and
things
like
that,
then,
is
the
positioning
of
that
helper
and
then
also
I
put
a
lot
of
emphasis
on
the
exit,
interaction,
because
I
think
it's
important
that
this
step.
We
could
collect
feedback
from
people,
but
maybe
this
won't
be
possible
with
the
MVC
version
of
it.
So
I'm
happy
if
it's
not
included
in
the
MVC
buts.
Eventually,
we
should
include
it
because
it'll
help
us
improve
this
this
bit
of
the
product
quite
a
lot.
A
So
this
is
then
the
user
flow
that
I
was
talking
about
and
since
the
last
time
when
I
was
presenting
this,
we
were
thinking
about
designing
these
user
onboarding
flows
for
each
type
of
the
personas
that
we
have
and
we
had
six
personas
at
the
moment.
I
think
we
added
the
designer
persona
recently
as
well,
probably
have
seven
now
since
then
we
simplified
it
a
bit,
because
we
want
to
validate
that.
A
This
type
of
guided
onboarding
will
work
with
the
minimum
amount
of
effort
and
with
the
amount
of
effort
that
can
go
into
a
single
milestone
and
we
can
deliver
it
basically,
and
we
decided
we
won't
do
a
dummy
project.
We
want
to
any
tailored
onboarding
for
personas.
At
the
moment
we
will
introduce
like
quite
a
generic
onboarding
and
we
will
guide
users
through
the
hit
lab
Community
Edition
project.
So
we
will
take
them
to
the
project
overview
repository
overview.
They
will
introduce
them
to
the
commit
screen
and
commit
details.
Stuff
like
that
right.
A
So
I'll
go
through
the
prototype
briefly
in
a
moment
and
then
also
we
will
show
them
how
to
create
a
new
project
and
how
to
invite
their
colleagues
the
newly
created
project.
So
this
is
something
we
feel
we
can
deliver
it
in
a
single
milestone
and
maybe
even
by
the
end
of
this
milestone-
and
we
can
start
learning
from
it
very
quickly.
A
Instead
of
working
on
something
huge,
you
know
tailored
to
personas
and
then
creating
a
dummy
project
and
in
the
end
it
might,
it
might
not
even
have
the
results
that
we're
looking
for
right,
which
is
positive
results.
So,
ok,
this
is
ok.
So
this
is
the
issue
where
we
documented
the
feedback
from
the
user
testing
that
we
did
with
the
initial
prototype
capturing
scheduled.
These
calls
we
wanted
to
have
5
calls
with
5
participants.
A
We
ended
up
having
free
because
I
think
cancelled,
or
something
like
that
she
had
and
I
did
one
user
testing
session
as
well.
It
was
the
first
time
I
got
the
opportunity
to
do
that.
Since
I
joined
his
lap,
I
did
it
in
the
past.
It
was
actually
more
fun
to
do
it
with
Hitler
participants,
because
I
think
we
have
such
an
engaged
community
that
people
are
eager
to
join.
A
So
yeah
thanks
again
to
catch
him,
for
you
know,
scheduling
all
these
calls
and
preparing
this
scenario
and
the
script
on
such
short
notice,
because
we
were
moving
quite
fast
with
this,
but
if
we
go
to
the
prototype,
so
this
is
the
simplified
version
of
that
screen
that
we
initially
had
where
we
had
the
user
choose
among
the
six
personas
we're
basically
just
introducing
the
types
of
helpers
here
and
telling
them.
We
will
guide
you
through
a
guided
tour,
basically
guided
comporting.
Of
course
they
can
skip
it.
A
So
this
is
something
the
tools
will
introduce
to
the
newly
signed
up
users,
but
as
we'll
run
tests
with
it,
it
will
be
only
a
certain
percentage
of
newly
registered
users
at
first
and
see
what
the
feedback
will
be
from
that,
and
it
would
be
only
on
github.com
in
the
first
iteration
and
that's
also
because
we
can't
have
that
coming
project.
Once
we
introduce
that
dummy
project,
we
can
also
introduce
this
in
the
self-managed
instances
as
well
so
yeah.
This
is
very
much
simplified.
A
A
I
can't
see
it
because,
okay
and
yeah,
these
are
the
types
of
helpers
and
with
introducing
them
to
this
screen,
for
example,
and
then
we
guide
them
to
the
repository
and
tell
them
about
the
repository
a
bit
and
to
the
commits
and
again
we
tell
them
about
to
come.
It's
just
a
basic
introduction
of
users
to
our
interface,
basically,
which
I
think
should
be
much
better
than
just
throwing
them
on
a
single
screen
and
having
them
figure
out
by
themselves,
which
is
what
what
we
do
at
the
moment.
A
A
And
then
we
also
go
to
the
issues
and
we
show
them
how
to
filter
the
issues
by
accepting
a
merge
request
label.
And
then
we
go
to
the
issue
itself.
We
explain
them
what
the
interface
is.
So
I
was
trying
to
strike
a
balance
between
how
much
content
we
have
in
these
helpers
and
how
helpful
I
believe
it
is
because
I
didn't
want
these.
This
is,
for
example,
quite
long
already.
A
So
this
is
the
guided
tour.
Then
we
also
want
to
show
them
how
to
create
their
own
project,
but
they
can
also
drop
out
if
they,
if
they
feel
like
they've,
seen
enough
right
or
maybe
they're
not
ready
to
create
their
own
project.
Yet
they
can
drop
out
and
we
basically
tell
them
yeah.
This
is
it
you
can
this
will
disappear?
Basically,
so
we
introduce
them
to
this
quick
menu.
A
Take
create
a
project
and
again
here:
I
can
I
go
back
again,
so
they
created
a
project
and
we
all
want
to
now
show
them
how
they
can
invite
other
people
to
this
project,
which
should
be,
you
know,
helpful
towards
getting
more
users
in
the
future,
but
if
they
don't
feel
like
it
or
don't
feel
ready
to
invite
more
people
to
the
project
they
just
create
it.
They
can
say
no
thanks,
but
let's
say
that
they
want
to
do
that,
and
we
told
them
where
to
do
that
and
how
so
this
is
very
much
simplified.
A
They
would
need
to
enter
an
email
there
and
that
project
where
I
simplified
it
for
the
sake
of
the
prototype,
and
this
is
pretty
much
it
for
the
prototype.
Okay.
So
the
final
bit
was
the
free
trial,
signups
of
Trudy,
all
the
research
that
we
did.
We
saw
that
the
free
trial
signup
was
quite
broken
and
hard
to
get
true
for
the
users,
so
we
want
to
introduce
improvements
there
and
I
already
wrote
down
a
couple
of
things.
A
I
would,
as
I
was
doing
research
so
now
that
we
are
starting
to
implement
the
MVC
prototype
free
to
use.
Our
onboarding
I
will
now
focus
a
bit
more
on
the
improvements
for
the
free
trial
side,
which
will
be
the
rest
of
this
milestone.
For
me,
plus
a
couple
of
other
things
and
yeah,
that's
pretty
much.
What
I
wanted
to
show?
Does
anyone
have
any
feedback
of
on
the
latest
iteration
of
the
guided
onboarding
I.
C
A
The
little
helper
on
the
bottom
right
right,
so
this
is
something
that
came
out
from
this
call
initially
and
yeah.
I
thought
it
was
a
really
cool
idea
and
it
would
be
perfect,
for
you
know
people
when
they
lose
track
because
I
remember
myself
going
through
guided
on
boardings
and
then
you
click
on
something
that
you
weren't
supposed
to
click
on
and
you
lose
track
and
there's
no
way
to
get
back
into
it.
Right
and
I
said
this
with
you.
This
is
going
to
be
perfect
because
you
can
resume
from
where
you
left
off
and.
A
A
A
Actually
there
just
to
indicate
affordance
that
you
can
actually
click
on
it,
but
but
clicking
anywhere
on
this
would
open
the
whole
menu
yeah.
That's
just
there
to
make
it
look
more
clickable,
I
guess,
but
yeah
I'll
get
some
more
feedback
from
users
on
this.
The
initial
feedback
that
I
got
from
one
of
the
users
was
that
it
didn't
have
good
enough
contrast
with
all
the
user
interface
that
we
have
in
the
background.
So
maybe
we
can
explore
a
darker
version
of
it,
but
it
was
only
from
one
of
the
three
users
that
we
received.
A
That
feedback
and
the
other
thing
is
this
is
fixed.
So
as
you
scroll,
this
one
remains
fixed,
so
it
should
be,
quite
you
know,
visible
and
it
will
animate
in
once
the
page
loads.
So
these
things
combined
I
think
it
should
be
okay,
but
let's
wait
until
we
see
how
it
gets
properly
implemented,
and
then
we
can
get
our
feedback
on
a
much
better,
because
this
is
so
so
much
simplified
right.
This
prototype
done
in
sketch.
Basically
it's
a
bit
hard
to
imagine
how
it
will
actually
work.
Yes,.
C
Something
you
could
think
about
doing
is
if
our
standard
is
double-a
compliance,
if
I
remember
correctly,
that's
what
it
is.
You
could
also
just
play
with
what
a
double-a
contrast
in
a
gray
would
look
like
and
just
see
how
that
feels.
But
I
really
like
the
dock
and
your
your
icon
for
clicking
middle
I,
mean
I.
Think
that's
super
intuitive,
but
I
love
that
you
thought
through
also
making
the
entire
dock
clickable.
So
it's
just
an
affordance,
but
you
can
click
anywhere
any!
That's!
That's
great
yeah
I.
A
Thought
that
was
actually
important,
because
if
I
only
had
the
small
logo
there-
and
it
says
non-
Pete
slap
one
out
of
three
and
the
progress
bar,
it
doesn't
look
that
it
doesn't
really
look
clickable.
It
does
have
a
bit
of
shadow,
but
it
just
wasn't
enough.
So
I
felt
I
needed
something
more
and
then
you
also
need
something
to
close
it
once
you
open
it
right
and
it
just
turns
into
an
axe.
Once
it's
open,
yeah.
A
B
B
C
As
you
were,
clicking
through
I
was
quickly
reading
the
content
of
the
tutorials
and
I
really
really
liked.
It
I
think
that
the
voice
and
tone
that
you've
used
is
really
nice.
It's
friendly
and
it's
engaging.
So
that's
really
really
well
done.
I
would
like
to
have
us
run
this
by
a
technical
writer
just
to
catch
like
some
missing
commas,
and
things
like
that.
I
mean
it.
That's
that's
tiny
little
nuance
right.
B
A
I
did
ping
mic
comments
in
this
issue,
so
I
hope
I'll
get
some
feedback
from
him
as
well.
I
think
I'm.
Looking
at
the
wrong
issue
again,
mixing
them
up
yeah
this
one
I
did
ping
him
I,
hope
I'll
get
some
feedback
yeah.
It
would
be
nice
cuz
it.
Sometimes
you
just
notice
I
misspelled
minutes
wrong
in
in
the
first
iteration
that
I
did
and
I
just
didn't
see
it.
It's
good,
it's
nice
to
get
some
fresh
eyes
on
some
coffee,
always
every.
A
That's
actually
what
I
was
aiming
for,
because
we
want
to
sound
a
bit
friendlier
in
in
this
particular
case,
because
it's
it's
the
first
experience
for
most
of
the
people
that
will
go
through
this
right.
So
it
can't
be
just
something
really
bland
and
cold.
It
needs
to
be
a
bit
warmer
and
it's
it's
guiding
people
right
as
well,
so
it
needs
to
be
quite
yeah,
friendly,
I
would
say.
A
C
A
And
yeah
the
next
time
we'll
we'll
revisit
this
one
we'll
look
at
this
again.
I
hope
it
will
be
implemented
already
so
we'll
have
something
actually
live
and
built
to
go
to
go
through
and
see
how
it
actually
works
and
we'll
also
have
data
to
see.
Does
it
actually
work?
Do
people
go
through
this
too?
Do
they
find
it
helpful,
I
hope
we'll
get
that
little
survey
survey
implemented
as
well?
That's
where
people
will
be
able
to
rate
it
from
one
to
five?
Is
it
like
really
helpful?