►
Description
Weekly design review for 19 July, 2020.
A
B
B
A
Proposal
group
yep
yeah,
thank
you
so
when
you're
working
with
protected
branches,
they
are,
they
have
like
a
table
view.
I'm
gonna
pull
up
my
gdk
as
I'm
talking
through
it
and
we're
gonna
bring
some
of
that
functionality
into
the
group
level
because
it
doesn't
exist
today.
But
what
we're
starting
with
is
just
the
default
master
or
main
whatever
it's
called
the
default
branch
rule.
A
So
my
initial
proposal
is
to
design
it
as
such,
like
it's
going
to
literally
just
be
that
table,
but
I
wasn't
sure
if
I
should
make
it
more
of
a
form
or
just
use
the
table
design,
because
I
mean
my
aspiration:
is
that
we'll
be
able
to
do
more
protective
branch
rules
than
just
the
default,
so
I
thought
it'd
be
easier
to
start
with
the
table,
but
I
mean
in
terms
of
like
implementing
a
design.
It
might
actually
be
easier
to
do
a
form,
but
it
wouldn't
scale.
A
B
A
Well,
I'm
just
thinking
if
you're
trying
to
show
like,
for
example,
in
protective
branches
right
now
like
you
can
see
there
are
several
rules
specified
here
or
specific
branches
that
are
specified
in
here.
I
can't
imagine
having
a
form
for
all
of
these
necessarily,
but
I
I
do
agree.
I
think
it
would
be
better.
A
I
mean
this
this
table,
it
just
has
not
been
updated,
it's
still
in
hamel
and
it
has
not
had
a
lot
of
ui
components
updated,
so
it
doesn't
even
respond
like
the
way
that
it
would
break
down
each
record
into
an
individual
row.
Like
some
other
table
designs
do
so
yeah
I
mean
I
definitely
would
rather
design
or
I
would
rather
us
implement
a
component
that
we
can
scale
well
in
different
viewport
sizes.
A
B
A
A
Yeah
I
mean
I
can't
really
see
people
managing
their
settings
configuration
particularly
from
a
mobile
device,
be
really
weird,
like
I
guess.
You'd
have
to
just
have
to
have
like
your
group
owner
on
a
beach
vacation
and
needing
to
change
a
setting
while
they're
sitting
there
like.
Maybe
that
would
be
a
case
where
it
would
happen,
but
by
and
large
people
are
using
gitlab
at
their
desk
they're,
not
doing
it.
For
these
reasons,
on
mobile
as
much.
A
Well,
I
tell
you
what
I'll
come
up
with
a
version
this
week,
I'm
going
to
miss
next
week
because
I'll
be
on
vacation
but
I'll
circle
back
with
a
couple,
compare
and
contrasting
ideas
for
like
what
it
looks
like,
maybe
in
the
first
release,
and
maybe
a
bit
how
it
would
work
in
a
visionary
perspective
and
see
what
y'all's
thoughts
are
again.
Two
weeks.
C
A
I
just
I
threw
it
in
there
because
I
was
kind
of
messing
with
it
to
see
if
I
could
get
it
to
play
a
little
nicer,
so
I
mean
I,
oh
it
hides
the
play
button.
I
was
just
kind
of
hacking
at
it
just
to
make
it
look
like
things
were
lining
up
nicely.
I
assumed
you
wanted
to
be
able
to
click
here.
Have
them
click
on
the
calendar
sets
the
date
and
then
clicking
it
resets
it
yeah.
I
assume
that
was
what
you're
trying
to
do.
A
Okay,
thanks
sigma,
I'm
working,
let's
see,
where's
the
interaction
on
this
one.
There
we
go
so
this
one
is
using
a
click,
it's
using
the
open
overlay
and
then
I
think,
I'm
doing
a
custom
spot,
which
is
where
you
laid
it
and
then
on
this
one
it
connects
to
this
guy
again.
I
think
it's
doing
like
it's
swapping
it
out
and
it's
putting
it
in
a
specific
location.
B
A
B
C
A
A
C
D
D
B
D
D
B
B
B
D
B
D
B
B
I
did
a
presentation
on
it
in
the
showcase
it
eventually
evolved
to
planning
objects,
now
they're
called
work
items
and
basically
to
try
to
summarize,
we
discovered
that
we
needed
to
refactor
issues,
and
so
since
we
were
going
to
be
redoing
it
anyway,
kristin
and
gabe
said
well,
now's
a
good
time
to
make
it
better
and
to
prep
for
kind
of
what
we
have
in
terms
of
a
long-term
vision
for
issuables
in
the
future.
So
our
thought
is,
we
create
a
base
thing.
B
B
I
don't
know
how
familiar
you
are
with
notion,
but
kind
of
along
the
lines
of
notion
where
you
can
have
a
custom
kind
of
template
thing
like
an
issue
and
then
you
can
build
the
widgets
in
that
you
want.
You
can
say
I
want
to
have
breadcrumbs.
I
don't
want
to
have
health
status
things
like
that,
so
this
is
just
the
very,
very,
very
basic
mvc
of
that
thing,
and
we
decided,
after
a
lot
of
conversations
that
we
wanted
to
make
it
mobile
first,
because
the
mobile
experience
isn't
great
for
issues.
B
So
we
want
to
go
ahead
and
be
thinking
about
that
now
for
mbc,
which
will
only
be
put
behind
a
feature
flag
to
a
small
subset
of
people
at
the
company.
We
are
going
to
have
title
assignees
description
and
status
and
that's
it
and
then
before
it
gets
into
the
hands
of
customers,
we'll
have
more
built-in.
B
B
So
hopefully
it's
set
to
the
right
screen
is
the
start
screen
yeah,
so
here's
an
example
of
focusing
on
it
from
mobile.
I
did
a
competitor
analysis
looked
at
four
different
competitors
and
there
were
some
similarities
in
all
of
them.
One
was
having
inline
editing
for
titles
and
descriptions,
and
so
I
did
a
lot
of
discovery
surrounding
that.
So
the
thought
here
is
that
you
can
click
and
type
in
we're
just
going
to
assume
that
we've
entered
a
title
typed
in
a
title.
We
would
have
no
additional
functionality
in
the
title
edit.
B
We
wouldn't
have
bolding,
or
you
know,
italicizing
or
anything
like
that,
which
we
don't
have
currently
anyway,
but
you
can
add
a
title
and
just
with
a
title,
create
your
work
item.
So
we're
still
I'm
still
a
little
concerned
about
that.
I
think
that
we
will
still
probably
need
to
be
able
to
assign
a
type,
but
we'll
add
that
in
I
assume
in
the
next
phase.
So
let's
say
that
I've
added
in
this
title-
maybe
I
do
want
to
go
ahead
and
add
a
description.
B
So
in
that
case,
maybe
you
would
click
and
I
just
realized.
I
need
to
include
this
editor
on
the
previous
screen,
but
let's
say
that
you
have
entered
in
your
description.
You've
got
your
buttons
down
here.
Your
controls
for
managing
the
edit
editor
functionality,
I'm
still
working
through
these
buttons
and
trying
to
kind
of
figure
out
how
I
want
to
lay
them
out.
So
that's
still
work
in
progress
and
gabe
wanted
to
see
some
alternatives
to
having
the
write
and
preview
tabs.
B
I've
got
those
on
the
desktop,
but
I
need
to
think
through
how
that's
going
to
work
on
the
mobile
settings
as
well.
I
also
don't
like
having
kind
of
competing
buttons
here,
so
obviously
with
a
mobile
device.
You
have
your
own
keyboard,
which
has
its
own
button.
I
think
we
can
customize
that,
but
I
don't
necessarily
want
to
remove
native
functionality.
So
that's
something
else
that
is
still
kind
of
being
considered,
but
let's
say
that
I've
entered
this
information
in.
B
Obviously
the
editor
controls
are
now
down
at
the
bottom
of
the
view,
which
also
is
going
to
be
the
case
on
desktop.
So
I
hit
save,
and
now
I've
got
a
title.
I've
got
a
description,
I'm
proposing
that
we
truncate
the
description
so
that
when
we
eventually
add
in
comments,
comments
aren't
just
pushed
way
down
below
and
some
of
that
comes
from
feedback
from
users
and
that
we
found
title
and
comments
were
much
more
important
than
description.
B
Description
is
important,
but
most
people
had
a
tendency
to
want
to
read
the
title
and
the
comments
and
then
come
back
to
the
description
if
they
had
to,
but
they
didn't
really
want
to
spend
a
lot
of
time
in
it,
which
I
thought
was
interesting,
so
we
would
truncate
it
and
give
them
the
ability
to
scroll
and
see
more
managing
assignees
would
happen
in
a
panel
potentially
like
this,
so
you
would
have
the
ability
to
assign
yourself
or
you
could
search
this,
of
course,
would
bring
up
the
keyboard.
So
it
would
be
a
little
jump.
B
Something
gabe
wants
me
to
explore
is
bringing
this
all
the
way
up
to
the
top
anyway,
so
that
you
don't
necessarily
have
it
kind
of
down
at
the
bottom,
but
I
kind
of
like
the
thought
of
being
able
to
see
a
little
bit
of
the
information
in
the
background,
while
you're
adding
your
assignees
just
because
I
know
so
many
of
us
work
on
so
many
different
issues
per
day.
It
could
potentially
be
easy
to
lose
a
little
bit
of
that
context.
B
B
B
So
I
don't
anticipate
that
being
a
big
concern
and
then
status
would
also
be
something
you
could
potentially
just
click
and
change
here
on
the
spot,
partly
because
we
had
so
many
users
looking
at
our
status
badge
and
thinking
that
it
was
a
button
and
after
talking
with
gabe,
it's
like
well,
why
not
make
it
a
button?
Actually,
why
not
make
it
something?
B
Instead
of
just
hiding
this
in
quick
actions
and
hiding
it
behind
a
menu,
we
can
still
put
it
in
those
places,
but
also
allow
it
to
be
something
where
users
can
choose
to
just
change
the
status
by
selecting
that
item.
If
they
want
to
any
questions
about
the
mobile
view.
Any
thoughts
there's
also
a
desktop
view,
but
I
know
that's
probably
a
lot
of
stuff
to
take
in
in
itself.
C
B
C
B
I
did
actually
explore
a
few
variations
of
this,
so
I
originally
explored
having
them
side
by
side
to
make
the
kind
of
most
of
that
space
and
that's
how
most
of
our
competitors
do
it,
and
I
presented
these
three
options.
This
is
more
so
showing
how
labels
could
potentially
display,
but
I
presented
these
three
options
internally
and
overwhelmingly,
the
feedback
was
to
go
actually.
B
This
is
recently
changed,
but
the
feedback
was
to
go
with
the
layout
that
I
had
presented
a
moment
ago
with
everything,
stacked
and
then
christy
came
back
and
said
how
about
we
try
putting
them
side
by
side
like
this,
or
maybe
even
you
know,
set
it
kind
of
like
this,
and
I
that
still
feels
a
little
odd
to
me.
It
feels
a
little
like
one,
we're
going
to
eventually
add
in
more
things,
so
how
do
those
things
fit
in
in
this
context,
as
opposed
to
something
more
vertical?
B
Personally,
I
liked
this
flow
better,
just
because
I
thought
that
it
well.
I
guess
more.
This
flow
because
I
kind
of
like
the
labels
left
aligned,
but
I
thought
that
it
made
better
use
of
the
horizontal
space
which
is
already
limited
and
and
felt
a
little
more
well
organized,
but
definitely
appreciate
the
feedback
and
would
love
any
thoughts
you
have
on
on
these
examples
versus
the
other
as
well.
C
No
just
to
kind
of
expand
on
that.
I
think
again,
these
look
better
like
the
first
one
on
the
left
feels
more
logical,
like
I
think
you
have
to
come
at
this
from
perspective
of
a
mobile
app
and
not.
How
do
you
convert
this
to
a
responsive
view
and
if
you
rethink
from
a
mobile
app
perspective,
a
lot
of
the
architecture
changes.
D
B
I
couldn't
agree
more,
and
this
is
also
something
that
I've
been
pushing
back
on
when
it
came
to
the
research
I
did
with
the
competitor
analysis,
all
of
our
competitors
either.
So
three
out
of
the
four
that
I
looked
at
three
immediately
redirected
you
to
use
their
mobile
app
when
you
tried
to
access
the
product
on
a
mobile
device,
specifically
on
like
a
phone.
The
fourth
I
thought
had
a
true
responsive
experience,
but
the
more
I
looked
into
it.
B
It
actually
has
a
separate
mobile
site,
so
it
is
still
responsive
web,
but
it's
not
the
same
code
exactly
at
least
just
based
on
the
structure.
I
looked
at
in
dovetail
or
devtools
dev
tools.
Sorry,
I
got
no
sleep
last
night,
but
dub
dub
tools
is
what
I'm
trying
to
say.
So
it
was
apparently
different
code
bases
to
me
which
made
me
think
they
have
a
separate
mobile
site
altogether.
B
So
I
think
that
in
the
long
run
we
need
to
consider
having
a
separate
mobile
experience.
That's
just
focused
on
issue
tracking
and
management,
primarily
because,
as
we
talked
about
with
austin,
there
aren't
a
lot
of
products
that
seem
seemingly
are
offering
anything
deeper
than
that,
but
that's
not
in
the
cards
for
now,
and
so
I'm
being
told
to
just
focus
on
mvc
for
this
and
make
it
mobile,
friendly
and
part
of
the
challenge
I
went
into
was
how
does
a
layout
like
this
translate
to
desktop
and
to
just
kind
of
show?
B
B
D
Yeah,
I
think
daniel
brought
up
a
good
point
about.
You
know
whether
it's
like
a
mobile,
just
a
responsive
experience
versus
like
a
more
native
kind
of
experience.
I
think
that's
yeah,
that's
a
really
important
thing
to
consider.
One
thing
I
was
just
going
to
mention:
holly
was,
I
was
wondering
if
you,
when
you're
doing
the
mobile
layouts,
whether
you
were
trying
to
use
the
or
whether
you
use
like
the
figma
app
on
your
iphone
to
actually
test
how
it
kind
of
feels.
B
I
did
I
did,
and
that
was
so
helpful
the
figma
mirror.
That
was
really
helpful,
because
I
found
that
even
even
just
looking
at
it
and
even
prototyping
it
on
my
laptop
was
not
the
same
as
having
it
in
my
hand
and
knowing
like
where
the
thumb
was
going
to
be
and
kind
of
getting
the
feel
for
it.
So,
yes,
that
was
a
huge
huge
benefit
to
have
that.
D
B
I
actually
encourage
the
pm's
to
get
it
as
well
and
to
try
to
test
it
themselves
using
that,
because
I
do
think
that
it
changes
the
experience.
I
mean.
I
really
think
that
it
helps
us
to
to
get
more
of
an
accurate
feel
for
what
that
is
going
to
be
like
when
it's
on
a
mobile
device
versus
just
viewing
it
on
a
large
wide
desktop
and
having.
A
C
That's
something
I
would
definitely
agree
about
is
that
in
pushback
to
say:
oh,
we
want
to
just
do
mvc.
It's
like
well
switch
this
and
view
it
in
your
hand,
and
tell
me:
does
this
mvc
make
sense,
I
think
a
lot
of
the
pushback
would
be
like
well
you're
right,
it's
not
really
a
good
experience
and
I
don't.
I
would
not
want
to
push
out
a
you
know,
meh
experience
just
because
it's
nbc
right.
B
I
don't
either,
but
I'm
I'm
curious
if
y'all
have
thoughts
on
whether
or
not
you've
had
to
do
that
and
and
how
you
address
that
experience
like
have
you
felt
you
had
to
push
something
out
that
was
not
complete
or
as
as
polished
as
you'd.
Like
I
mean,
I
think
we
all
have,
but
even
to
the
point
where
you
feel
like
a
good
experience,
is
being
sacrificed
to
a
degree.
D
Yeah,
that's
a
good
question,
I
mean
for
me.
I
mean
I
feel
like
sometimes
you
know
it's
not
doesn't
come
out
as
polished
as
I'd
want
it
to
be,
or
I
know
there's
going
to
be.
I
already
know
that
there's
we
already
have
follow-up
issues
for
something
when
we
release
it,
but
it's
never
to
the
point
where
the
user
can't
complete
the
task.
I
feel
like.
I
always
feel
like
it's.
It's
gonna
be
functional.
It's
gonna!
It's
gonna!
You
know
it's
gonna
work,
it's
not
gonna
be
yeah.
D
C
Yeah,
I
think
one
something
to
expand
on
that
is
to
make
sure
that
if
it's,
you
know
they
can
complete
the
task.
But
how
would
they
do
that
by
making
sure
the
foundational
aspect
of
the
mvc?
Is
there
so
focusing
on
the
foundational
aspects
of
what's
the
most
interactive
or
interacted
with
pieces
and
focus
on
that?
As
the
you
know,
the
mvc
and
try
and
get
that,
as
you
know,
usable
as
possible,
so
that
the
user
doesn't
have
the
problem
completing
the
task?
C
And
then
you
iterate
from
that
like,
for
example,
I
don't
know
how
often
somebody
creates
a
new
issue
versus
goes
and
looks
at
the
issue,
so
perhaps
less
focus
on
the
creating
of
the
process
and
more
so
about
the
reading
of
the
issues
and
then
responding.
Perhaps
that
could
be
the
first
thing
and
or
then
something
more.
C
You
know
under
the
hood,
redesigning
the
layout
or
the
architecture
of
the
page,
to
be
more
compartmentalized
so
that
when
it
does
collapse
on
the
mobile,
it
does
automatically
fit
that
interface,
that
you
experience
with
a
mobile
experience
and
that's
something
that
we
really
haven't
done
much
from
the
pajamas
aspect.
Is
that
what
are
these
components?
Look
like
architecturally,
you
know
as
organisms,
you
know
nick
is
pushing
this
and
it's
not
really
going
further
anywhere.
B
B
B
For
the
feedback
so
far,
this
is
a
big
project
and
there
are
a
lot
of
new
pieces
to
it,
and
that
makes
me
a
little
on
edge
because
I
know
that
we've
taken
the
time
to
kind
of
vet
and
get
feedback
on
and
evaluate
the
progress
of
and
the
the
functionality
and
user
experience
of
the
existing
patterns
that
we
have,
and
so
introducing
a
lot
of
new
patterns
makes
me
nervous.
But
I've
expressed
those
concerns
several
times
and
I'm
told
even
by
engineers
we're
moving
forward
with
making
new
things.
B
D
B
I
did
create
so
this
is
about.
I
have
the
prototype
for
the
desktop
and
for
the
mobile,
and
I
did
do
a
little
bit
of
just
quick
internal
stuff,
but
it
wasn't
really
formal
and
polished.
This
was
actually
just
last
week,
so
I
do
want
to
get
it
on
usertesting.com
and
just
get
some
quick
feedback
on
that,
but
yeah.
I
think
I
think
today
actually
I'll
be
wrapping
up
annotations
for
the
engineers
they've
asked
me
to
go
through
and
identify
everything.
That's
currently
in
get
lab
ui
and
make
a
note
of
that.