►
From YouTube: UX Showcase Alternate Detail View Layout
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hi,
I'm
camilia,
I
am
senior
product
designer
from
securin
protect
and
today,
I'm
just
going
to
talk
about
a
design
where
updating
mainly
focus
on
like
how
to
help
user
to
consume
large
amounts
of
data,
and
also
like
very
easy
to
make
some
actions.
I'm
sorry
for
that.
No
presentation,
because
I'm
going
to
parent
to
live
like
very
soon
and
a
lot
of
work
held
up.
A
So
if
there
anything
unclear
like
what
I'm
talking
about
like
just
put
it
in
the
question,
I
will
answer
it
later
and
I
can
always
like
explain
you
offline
and
first.
I
just
want
to
explain
what's
the
current
problem,
so
this
is
example
of
alert
page,
and
this
is
the
dummy
data.
But
those
are
usually
kind
of
security.
Alert
came
into
the
system
that
the
user
us
receive
and
what
the
user's
general
behavior
will
know
from
research
is
that
they
need
to
make
some
quick
actions
like,
for
example,
from
this.
A
A
Data
and
real
data
can
be
even
more
and
what
we
actually
want
to
do
is
we
want
to
use
it
to
really
like
easy
to
consume
all
those
informations
and
make
quick
decisions,
but
we
don't
want
to
let
user
click
on
different
ones
and
go
to
next
page
and
come
back.
So
that's
a
lot
of
actually
clicks
for
them
to
see
what's
happening
and
prevent
them
from
doing
something
very
quick.
A
So
that's
the
challenge
to
do
something,
quick
with
like
quick
decision
but
with
large
amount
of
data,
and
we
have
like
actually
two
options
we
have
in
the
head,
so
the
first
one
is
happening
yeah,
so
the
first
one
we
want
to
use
a
split
view
is
more
like
an
email,
so
user
can
quickly
just
go
through
them
and
show
them
a
summary,
and
if
they
want
to
see
detail,
they
can
see
it
and
they
just
display
them.
A
Also
in
a
nicer
way
and
another
option
is
we
want
to
make
the
drawer
bigger
and
the
same
thing
display
them
in
a
nicer
way.
So
there
are
some
like
advantage
and
disadvantage.
We
start
off,
for
example,
for
the
expanded
drawer,
since
we
already
have.
The
component
of
the
small
door
is
very
easy
for
us
to
like
continue
the
work
comparably
and
we
can
like
both
on
the
design
side
on
the
development
side
is
easier,
but
then
we'll
have
a
problem
with
like
a
maybe
double
score
bar
or
something.
A
So
that's
something
we
really
don't
want
and
also
a
height
part
of
the
table.
If
you
can
see
that,
like
some
information
on
this
side,
might
be
useful
for
the
user,
they
don't
see
it
anymore
and
for
the
split
layout,
I
think
it's
like
the
is
like
it's
very
easy
to
scan
and
it
doesn't
need
user
to
go,
click
close
and
like
go
back
and
forth
and
stuff.
But
the
difficult
part
is
like
this
is
new
layout.
We
need
to
think
a
lot
and
maybe
create
new
component
and
also
for
development.
A
It's
more
effort
compared
to
the
previous
one.
So
it's
kind
of
like
we're
not
really
sure
which
one
is
the
best.
So
we
decided
to
do
the
research
first
and
to
see
how
user
prefers
and
we
just
like-
show
user
like
three
different
ones.
The
first
one
is
the
current
one
like
even
we
know
that
the
this
one
is
too
small.
We
still
want
to
confirm
with
the
user.
A
This
is
too
small
and
when
we
confirm
it,
it's
really
very
small
for
us
to
consume
a
lot
of
data
and
we
also
show
user
options
with
a
bigger
drawer
and
also
show
them
like
the
this
split
layout
and
let
them
play
around
with
make
this
a
little
bit
more
like
a
clickball
and
with
the
real
data,
and
they
can
just
in
the
research
they
can
really
dive
into
the
situation
and
to
try
to
decide
whether
this
is
like
real
for
them
to
deep,
like
to
make
it
a
more
real
scenario
to
let
them
imagine
that.
A
Do
they
want
to
solve
this
problem
or
not
not
let
them
just
like
see
the
differences
play
the
layout,
so
we
can
get
more
information,
and
actually,
I
think
I
have
like
when
I
build
the
layout
since
this
was
like
having
some
schooling
and
stuff
like
it
took
me
some
time,
but
I
think
I
have
some
small
tip.
A
There
might
be
useful
for
you,
so
what
I
realized
that
at
the
beginning,
the
schooling
doesn't
really
work
and
with
the
expand
and
the
collapse,
the
main
problem
is,
I
have
a
lot
of
groups
so,
on
the
left
hand
side
I
usually
like
use
a
lot
of
groups
and
when
that
copy
paste,
the
data
and
to
different
like
content,
is
just
duplicated
a
lot
and
it
creates
problems.
A
And
then
I
realize,
if
I
create
a
lot
of
local
components
and
just
change
the
data
but
lets
the
interaction
happen
outside
of
the
frame
it
actually
works
way
better
and
also
the
auto
layout
is
better
than
boot
game.
So
that's
some
video
tips.
I
see
from
the
internet.
The
people
says
like
yeah,
use
a
fewer
group,
but
try
auto
layout
and
reuse
like
local
components
like
even
with
a
small
thing.
I
put
the
interaction
outside
of
the
frame.
A
Actually
it
works
better
so
next
time,
if
you
have
similar
problem,
maybe
that's
something
good
to
do
and
go
back
to
the
research.
So
the
research
was
like
very
informatic,
and
I
think
we
did
six
users
and
we
got
a
lot
of
results,
and
this
is
how
I
label
it.
I
know
some
kind
of
effort,
I'm
putting
in
to
create
some
global
kind
of
tag.
I
also
want
to
share
this.
Maybe
this
can
help
us
like
to
have
some
global
tax,
which
is
useful.
So
for
me,
what
is
important
is
always
like.
A
Even
the
target
of
the
research
is
to
validate
the
design
we
still
get
to
the
general
flow
because
we
created
the
real
scenario,
so
the
general
flow
behaviors.
I
always
tag
them,
no
matter
what,
because
it's
informative
in
the
future
and
for
this
research,
because
we
have
a
lot
of
information,
we
want
to
know
which
are
the
important
one
for
them
to
finish
their
tasks.
A
So
I
highlighted
like
specifically
what
are
the
important
information
for
them,
and
there
are
a
lot
of
new
ideas
actually
came
from
the
user,
which
is
not
our
research
questions.
I
think
that's
also
something
like
could
be
valuable,
always
keep
in
mind
like
save
it
somewhere
and
the
others
are
like
for
even
what
others
are.
Some
small
things
that
I
think
need
to
be
improved
and
the
main
questions
like
for
this
research
which
design
you
they
prefer.
It
help
us
to
solve
the
language.
A
If
I
go
to
the
research
summary
so
from
the
research,
we
know
that,
like
basically
almost
all
users
think
the
small
drawer
is
too
small.
It's
one
user
says
it's
okayish,
but
the
other
ones
really
says
like
it's
too
small,
so
we
confirmed
our
assumption.
Even
we
have
like
quite
a
strong
feeling
that
this
is
a
problem
like
confirmed
with
user
is
always
good
and
for
the
two
layouts
like
this
one
and
the
bigger
drawer.
A
Actually
he
liked
the
table
more
because
he
used
excel
sheet
a
lot,
so
I
think,
compared
to
the
another
like
a
group
which
prefer
the
split
layout,
the
more
email-like
layout.
The
people
says
it's
easy
to
see
it's
very
easy
to
navigate
all
those
stuff,
so
those
reasons
could
change
a
lot.
If
user
don't
use
microsoft
anymore,
if
you
user,
don't
use
excel
sheet
anymore,
like
they
might
not
prefer
this
one.
A
So
this
seems
like
a
stronger
performance
from
the
user
and
another
big
question
we
have
from
the
research
we
want
to
answer
is
like
about
information.
What
are
the
important
informations
and
is
information
hierarchy?
There
is
good,
so
all
of
them
says
good,
so
they
literally
tell
me
that
it's
really
good
to
use,
but
I
still
observe
something
so
like,
for
example,
if
you
take
this,
you
can
still.
A
Yeah,
so
if
you
take
this
as
an
example,
so
we
didn't
like
for
the
all
details,
we
didn't
group
them,
but
I
see
a
lot
of
I'm
not
first
six
out
of
six
but
there's
quite
a
lot
of
amount
of
users
when
they
search
it.
It
says
you
have
like,
for
example,
destination
like
source
tcp
and
destination
tcp,
so
they
try
to
find
the
information
with
the
source
and
destination
ip
destination
ip
source.
They
always
like.
Try
to
fund
these
two
type
of
information,
so
these
two
grouping
might
help
users
to
consume
the
data.
A
A
Some
other
things
are
interesting,
but
also
confirm
that,
like
what
type
of
action
they
are
doing
and
at
the
beginning,
we're
not
sure,
like
those
are
very
useful
actions,
creating
incidents
download
and
stuff.
So
it's
all
confirmed,
and
also
I
feel,
like
one
user,
I
think,
missed
some
of
the
actions
because
they're
in
different
locations
and
stuff
and
in
the
later
updates,
I
put
all
those
actions
together.
So
it's
easier
for
users
to
find,
and
also
all
those
like
additional
information
like
what
I
labeled
in
dollar
tile.
A
I
think
in
the
future
to
inform
us
better,
no
matter
what
type
of
like
products
which
helps
user
record
always
refer
back.
So
our
research
is
not
a
one-time
thing,
so
it's
inform
our
future
like
a
related
design
and
also
there
are
a
lot
of
new
ideas
came
from
user,
which
is
not
related
with
like
what
we're
trying
to
find
out
here
like,
for
example,
a
lot
of
them
want
to
have
like
a
notification
system
like
they
want
to
be
integrated
like
a
better
weather
product.
A
A
So,
with
updates
like
after
the
research,
so
we
basically
update
the
ui
a
little
bit
like
I
said
all
the
actions
are
grouped
together
and
all
the
information
we
take
them
as
a
source
destination
and
general
network
to
help
user
to
consume
it
better.
We
clean
the
ui
so
before,
like
during
the
test.
We
still
have
like
the
boxing
style,
noise
and
less
boxing,
so
there's
still
kind
of
space
to
improve,
I
think
in
the
future.
A
So
this
is
the
current
status
for
now
and
what
we
are
going
to
do
and
we
are
waiting
for
the
prioritization
for
the
development
at
the
meantime
like
we
want
to
probably
create
new
either
as
a
component
or
layout,
but
haven't
decided
yet.
So
I
think
I
also
linked
the
future
pajama
issue
here,
so
I'm
going
on
the
leave
apparently
for
like
three
months
four
months,
something
like
that
longer
and
if
anyone
who
have
time
are
interested
into
this,
I
think
it's
something
very
nice
just
to
pick
it
up
and
that's
it.
C
I
had
a
couple
that
I
put
in
the
agenda
and
what
was
interesting
was
for
both
of
them.
You
ended
up
addressing
them
in
the
updates
that
you
made
so
I'm
going
to
leave
them
in
the
agenda
just
because
I
had
already
put
them
there,
but
I
also
updated
to
say
yay.
You
did
this
yeah.
The
first
thing
that
I
immediately
noticed
was
the
unboxing
issue.
Everything
was
so
bounded
and
it
was
causing
like
it
looked
like
it
was
going
to
cause
so
much
scrolling
and
then
plus
it
was
just
some
visual
clutter.
C
So
I'm
glad
that
you
caught
that
and
made
some
updates
and
then
the
other
thing
was
the
the
detail
view
needed
that
better
information
hierarchy
for
scan
ability.
So
I
was
very
pleased
to
see
that
by
the
time
you
got
to
the
end
you
had
found
both
of
those
things
already
and
you're
working
on
them.
So
thank
you.
B
I
had
a
quick
question.
I
know
that
during
your
explorations
there
was
some
discussion
around
allowing
users
to
toggle
between
the
two
different
views,
split
view
and
table
view,
and
I
was
just
wondering
where
that
conversation
ended
up.
A
We
created
a
new
issue
for
it
as
a
follow-up,
like
could
be
potential
like
the
next
actionable
insights,
but
since
we
have
other
priority,
we
didn't
really
like
talk
it
yet,
but
I
think
it's
also
good
good
to
bring
it
when
we
were
like
talking
about
the
pajama
related
like
splitting
structure
could
be
something
we
already
introduced
as
a
component
first
during
heaven,
development.
Yet.
B
There's
a
nice
read-only
tip
in
the
first
bullet
too.
That
I
think
is
worth
pointing
out
to
everyone.
Just
as
a
reminder.
We
don't
always
need
presentations.
A
C
D
I
have
a
quick
question:
are
there
any
plans
on
taking
these
learnings
and
trying
to
apply
it
to
a
an
abstracted
component
for
pajamas?
You
know
like?
Maybe
this
could
fall
more
under
region
or
something
like
that.
A
B
Okay,
thank
you.
Camilla
zoom
moves
all
the
buttons
around
when
there's
chat
opened,
where's,
topical.