►
From YouTube: Magento PWA Backlog Grooming, 7 September 2018
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
A
I
should
would
choose
to
accept
that
we're
be
talking
about
the
search
experience
and
we
really
talked
a
little
bit
about
the
completion
of
that
checkout
experience,
which
is
or
confirmation,
as
well
as
implementation
of
some
of
the
great
work
that
Sammi
has
done
on
the
UX
I,
which
is
editable
part
and
so
you'll
see
you
know
with
that
recession.
We're
continue
to
make
really
good
progress,
not
only
on
what
we've
designed,
but
also
you
know
the
dependencies
there
within
right,
and
so
you
know
perfect
example.
A
You
know
barbering
folks
are
taking
on
the
beginnings
of
authentication.
Well,
you
know
one
of
the
first
things
you
want
to
do
with
authentication
is
order,
confirmation
right
being
able
to
go
into
that
and
and
and
and
see
from
there
and
be
a
begin
to
see
what,
in
order
to
look
like
and
so
next
week.
A
Looking
at
things
like
order,
details
and
other
experiences
that
we've
got
the
beginnings
out,
certainly
using
the
Illuma
reference
team
as
a
starting
point,
but
with
all
the
great
work
again
in
research
that
Tommy
and
team
are
doing
really
pushing
the
needle
as
much
as
you
can
for
a
reference
team
that
is,
that
is
progressive.
So
so
that's
all
we've
got
in
store
for
our
this
morning
this
afternoon,
depending
on
where
you're
calling
from
any
any
questions
or
comments
before
we
I
before
we
get
going.
B
A
Excellent
yeah
for
this
one,
we're
gonna
get
into
the
details
of
what's
coming
next
and
then
so.
We've
got
some
some
great
great
partners
here
on
the
on
the
call
really
been
helping
us,
you
know,
carry
things
especially
around
the
venue,
a
theme
starting
off
with
some
of
the
check-out
experiences
onwards
to
some
of
the
backend
experiences,
so
you've
got
a
good,
good
cross-section
and
really
a
good
good
set
of
eyes
on
what
we're
doing
this
moment,
as
we
kind
of
run
things
openly
through
these
grooming,
so
just
little
bit
of
context
there
but
yeah.
A
So
look
I'm
starting
off
with
something
easy,
I
think
the
search
piece
will
cover
a
good
portion
of
what
we
want
to
cover
for
our
for
today.
A
search
is
always
a
big
one,
but
I
do
think,
there's
something
we
can
start
with
on
that
one.
So,
let's,
let's
start
off
with
something
that
I
think
does
have
some
recency
here
again,
just
for
our
housekeeping
purposes.
You'll
see
for
the
items
are
recovering
on
Friday.
They
will
be
marked
forth.
A
So
we'll
start
off
with
with
where
we
left
off
again
at
the
at
the
last
demo,
which
of
course
is
advancement
of
that
many
part,
and
so
just
for
you
know
just
for
reference
for
those
who
those
who
have
seen
the
the
current
mini,
cart,
Jimmy
and
team
did
a
great
job
of
kind
of
starting
to
that,
and
we've
got
some
some
examples
from
the
Bergeron
folks
building
into
what
that
experience
looks
like,
and
so,
as
we
add
to
carts,
we've
got
the
basics
of
that,
but
you'll
see
pretty
quickly.
We
need
you
know.
A
Any
details
were
received
fit
so
I
set
these
up
earlier
this
week
for
us
to
kind
of
take
a
look
at
and
consider
I
took,
god.
I
took
the
little
screenshots
from
from
Zambia.
This
is
part
of
the
larger
prototype
that
we're
sharing
with
community,
but
just
as
a
reference
and
and
from
there,
we
want
to
advance
essentially
where
we've
got
today.
A
Zegna
in
this
case
is
just
a
summit
watch
but
then
adds
a
little
bit
more
details
from
the
project.
Details
in
this
case
sizing
colouring
quantity
we
certainly
have
heard,
but
then
the
ability,
of
course
to
edit
and
or
remove-
and
so
so
this
was
going
to
be
interesting,
but
I
think
carry
with
what
we've
created
so
far,
but
from
a
you
know
from
a
total
you
know
you
know
totally
user
story
standpoint
as
a
shopper.
A
We
want
to
edit
remove
and
then
again
out
of
any
items
of
favorites
from
the
checkout,
so
they
can
make
an
accurate
purchase
online.
Let's
say:
you've
bought
too
many
shoulder
dresses
here.
You
need
to
adjust
that.
Maybe
you
don't
want
it
at
all.
We
want
to
accomplish
that
and
make
it
accurate
purchase
I'm.
So
so
what
is
it
intelligent?
This
shouldn't
surprise.
You
too
much
updates
to
them
to
the
mini
cart
itself
and,
of
course,
the
abilities
to
do,
because
you
know
the
ad
the
favorites
at
and
remove
we're
making
some
assumptions.
A
You
know
some
of
those
larger
pieces
where,
let's
say
four
items
turns
into
four
hundred
and
forty
four
forty
things
like
that
that
we
have
to
think
about
when,
when
we
start
to
implement
this,
but
we'll
make
some
assumptions
with
this
being
a
very
base
case,
but
in
identify
future
story
afterwards,
in
terms
of
the
tasks
themselves,
you'll
start
to
see
a
pattern
here,
first
step,
especially
with
the
community.
Taking
a
look
at
us,
we
want
the
to
allow
for
some
time
of
discovery,
I'd
understand
how
it's
currently
implemented.
A
We
also
allow
the
the
ability
to
begin
implementing,
edits,
remove
and
add
the
favorites.
We
can
certainly
break
this
out,
maybe
thumbnails
already
there,
but
there
are
some
basic
product
items
in
their
title
and
details
for
the
UX
and
last
but
not
least,
looking
out
for
for
James
here
in
Austin
testing
and
documentation.
What
we
have
here
needs
to
add
needs
to
fast,
followed
with
some
documentation
so
that
so
that
people
can
set
this
up,
though.
So
that's
what
we've
got
again
we're
just
this
should
be
pretty
familiar
for
those
who
were
at
the
demo.
A
A
D
A
B
F
A
Yeah,
this
would
just
been
noting
it
and
we
would
cover
you
know
the
ability
to
view
those
at
a
later
later
time.
But
yes,
this
would
be.
She
could
be
here
verified
by
you
know,
you
know,
checking
some
things
behind
the
scenes
wherever
that
might
be.
But
yes
is
that
this
is
just
the
the
facing
version
of
that.
E
A
And
I
think
if
we
want
to
break
this
down
a
little
bit,
maybe
we
you
know,
maybe
we
can
edit
this
a
little
bit
and
kind
of
separate
favorites
from
the
other
two
I
like
the
idea
of
keeping
it
there
and
which
allows
us
some
discovery.
But
but
if
you
know,
if
favorites
kind
of
takes
us
down
a
a
you
know,
it
takes
us
into
it
kind
of
its
own
body
of
work.
A
D
F
Yep,
so
what
happens
to
those
line
items
if
I
have
more
than
one
thing
in
the
car,
because
it
looks
like
it's
showing
like
just
the
price
for
one
unit
and
the
total
at
the
bottom.
If
I
have
like
four
dresses,
will
it
show
me
the
the
total
for
four
dresses,
or
is
it
just
going
to
show
me
the
unit
price.
E
F
E
F
I
was
I
was
just
kind
of
thinking.
I
didn't
know
how
common
that
might
be
I
mean
certainly
on
a
fashion
site.
I
can
imagine
you're
more
likely
to
just
be
buying
one
of
each
item
but
I'm
guessing
if
you're
buying
like
I,
don't
know
if
it's
socks
or
something
then
maybe
I
am
buying
ten
at
the
time
and
I
kind
of
want
a
view
on
how
much
I'm
spending
on
each
type
of
item
rather
than
just
the
individuals
but
has.
G
Always
puzzled
me
about
Magento
specifically,
and
it's
sort
of
inline
editing
of
the
of
the
card
item.
I
have
exactly
the
same
questions
as
you
and
I.
Don't
actually
know
I've,
never
seen
in
the
fashion
vertical
that
UI
implemented,
as
well
as
I
want
with
that
expansion
and
contraction.
But
that's
really
it's
more
of
a
UX
question.
I
just
want
to
register
that
I
also
am
puzzled
by
this
and
I.
Think
so
me
I've
asked
you
better
before.
E
Yeah
we've
talked
about
this.
The
thing
is,
venya
is
a
very
specific
vertical
and
a
very
specific,
so
I
would
say
that
the
larger
decision
we
probably
have
to
discuss
is
do
we
want
to
provide
an
example
for
the
use
case
of
when
you
want
to
show
updated
to
updated
amounts
for
each
line
item
for
those
use
cases.
E
There
are
other
specific
things
like
this
I
mean
even
with
navigation
rights.
Good
practice
is
to
probably
not
have
more
than
three
or
four
levels,
but
there
are
many
much
as
I
bypassed.
For
instance,
they
have
frequently
seven
to
eight
levels
and
the
way
that
our
navigation
is
designed
right
now,
I
mean
I've,
been
discussing
this
with
Jimmy
there's
no
way
to
easily
switch
from
11
7
to
11,
then
that
goes
back
to
the
top.
E
Every
time
to
close
it,
and
so
red
comes
inside
the
now
breadcrumbs
on
the
page
like
how
we
can
allow
them
to
do
that
is.
Do
we
want
to
provide
an
example
for
that,
because
in
venÃa
we
only
have
three
levels
right
now,
so
that
it's
a
similar
question
for
the
card
I'm
happy
to
discuss
the
the
experience
around
providing
accurate
prices
for
each
line
item
in
the
car,
but
it
would
have
to
be
like.
Are
we
doing
that
millennia
or
are
we
saying
if
you
have
that
use
case?
F
A
F
E
Okay,
yeah
I
mean
that's
kind
of
the
reason
why
I
left
it
the
way
it
is,
though,
I've
had
discussions
around
this
with
seven
and
others
before.
If
I
don't
know
how
much
extensibility
of
experience
we
want
to
demonstrate
with
venya,
but
it's
definitely
something
we
can
consider
for
the
component,
the
pentagram,
the
library
we
have
to
say,
yeah.
E
G
G
Of
these
types
of
components,
just
in
the
persona
of
Freddy,
the
developer,
who
wants
tools
I,
would
urge
that
this
not
become
one
of
those
components
that
has
two
pages
of
configuration
options.
I
would
much
rather
that
the
line-item
concept,
which
Jimmy
has
implemented
in
a
very
generic
way,
be
something
that
you
you
you
plug
things
like
this
into,
so
the
line-item
display
itself
would
have
extension
points
for
adding
interactive
functionality
in
line
and
for
modifying
it's.
You
know
size
or
its
its
connections
to
data
rather
than
having
Peregrine's
component.
E
E
But
if
you
wanted
to
do
this
other
one,
yes,
how
you
could
do
it,
but
yeah
I,
don't
think
that
we
can
cover
every
it's
not
possible
to
anticipate
you
know
and
what
percentage
you
know
that
it
really
was
that
effort
of
you
know
documenting
and
trying
to
extend
for
all
of
that
right.
That's
the
question!
Well,.
G
Fortunately,
in
what
my
opinion
of
the
best
practice
is
the
documentation
burden
is
the
smallest,
because
you
don't
have
to
document
a
whole
bunch
of
alternative
and
variant
behaviors
in
the
first
iteration
of
the
thing
you
can
just
say:
here's
where
you
drop
in
X
and
then
you
can
implement
X.
If
you
want
to
to
satisfy
the
story
and
in
the
case
of
this
implementation,
as
opposed
to
others,
what
I've
said
just
do
it?
G
A
H
A
Think
there's
a
lot
to
be
said
about
keeping
this
simple
I
do
like
the
fact
that
this
simple
case
actually
embodies
what
a
high-end
fashion
retailer
might
be,
in
fact,
you're
not
going
to
be
ordering
four
of
these
tailored
trousers
in
that
size,
small
and
so
I
think
that
I
think
that's
okay,
I
think
we
have
to
allow
for
some
breathing
room
for
some
of
those
extensions.
Any.
E
A
I
think
I
think
four
down
I.
Think
if
you
guys,
if
you
guys
are
okay
with
this
I,
put
a
couple
notes
for
us
to
to
assign
some
research,
maybe
in
the
in
the
future,
once
this
is
hardened
a
bit
and
then
but
then
look
out
you
know
for
presenting
ever
for
extensibility
points
in
the
future,
making
sure
that,
with
what
we
do,
those
cases
you
know
could
be
achieved
for
the
right
situation.
But
it's
I
think
it's
a
good
conversation
to
have
and
good
questions
to
have
as
part
of
itself
mm-hmm.
A
E
We
hit
edit
items
so
that
there
are
two
use
cases
I'd
like
to
kind
of
make
transparent
here.
One
is
that
you
want
to
add
the
same
item
in
a
different
configuration
like
you
really
like
those
pants.
You
say
you
want
them
in
Navy,
but
you
also
want
them
in
in
maroon
or
whatever
other
color.
So
that's
an
intentional,
like
I
want
to
lose
this
product
in
two
different
configurations
which
would
be
dealt
with
by
either
clicking
on
the
thumbnails
or
the
title
of
the
product.
E
That
takes
you
to
a
PD
page,
and
the
flow
is
exactly
like
if
you
were
to
just
go
to
the
PD
page
and
add
that
as
a
product,
the
only
difference
is
that
it's
a
repeat
visit
for
edit
card.
What
we
discussed
was
that
the
configuration
of
the
product
would
be
abstracted
and
would
stay
within
sort
of
the
car
space.
E
Do
you
click
it?
It
shows
you
the
configuration
parameters
for
that
item,
with
the
call
to
action
to
save
changes
and
occult
and
the
header
that
says,
you're
editing
the
car
items,
so
you
make
your
changes,
you
save
them.
It
kind
of
updates
in
in
the
button
just
like
we
have
on
the
Add
to
Cart
button,
and
then
it
pops
you
back
into
your
mini
cart
and
tells
you.
Your
cart
item
has
been
updated.
E
Did
I
did
because
it's
challenging
on
iOS
and
it's
we're
kind
of
more
in
an
android
facing
pattern,
and
so
after
many
discussions
with
Jimmy,
we
decided
to
go
with
the
dot
pattern
for
technical
reasons
and
also
for
extensibility
reasons
why
we
would
have
to
consider
doing
like
a
drop-down
of
actions
within
a
couple
of
areas
like
if
you've
seen
on
whatsapp.
If
you've
ever
you
said,
which
is
a
bit
Messier
and
everything
would
be
a
with
this,
it's
kind
of
a
it's
its
own
menu,
so
we
could
add
more
items
to
it.
E
G
E
Mean
it
can
be
more
than
one
layer
deep,
but
I
feel
like
it's
slightly
less
elegant.
In
this
context,
I
mean
for
things
like
a
messaging
app.
You
do
have
need
to
sort
of
nest
a
lot
of
functionality
within
a
single
tile
based
on
if
you're
in
a
group,
conversation
or
a
one-to-one,
and
so
on.
This
case
is
a
little
bit
more
simple,
especially
with
zhenya
and
I.
Just
feel.
All
things
considered
this.
This
type
of
solution
is
definitely
more
simply
extensible
than
it's
unknown.
G
Okay,
yeah
I,
see
it
I,
see
it
I
think
I
think
I'd
have
to
use
it
at
an
implementation,
but
I'm
young
convinced
provisionally
that
it's
not
like
a
huge
missed
opportunity
for
swipe
I,
just
kind
of
wanted
some
context.
No.
A
I
had
the
same
feeling
as
well
I.
Think
four
I
think
we
really
have
to
keep
a
close
eye
on
some
of
these
interactions,
as
they
span
across
iOS
and
Android,
to
make
sure
that
you
know
that
it
is
because
we
were
essentially
creating
a
reference
team
that
needs
to
needs
to
serve
both
right,
and
so,
if
we
have
to
make
some
concessions
like
this
to
serve
both
I
think
you
know.
If
you
were
to
look
at
a
list
of
principles,
I
think
that's
something
we
should
consider
so
I
think
was
the
right
thing.
A
E
I
think
all
things
considered,
we
are
really
not
stuck
with
sacrificing
some
desires.
I
suppose
is
that's
kind
of
a
cool
thing
that
you
can
do
that
maybe
you're
but
I
think
from
a
practicality
and
just
usability
standpoint
I
prefer
the
solution
that
we
changed
to
with
the
three
jobs,
because
that's
also
understood
if
the
Alice,
these
of
the
three
jobs
immediately
indicates.
F
E
E
The
slot
machine
kind
of
thing
at
the
bottom
of
our
us-
or
it
could
be
just
your
keypad
that
comes
up
and
you
enter
a
number
and
it
updates
it
could
go
up
different
ways:
I
hadn't
discussed
with
Jimmy
or
anyone
else
sort
of
where
we
were
landing
and
it's
open
to
discussion.
We
can
go
with
it's
sort
of
a
utilitarian
function,
and
you
know
whatever
is
easiest,
for
people
is
what
I
would
probably
lean
on.
E
F
Know
that
that
makes
sense
to
me
I
think
it
was
just
that,
because
there
was
an
indication
on
there
of
the
arrows
being
either
like
gray
or
black,
depending
on
whether
you
could
go
up
or
down,
though
I
just
wanted
to
make
sure
that
it
those
it
wasn't
intended
that
those
were
actual
touch
targets
up
and
down
from
there.
Yeah.
E
I
think
not
allowing
them
to
already
the
last
discussion
on
that
was.
They
cannot
delete
the
item
by
making
the
quantity
zero.
They
would
have
to
go
to
the
Dobson
say,
remove
item
so
that
that
arrow
would
always
have
to
be
gray
anything
beyond
one,
because
it
was
a
visual
indicator
that
you
can't
go
to
zero,
but
I
haven't
that
that
was
the
result
of
the
previous
cycle
of
testing
and
I
have
not
tested
this
after
that.
To
make
sure
that
that
communication
is
actually
going
through.
F
Then
the
other
one
was
probably
just
a
consideration
for
estimation
there
on
the
edit
screen
it
looked
like
like
in
the
particular
example,
one
of
the
colors
was
disabled
for,
like
presumably
not
being
available
in
that
size,
or
something
like
that.
So
I
think
that
would
just
to
make
sure
that
any
presumably
any
changes
on
that
edit
screen
are
also
invoking.
Another
API
call
do
double
check
that
it's
like.
Oh,
you
changed
the
size.
We
may
need
to
take
the
available
colors.
F
E
Absolutely
and
that
functionality
we
currently
have
in
the
PD
page
Jim
will
have
that
in
mind.
When
he
did
the
product
detail
occasion,
I
was
thinking
it
would
be
literally
quite
same
functionality.
It's
just
you
don't
have
the
impression
of
leaving
the
car,
because
that's
kind
of
muddled
with
I
mean
you
leave
the
car.
Do
you
go
back
to
PD
page
we
would
have
to.
E
E
A
E
A
C
A
A
Maybe
we
can
make
a
couple
small
changes
here
and
then
they
just
show
the
big
beginnings
of
some
of
the
chain
and
then
carve
out,
and
maybe
that's
what
we
do-
that
that
second
pane
that
full
editing
experience
and
then
clone
most
of
this,
but
that
that
that
is
taken
consideration.
So
I
think
your
notion
has
convinced
me
to
do
so,
and
so
maybe
for
the
purposes
of
this
estimation,
let's
just
consider
this
experience
and
then
and
then
we
can
come
back.
A
C
G
Reason
so
the
reason
that
I
suggested
what
I
suggested
is
that
if
you
observe
this
to
be
a
collection
of
composed
together
bits
of
functionality,
the
card
item
itself
and
then
a
place
where
injected
interactive
functionality
goes
that
gets
bound
and
then
that's
an
example.
Implementation
of
that,
then
that's
a
natural
place
for
story
separation,
but
it's
incumbent
on
the
developer
to
suggest
that
split
so
that
Eric
can
write
it
down.
G
I
can
do
it
I'm,
just
I,
don't
want
to
stomp
all
over
everyone
I'd
like
to
encourage
people,
maybe
to
see
what
I'm
seeing
and
if
they
can
see
along
those
lines,
then
start
volunteering
that
you
could
take
one
of
those
things
like
just
the
base
implementation
of
the
card
item
that
doesn't
have
the
Edit
ability
strategies
and
then
also
an
acceptance.
Criterion
of
that
story
would
be
that
you
add
a
place
where
such
a
thing
would
go.
You
know
a
place
where
children
are
injected
to
get
bound.
That
kind
of
thing.
A
A
A
E
A
Kidding
there
we
go
alright
great
everybody
see
the
screen
seen
it
love
it,
excellent,
cheering
it
caring.
So,
let's,
let's
get
to
the
as
to
the
estimate
here.
So
again,
you
guys
know
where
I'm
gonna
start
on
this
one.
So
what
are
your
thoughts
on
on
this
one?
From
a
from
an
estimation
standpoint
now
that
we've
got
just
a
clean
single
panel
here,
we'll
do
the
other
one.
Next.
G
G
C
Just
from
the
streamlines
we
were
talking
about,
it
sounds
like
the
only
real
API
call
and
Redux
action.
We're
gonna
have
to
implement
is
the
remove
item.
Everything
else
is
not
really
going
to
have
an
action
associated
with
it.
It's
basically
just
a
UI,
build
out
unless
I'm
misunderstanding
something
about
the
issue,
but
to
me
that
sounds
like
that
could
be
done
in.
I
A
And
then,
how
do
you
feel
about
the
uncertainty
around
the
add
to
favorites?
Do
you
think
there's
enough,
at
least
for
you
to
tackle
that
with
at
least
from
a
presentation,
layer
standpoint
or
do
you
feel
like
you
need
a
little
bit
more
of
an
estimate
to
at
least
consider
that
what
are
your,
what
are
your
thoughts
on
that
and
that's
the
one
that
worries
me
a
little
bit,
it's
a
little
bit
more
ambiguous.
C
Yeah
I
guess
that
is
another
API
call
at
that
point.
I
think
that
I
mean
that
sounds
like
a
bit
of
discovery,
but
as
far
as
the
magenta
API
documentation,
I've
felt
pretty
confident
about
looking
stuff
like
that
up,
it
seems
like
they're
pretty
well
documented.
It
doesn't
seem
like
it
would
be
too
much
work,
but
I
could
easily
be
convinced
that
this
could
turn
into
a
five
like
I'm
I'm,
not
super
hard
set
on
the
three.
That
was
just
my
initial
reaction.
G
J
G
A
I
think
growing
on
this
one
I
think
we've
given
some
thought
I,
don't
believe.
We've
covered
that
yet,
with
some
of
the
some
of
the
work
so
I
think
we're
open
to
stuff
for
this
I.
Don't
think
we
need
to
worry
so
much
about
what
that
that
reaction
might
look
like
on
the
screen,
but
I
do
think
it's
some
point.
We
need
to
come
back
around
to
that.
E
Would
say
that
whatever
it
is
it
they
should
all
all
those
actions
should
probably
accept
the
remove,
which
would
ask
which
will
ask
you
for
confirmation.
I
would
follow
the
same
thing
that
we're
doing
folk
art
item
updated,
which
is
at
the
top
of
the
screen,
where
it
has
added
two
favorites
that
we
expected
seeing.
The
result
of
an
action
is
always
in
the
same
place,
and
it's
not
changing
for
every
action
got.
C
E
A
Let's,
let's
note
that
I
know
Jimmy's
Jimmy's
out
today,
so
if
I,
like
the
note
note
this
one
so
Tommy
could
you
on?
Could
you
fill
it
out
a
little
bit
for
me,
real,
quick,
so
I
can
capture
that
to.
E
A
All
right
that'll
be
a
present
for
Jimmy
when
he
gets
back
on
Monday
excellent,
all
right,
good
questions
that
well
we'll
put
that
on
and
so
I'm
feeling.
With
some
of
the
questions,
we
have
there's
a
little
bit
of
there's
a
little
bit
of
ambiguity
on
some
of
these
things,
none
of
which
we're
staffers,
but
I
mean,
but
it
does
me
feels
like
it
adds
a
little
bit
of
weight
to
the
estimate,
which
again
is
okay.
A
I
would
rather
I'm
feeling
better
about
a
five
versus
a
three
on
this
one,
because
there's
some
room
for
interpretation
and
back
and
forth
they
just
without
without
any
more
we're
not
going
to
be
able
to
get
those
questions
answered,
but
again
not
nothing
to
stop
things.
What
is
them
so
with
that
in
mind,
what
does
everybody
feel
about
a
five
on
this
one
that.
A
Right
can
I
get
a
second
for
a
five
any
any
second,
all
right,
James,
so
excellent,
very
good.
All
right,
let's
go
and
close
this
without
then
so
we've
got.
Does
this
one?
That
concludes
the
the
Edit
ability
of
the
mini
cart.
I
will
I,
will
clone
this
one
and
then
and
then
again,
take
I
get
the
latest
from
samya
on
the
details.
Page
of
that
one.
That
alone,
based
on
what
was
perceived
to
be
a
short
story
for
today,
will
probably
take
a
good
chunk
and
I
don't
want
to
I.
A
Don't
want
to
I
just
do
that
ad
hoc,
so
we'll
move
that
to
the
top
of
the
list
for
next
week
to
make
sure
you
got
all
those
taken
care
of,
but
also
who's,
some
of
the
learnings
from
this.
So
let
me
go
ahead
and
save
this
one
out
there
we
go
alright,
so
we've
got
one.
We
got
one
of
these
ends,
which
is
fantastic,
so
we've
got.
We've
got
approximately
18
minutes
left
here
until
close
I'm
a
little
worried
about
opening
up
search
with
that
limited
amount
of
time.
Yeah.
I
A
I
am
a
product
standpoint,
I'm
very
eager
and
excited
about
search,
but
I
do
worry
about
this,
something
that's
a
little
bit
a
little
bit
more
straightforward,
and
if
we
have
time,
if
we
do
that
very
quickly,
I
at
least
want
to
introduce
the
idea
of
kind
of
a
very
minimum
search
to
at
least
get
us
thinking
for
next
time.
How
does
that
time.
A
I
put
the
wrong
it's
the
wrong
screen.
This
is
not
good
all
right,
so
let
me
so
we're
going
to
take
a
look
at
the
updated
order.
Confirmation
for
for
venya
what
you're
seeing
here
is
not
the
updated
order.
Confirmation
I've
got
the
wrong
screen,
but
the
story
is
like
I've
got
this
on
yeah,
it's
a
clone,
sorry
guys,
so
the
updated
order.
Confirmation
is
267.
The
idea
here
is
to
take
take
with
what
we've
got
on
the
confirmation
in
the
venue
prototype,
which
is
this
guy
right
here.
A
A
That's
the
shipping
and
payment
method,
but
then,
at
the
end
we
have
an
extremely
basic
creation
of
an
order,
but
it
doesn't
include
some
of
the
niceties
that
sound
means
put
together,
which
is
the
order
number
which
seems
basic,
that
we
still
want
to
pull
that
out.
The
beginnings
of
where
we
would
link
to
for
an
order,
detail
screen,
which
you
want
to
know
if
they're,
making
a
purchase
and
then
the
beginnings
of
the
beginnings
of
creating
an
account
which
then
links
to
where
bargaining
is
starting
off
with
with
that
login
screen.
A
And
so
again,
this
one
should
be
pretty
straight
for
a
lot
of
its
content,
but
there'll
be
a
little
bit
of
a
little
bit
of
work
pulling
in
some
of
the
samples.
Some
of
the
data
of
the
recently
created
order,
based
on
based
on
things
to
add
to
get
this
going
so
maybe
more
straightforward
to
understand,
maybe
a
little
bit
more
work
on
discovery,
but
that
is
the
that's.
That's
the
thinking
there.
E
E
E
D
D
D
E
A
Me
I'm
gonna,
look
out
for
it.
I'm
gonna
say
that
the
the
reference
design
is
work
in
progress.
I
agree
with
Anton
I
think
we're.
What
we
want
to
do
here
is
to
advance
this
and
start
to
think
about
linking
together
some
of
the
things
that
are
in
flight
and
building
off
what
we've
got
so
I
think
it
achieves
that.
But
we
will
not
declare
this.
A
You
know
this
final
until
we
get
to
that
point,
but
I
do
want
to
link
in
some
of
the
work
that's
being
done
on
the
on
the
authentication
piece,
which
this
is
a
perfect
place
to
do
that
and
start
to
pull
in
data
around
that
order.
Number
what
you
still
haven't
done
yet,
and
that
alone
is
probably
a
nice-nice
story
and
that's.
A
A
N
plus
one
for
this
one,
so
so,
let's
take
a
look
at
this
one
I
think
this
will
certainly
carry
us
to
time
here,
but
I
wanted
to
kind
of
go
start
off
with
what
we
had
here.
I'm
gonna
change
out
the
image
here,
based
on
what
we've
got
here,
but
the
idea
here
is-
and
the
story
is
right
as
a
shopper-
I
want
to
have
the
immediate
access
to
the
order
that
I
have
placed
after
checkout,
so
that
I
can
check
the
status
at
any
time.
A
The
actual
linking
to
the
order
itself
doesn't
require
authentication.
You
can
go
into
an
again
areas-
that's
kind
of
nice
for
that
continue
shopping
this
in
the
scenario
that
we
have
and
then
create
an
account
would
be
stubbed
out
initially,
but
then
link
to
the
work
that
bargaining's
picked
up
for
that
one.
So
that's
the
that's
the
idea
here
and
then
so,
as
as
a
shopper,
you
want
to
be
able
to
go
back
to
that
order.
It's
really
just
a
this
is
copied
over
from
search.
E
A
Worries
I
was
in
the
process
of
cloning.
That's
before
grooming,
so
so
for
this
one,
it's
simply
just
a
what
we
wanted
to
simply
just
a
in
extension
and
of
current
order.
Confirmation.
A
A
A
J
A
Assumptions
would
be
States
what
I'm
trying
to
figure
out
a
way
to
capture
the
states
where
this
is.
This
is
a
necessarily
covered
indicated.
States
assented
state
of
confirmation
future.
So
the
idea
is
that
you
wouldn't
be
asked
to
go
to
an
account
if
you
already
authenticated.
That's
not
part
of
the
story.
Anyone
just
do
links
for
that.
The
tasks
themselves
would
be
the
discovery,
so
we'll
be
able
to
do
discovery
to
retrieve
order.
A
D
A
Perfect,
and
so
the
task
is,
as
we've
got,
that
will
reference
the
current
check
out
in
LUMO
and
the
sorry
in
the
rest
call
from
luma
future
considerations
for
ordered
details.
So
this
is
identifying
that
once
you
basically
so
maybe
stories
based
on
the
design
where
we
leave
off
with
and
then
first
testing
and
documentation,
but
essentially
in
its
most
basic
form.
It
is,
it
is
just
a
creation
of
this,
and
so
the
idea
is
to
go
there
and
be
able
to
create
a
Cal
tell.
D
A
D
A
They
should
actually
just
go
to
the
the
actual
creation
of
the
account
experience.
That's
all
handled
under
a
separate
story.
This
was
supposed
to
be
very
simple
where
it's
just
just
this
screen,
the
other
screen
has
actually
been
groomed
and
there's
being
done
well.
Why
here?
So
why
not
in
this
story.
D
D
A
It
it
could
be
I
think
it
just
links
to
something
that
already
does
that
so
I
think
it
I
think
we
have
a
coverage,
but
please
keep
you
honest,
I
I
can
I
think
I
can
make
sure
you
all
find
the
the
experience
that's
being
built
right
now
for
the
check
out.
I
think
it's
I
think
it's
being
covered
in.
Essentially
this
is
just
linking
those
together,
but.
D
D
So
that's
order
confirmation,
page
right
right,
so
that
order
is
confirmation
page
we
from
here
we
don't
with
it
the
best.
It
would
be
a
bad
experience
to
send
the
user
to
create
accounts
for
because
what
others
that
would
be
weird,
why
do
I
need
to
fill
in
the
form
if
I
already
filled
all
the
data
during
checkout
I'd
because
doing
check
my
by
specified
right
so
and
how
it
works
today,
either
you
you
go
to
check
out
the
checkout
place
order
and
there
is
there
is
a
button
create
accounts?
It's
all.
D
D
What
happened
so
this
would
be
much
simpler
to
do.
Oh
yeah,
here
the
create
account.
You
show
two
forms
at
password
and
you
basically
do
a
rest
request.
That
is
already
a
thing
happening
that
is
yeah.
So
this
is
something
that
could
be
quickly
implemented
and
this
effectively
you
don't
have
to
wait
for
that
story.
The
customer
gestation
form
is
important.
At
least
I
would
say
lower
priority
than
just
creating
a
sound
from
mortars.
Sure
so
I
would
again
you
decide.
D
A
Get
the
yeah
I
think
I
think
your
point
is:
if
I
understand
Ray's
independence
and
if
this
is
created
independent
of
the
other
ones,
then
yeah
actually
I
could
see
that
so
that
that
makes
sense.
If
we
can
clarify
that
where
you
would
create
it,
but
then
when
we
create
the
other
experience,
they
would
be
stitched
together
and
we
wouldn't
have
to
tell
day.
D
They
would
be
independent
from
here.
You
don't
want
even
like
even
in
the
dark
state
and
final
thing,
you
don't
want
to
sound
user
to
customize
accommodation
form.
It
would
be.
It
would
be
like
surprise
the
fact
they
already
used
to
experience
that
they
have
on
carbon
magenta
check
out
I
think
they
have
another
stores
where
you
filled
all
your
information
during
checkout.
Why?
Why
are
you
being
redirected
by
Marriott,
formal
registration?
Do
you
already
have
all
information
just
say
that
information
from
from
the
filter?
A
All
right,
let's
see
on
this
one,
so
let's,
let's
talk
about
where
we
left
off
on
this
one,
so
we've
got
again.
This
was
a
copied.
Sorry
guys!
Let
me
bring
vertigo
here.
No.
A
A
Reference
design,
of
course,
is
work
in
progress,
tasks,
I
think,
makes
sense,
but
I
think
what
we
want
to
do
is
I.
Think
Anton
has
a
good
point
in
terms
of
the
independence
of
this
versus
the
the
other
screen,
so
I
think
yeah.
It
would
be
great
to
it'd
be
great
to
have
a
have
a
situation
where
we
simply
would
just
ask
for
a
password
for
the
air
for
the
create
account
on
there
and
that
would
just
be
completed
before
we
would
link
this
and
so.
A
A
Get
your
considerations
I
wouldn't
worry
about
that,
and
this
is
copies
and
search
and
that
reference
design,
I
will
copy
this
and
I
think
that's
it.
So,
in
terms
of
the
basics,
again,
we're
still
pulling
in
this
information
we're
going
to
use
as
much
as
we
can
to
create
that
accounts,
which
would
be
the
completion
of
this
particular
story,
and
that's
it,
and
so
so,
assuming
that
we
can
all,
in
the
back
of
our
mind,
see
that
visual
and
how
that
works.
A
C
A
D
Point
is
that
it
wouldn't
be
temporary.
Yes,
we
would
meet
the
customer,
account
creation
form
separately
and
if
there
would
be
a
link
to
that
page,
but
from
for
the
creation
we
already
have
all
the
user
information.
So
the
only
thing
we
have
to
do
is
to
do
a
request.
Magenta
get
user
password
to
do
request
to
magenta
to
create
account,
make
sense.
D
G
I
mean
I
got
I,
got
it
in
yeah
hold
on
a
second
hi.
I
was
just
looking
at
the
api's,
which
does
everyone
here
understand
by
the
way,
how
to
call
up
an
actual
like
REST,
API,
swagger
doc,
that's
complete,
because
it's
if
you
experienced
with
Magento
it's
pretty
straightforward.
If
you're
not,
then
it's
weird
about
the
Magento
swagger,
yes,.
G
D
F
I
F
Like
a
final
final
bomb
to
lob
in
the
fire
run
off
to
a
different
meeting,
is,
would
you
do
you
consider
this
somewhere,
where
this
would
be
component?
Reuse
like
you,
would
have
a
single
component
that
is
collecting
the
account
details
that
may
display
them
as
form
inputs
or
may
display
them
as
prefilled
forms
that
is
used
in
both
location.
Or
do
you
consider
these
entirely
separate
components
that
I
just
happen
to
submit
to
the
same
function?
I.
D
My
my
understanding
is
the
best
practice
for
check
out
that
you
place
order.
You
see,
order
confirmation
page,
you
are
offered
to
create
account,
you
see
two
passwords
fuse
or
they
can
be
there.
You
enter
your
password
twice
and
then
create
account,
and
that's
it
that
all
you
do.
The
account
is
created
for
you
order.
A
A
With
this
I
know
we
had
some
ideas
around
this,
but
I
think
I
think
we
all
understand
the
the
need
for
utilizing
what
we
already
know
about
the
order
to
create
the
account
I
just
want
to
do
a
quick
review
that
maybe
I
can
again
will
be
being
respectful
for
some
of
the
folks
in
Europe,
where
this
is
fairly
late
at
the
end
of
time
here,
let's,
let's
a
little
tease
it
for
next
week,
a
good
discussion
for
that,
but
but
again
super
appreciate
everybody's
time
on
this.