►
From YouTube: Magento PWA Backlog Grooming, 17 August 2018
Description
Weekly product backlog grooming for Magento PWA.
A
A
D
C
Volunteering
ideas
even
outside
of
backlog,
and
we're
really
grateful
for
the
participation
on
that.
This
is
Mark
wine
he's
new
as
well
he's
an
intern
who
was
so
excited
about
pw8
studio
that
he
decided
to
become
an
external
contributor
on
his
last
day,
and
then
we
have
our
Jim
Costa,
who
is
was
comm,
wrap
in
you
based
in
Germany,
right,
yep,
yep
and
art
has
been
helping
with
the
new
ideation
so
and
then
I
guess
more.
F
E
E
E
So
when
today,
we'd
like
to
make
some
progress
on
the
again
navigation,
also,
the
shipping
and
the
beginnings
of
payments
and
what
we're
gonna
do
is
I
base
that
off
of
the
current
state
of
engine.
So
what
I've
done
is
kind
of
created.
Some
preliminary
stories
on
this
we'll
go
through
this
in
detail.
I
definitely
want
to
get
your
feedback,
especially
on
things
like
tasks
and
assumptions,
so
they're
know
so
they're
kind
of
work
in
progress
on
that
well.
E
But
the
essence
of
here
is
that
we
want
to
make
progress
on
things
that
traditionally
been
part
of
our.
You
know
work
in
progress
versus
the
theme,
so
so
I've
got
this
up
and
running
on
our
local
set
up.
Many
thanks
to
Paul
and
many
others.
I
think
I've
inspired
others
to
get
this
set
up,
which
has
been
great
and
so
on.
So
what
been
running
this
with
a
traditional
product
page,
but
as
you
can
see,
there's
definitely
work
to
be
done.
Things
like
wish
lists
and
others
are
gonna,
be
in
future
phases.
E
But
as
you
as
you
look
at
these
experiences
and
begin
to
add
to
cart',
you
know,
we've
made
a
lot
of
assumptions
and
along
the
way
right.
You
know
we
don't
have
yet
the
ability
to
change
the
quantity.
Do
we
have
the
ability
to
change
change
or
even
remove
these
from
the
from
the
from
the
from
the
entire
cart
experience,
but
they
do
create
complete
orders,
which
is
fantastic.
E
That
was
really
the
the
kind
of
the
big
effort
in
the
most
recent
milestone,
but
we
want
to
start
doing
is
take
a
look
at
things
like
navigations.
Now,
one
of
the
things
that
Jim,
Ian
and
others
have
done
have
created
some
placeholders
here
that
just
you
know
quite
honestly,
just
needed
an
opportunity
and
someone
to
help
drive
this
home
based
on
the
latest
design
work.
As
you
can
see,
the
the
design
work
we've
got
here
and
in
vision
is,
is
really
an.
E
You
know
well
ahead
of
kind
of
where,
where
we
want
to
be-
and
we've
got
some
really
good
thinking
from
saamiya
and
team
on
what
this
might
look
like.
So
with
today's
with
today's
today's
grooming
we're
gonna,
take
you
take
a
look
at
again
the
beginnings
of
navigation,
which
may
seem
straightforward,
but
we
want.
E
We
want
this
to
be
data-driven
and
so
will
so
we'll
go
through
some
examples
there
based
on
you,
know,
based
on
that
and-
and
you
know
see
what
we
can
do
to
kind
of
address
the
gap
between
what's
designed
and
what's
currently
in
developed
and
again
taking
advantage
of
some
of
the
recent
API
work
that
know
that
James
and
many
others
have
been
doing
I'm
kind
of
that
layer
in
between
graph,
QL
and
kind
of
the
the
rest
approach,
especially
recently
for
the
checkout.
So
that's
we're
gonna
start.
E
So
these
are
so
we're
going
to
start
off
here.
The
navigation
menu
so
we'll
go
through
some
assumptions
and
stories
on
that.
As
you
can
see,
that
is
a
bit
different
from
that,
and
so
we'll
take
a
look
at
that
and
then
and
then
we'll
again
will
we
then
move
into
things
like
the
the
the
shipping
methods
which,
again,
if
you
see
in
our
in
our
existing
checkout,
losing
this
or
static
right?
And
so,
if
you
go
and
go
into
the
carts,
go
ahead
and
start
check
out
again,
Jimmy's
done
a
fantastic
job.
E
Actually,
this
doesn't
even
have
the
recent
work
on
the
shipping
work,
which
is
which
is
great,
but
then
you
know
the
idea
of
you
know
getting
it
by
a
certain
date
with
a
certain
shipping
back
old.
The
way
magenta
to
does
that
right
now
is
just
to
fix
rates
we
to
fixed
methods.
We
want
to
pull
that
into
to
this
experience.
E
That's
that's!
That's
really
the
goal
and
again
I
just
for
the
purposes
of
this
call
because
I
know
we
have
folks
joined
in
and
out
of
this
I
wanted
to
kind
of
show,
we're
you
know,
kind
of
where
we
are
and
where
we
want
to
go,
and
then
I've
got
some
supporting
materials.
Here
from
samya
who's
out
today
on
the
on
the
prototype
and,
of
course,
our
luma
theme,
which
keeps
us
honest
in
terms
of
the
parity
between
you,
know,
kind
of
2.2
and
kind
of
where
we're
going
with
2.3
with
PWA
awesome.
C
C
Another
one
is
something
that
if
you
explore
it,
it
seems
a
little
bit
missing
like
change
in
quantity
and
then
another
one
is
just
something
that
seems
obviously
like
it
ought
to
impart
this
scenario
or
something
that's
noticeable
and
not
doing
what
it
ought
to
be
doing,
and
example
for
that
might
be
that
the
homepage,
where
we
begin
our
scenario
and
the
cool
category
component,
that
our
team
built
in
many
cases,
images
now
that
actually
may
be
a
graphic.
You
will
both.
A
C
We
have
and
are
trying
to
order
more
and
more
stories
have
the
basic
things
you
need
to
get
started
up
and
up
above
and
beyond,
just
having
a
development
environment
first
place.
You
need
to
have
a
acceptance
criteria,
you
need
to
have
a
user
story
and
that
story
needs
to
be
described
from
the
point
of
view
of
one
of
our
personas,
the
the
shopper
Sheila,
the
H.
C
What
you
want
to
do,
okay,
what
you
want
to
do
is
have
a
story
with
acceptance,
criteria
and
user
story
definition
endings,
one
of
those
personas
and
as
much
collateral
as
necessary
to
get
going
and
usually
for
the
UI
and
theming
stories.
That
means
that
we
look
through
the
venía
materials
that
Samia
has
produced
and
iterated
upon
and
that
James
has
produced
and
iterated
upon
in
terms
of
the
written
down
best
practices.
Mr.
C
C
E
Think
fair
game,
for
this
also
is
if
we,
if
we
uncover
that
one
of
these
stories
is
just
too
large
and
we
get
you
know
we'll
know
when
we
see
it
we'll
break
it
up
right
so
I
said
we
made
some
assumptions
of
what
we're
gonna
be
presenting.
But
let's
be
let's
be
completely
honest:
if
this
can't
be
done
in
a
two-week
sprint,
let's
break
it
up
and
that
could
be
some
of
the
preparation
could
be
some
of
the
documentation.
I
think
those
are
all
fair
game
for
what
we're
trying
to
do.
E
E
C
Yep,
that's
excellent
news
because
envision
itself,
if
it
can
be
kind
of
difficult
to
access,
we
had
some
trouble
with
it,
and
our
thought
was
that
whenever
you
needed
some
additional
access
that
we
could
just
give
you
a
particular
comp.
But
it
sounds
like
people
can
just
navigate
it
themselves,
which.
E
Is
great
again
it's
a
little
bit
of
both
right
I.
Think
we're
gonna.
Try
to
do
is
put
more
of
the
snapshots
inside
of
these
work
out
in
which
helps
with
you
know,
yeah
access
and
things
of
that
nature.
But
for
those
who
want
to
just
explore
around
with
this,
you
know
we
can.
We
can
do
a
quick
share
as
and
that's
a
there's,
a
nice
way
to
kind
of
work
from
that
that
sound
me
and
set
up
for
us
so
yeah
any
any
other
questions
before
we
get
started.
E
All
right
so
well,
so,
let's
start
off
with
navigation,
again
I
kind
of
went
through
at
a
high
level,
the
types
of
things
that
we
were
looking
to
cover
here
and
so
essentially
again
going
back
to
to
where
we
are.
Currently,
we
want
an
experience
that
goes
from
this,
which
is
kind
of
static
forms
of
all
the
categories
they
currently
are
assumed
assumed
in
in
the
venya
catalog,
but
then
to
take
it
into
something.
E
That's
a
little
bit
more
more
traditional
in
terms
of
menea
doesn't
necessarily
have
to
have
the
thumbnails,
but
what
it
does
represent
is
a
three
level
menu
and
some
really
interesting
interactions,
and
so
for
those
are
really
really
keen
on
some
of
those
micro
interactions.
The
sliding
the
closing
going
back
to
again
one
of
three
states,
primary
secondary
and
tertiary,
represents
a
really
interesting
case
to
kind
of
take
a
look
at
again
bring
in
real
data
from
the
product
and
catalog
from
m2
to
help
power.
E
This
person's
kind
of
a
placeholder
one
that
we've
got
right
now
so
I'd
love
to
talk
about
this
a
little
bit
more
again
at
first
blush.
This
is
fairly
straightforward.
A
lot
of
the
design
specs
are
baked
into
the
the
documentation,
but
also
the
other
prototype
itself,
but
there
are
some
you
know:
I
expect
there
will
be
some
questions
on
things
like
you
know
the
special
treatment
that
we've
got
for
sale
and
clearance,
and
you
know
what
are
some
of
the
edge
cases.
E
If
you
know
somebody
puts
a
hundred
different
categories
in
this
and
like
those
types
of
things
which
you
think
are
all
fair
game,
but
the
purpose
of
this
is
to
find
that
starting
point,
and
so
for
the
you
know.
For
the
purposes
of
this.
It's
it's
about.
You
know
a
shopper
and
a
shopper
in
this
case
wanted
to
browse
the
store
from
a
prominent
location
on
the
storefront
and
clicking
the
menu
of
some
sort
and
then
accessing
categories
and
accounts,
so
they
can
make
a
purchase.
E
E
C
Link
there,
it's
part
of
the
basics,
acceptance
criteria
yep
just
in
order
to
provide
room
yep
in
the
UI
that
you've
made
so
that
we
don't
have
to
cram
something
in
there
later
yeah.
This
is
mostly
about
building
the
UI
and
then
filling
it
out
with
what
data
you
can
access.
The
data
story
involves
as
much
graph
QL
as
possible,
and
sometimes
that
coverage
is
not
complete
or
it's
buggy.
C
E
Absolutely
so
I
think
with
that
in
mind.
Let's
talk
about
a
couple
considerations:
is
this
enough
to
get
started?
I
think
if
there's
kind
of
a
test
right
there
are
these
the
right
assumption.
So
these
the
right
task
and
I
think
once
we
feel
like
we've
got
a
consensus.
What
would
be
a
good
estimate
of
this
again
using
the
same
same
model
we
had
before?
So?
What
do
you
guys
think
is
this
enough
to
get
started.
C
Barring
that
what
information
are
you
missing,
that
is
preventing
you
from
making
some
kind
of
estimate
very
very
mind
for
those
of
you
who
are
new.
Our
estimates
are
basically
small,
medium,
large
or
huge.
If
you're
familiar
with
doing
Fibonacci
estimation,
we
do
one
two
three
five,
eight
or
13,
if
you're
well,
if
you're
nasty.
E
A
H
Almost
all
our
projects
include
some
special
menus,
not
only
the
categories
inside
menu,
also
external
link
link
for
some
pages,
long
extension
somehow,
but
in
general
same
as
pages
and
external
name,
maybe
directing
for
product
not
really,
but
for
shirts.
Ms
pages
antics,
external
links.
Do
you
have
to
keep
in
mind.
C
C
So
when
this
comes
down
from
the
category
API,
it
will
have
enough
metadata
to
tell
you
which
type
of
link
it
is.
We
hope,
and
if
not,
that
is
something
to
identify.
I
know,
for
instance,
that
graph
QL
right
now
does
not
supply
the
full
navigation
tree
unless
I
am
way
out
of
touch.
Am
I
way
out
of
touch
let's
find
out
I'm
gonna
use
graphical
on
my.
I
C
C
All
right
in
I
would
say
if,
if
you
want
to
look
at
the
at
the
Magento
codebase
in
github,
you
can
search
that
codebase
is
something
that
I
like
to
do.
If
you
just
go
on
your
machine,
if
you
don't
want
to
go
to
github.com,
slash,
Magento,
slash
magenta,
oh
yeah,
just
the
regular
Magento
organization,
slash
engines
or
a
cool
thing
I
like
to
do
is
in
the
search
box.
Actually,
no,
not
even
the
search
box,
you
just
type
cheats,
so
type
T
yep
and
then
schema
dodge
dot,
graph,
QL,
email,
I'm.
C
C
What
has
been
defined
using
is
a
very
readable
graph.
Ql
schema
definition
language
if
you
click
any
of
those.
Like
your
look
at
catalog
graph,
QL
SC
schema
graph,
QL
KS,
which
I'm
sorry.
It
says
five
up
from
where
you
are
one
more
down
yeah,
so
hit
head
in
there.
Alright
and
you'll
see
that
just
right
here
in
the
code
in
the
current
date,
we
have
a
query
type
that
is
defined
so
that
you
can
ask
for
products
and
categories
at
the
root
tree,
and
these
things
are
very
extensively
documented.
C
C
C
G
C
C
C
I
C
C
C
I
C
So
can
you
guys
see
my
graphical
front-end
here,
yep
with
it
with
the
introspection
queries,
it's
able
to
just
kind
of
look
through
what's
possible
and
so
I
look
through
queries
and
I
see
that
down
here
the
things
that
you
can
look
for,
our
the
URL
resolver,
which
is
something
that
PWA
uses
in
the
backend
category
products
store,
config,
customer
and
custom
attribute
metadata,
and
so
again
you
can
go
through
the
category
tree
and
then
that
is
a
recursive
data
structure.
So
you
can
see
its
children
its
products.
C
And
so
if
your
navigation
is
all
categories,
then
this
will
totally
do
you,
but,
like
art
says
that's
not
what
navigation
necessarily
is
its
categories?
Products
CMS
pages
and
the
business
user
can
choose
to
reorient
at
that.
Yeah
I!
Don't
see
that
here,
but
don't
take
my
don't
take
me
for
granted.
If
you
guys
a
maybe
a
branch
or
a
technique
that
you're
using
to
actually
derive
real
navigation
out
of
this
then
I'm
all
ears.
What
do
you
got.
C
C
So
is
there
navigation
I,
don't
see
it,
so
this
is
a-ok
so,
rather
than
continue
to
go
down
this
rabbit
hole.
I
will
say
that
this
seems
to
be
a
significant
part
of
this
story.
Yeah
after
the
creation
of
the
UI,
then
actually
getting
it
to
populate
with
all
the
navigation
types
that
art
you
mentioned
might
have
to
be
a
follow-up
story
yep,
and
so
this
one
our.
If
you
think
this
is
okay.
C
H
C
E
Right
so,
as
you
guys
see,
I'm
just
kind
of
keeping
up
here
so
I
think
we're
gonna
rely
upon
the
category
tree
for
graph
QL
yeah,
where
he's
gonna
be
needed
for
that
and
the
tasks,
I
think,
are
still
still
fair
game
again.
Basically
shoring
up
the
visual
there
we're
just
basically
the
the
criteria.
This
is
good,
see
how
far
we
can
get
and
based
on
some
of
the
limitations
of
graph
QL
and
thing.
E
Both
we
can
actually
partner
with
the
graph
QL
team
to
identify
and
there's
even
tag
associated
stories
as
that
keep
setting
keeps
getting
flushed
out
so
cool
excellent,
all
right
anything
else
on
this
one
that
will
at
least
preclude
us
from
an
estimate.
How
are
we
feeling
we've
answered
the
data
question
all
right.
We
know.
I
E
C
C
E
J
E
C
Right
now
it's
fairly
loose
down
the
weave.
We
aren't,
you
know
imposing
very
strict
test
coverage
metrics
at
the
current
time
till
we
get
two
scenarios.
So
I,
don't
think
you
know.
That's
gonna,
take
a
lot
of
time,
but
I
do
want
to
caution
that
recursing
through
a
tree
with
graph
QL,
is
something
you
have
to
get
used
to
a
little
bit.
C
If
you
haven't
done
it
and
the
building
of
the
UI
in
such
a
way
that
it
won't
jank
under
any
circumstances,
part
of
our
definition
of
done,
and
so
that's
that's
something
that
takes
a
little
bit
of
extra
skill.
I
would
I
would
put
this
at
a
five
if
I
was
being
careful
which
I
I
so
rarely
am
okay,
then
you.
E
All
right,
very
good,
I
think
this
is
I,
think
this
one's
sort
ordered
that
any
any
other
questions
on
this
one
before
we
close
it
up
all
right.
Let's
do
it
all
right,
so
this
is
number
240
this
one's
in
good
shape.
We
will
reach
out
to
you
guys
in
terms
of
who
can
take
this
on
than
the
way
we're
you
know
technically
min
sprint
on
this
one,
but
with
the
community
work
we
run
this
one
a
bit
hybrid.
E
If
somebody's
willing
to
pick
this
up,
let
us
know
and
we'll
reach
out
to
others
outside
of
this
call
as
well.
So
thank
you
for
that
one.
So,
let's,
let's
not
switch
gears,
then
let's
look.
We've
got
a
bounce
about
half
an
hour
left
here.
I
think
we
can
do
shipping
methods
if
they
keep
it
pretty
simple
and
so
absolutely,
and
so,
let's,
let's
take
a
look
at
where
we
kind
of
where
we
are
and
where
we're
going.
So
with
regard
to
the
venue
work
again,
this
is
so
we
just
finished
navigation.
E
On
this
example.
We're
gonna
add
something
like
this
to
the
cart
again
like
we
did
before
and
right
now.
These
are
you
know
these
are
just
a
kind
of
content
areas
and
so,
with
with
regard
to
shipping,
it's
the
it's.
The
idea
of
getting
into
this,
get
it
by
type
of
experience,
and
so
they
get
it
by
experience
is,
is
a
essentially
a
combination
of
date,
estimates
plus
method
for
the
purposes
of
MVP.
We
get
a
bit
fancy
on
on
the
UX
for
the
date
estimate.
E
Surely,
if
we
get
that
I'd
be
fantastic,
but
but
just
showing
the
method
itself
I
think
would
be
would
be
great,
and
so
you
see
here
in
the
example
here
from
the
edge
from
the
envision
prototype.
Just
a
you
know,
just
a
basic
value
of
basic
means
to
select
something
in
the
case
of
again,
we've
got
free
standard
shipping,
but
traditionally
the
data
just
shows
something
like
a
flat
rate
or
a
best
way.
I
think
that
alone
would
go
a
long
way
and
be
able
to
select
something
again
programmatically.
E
So
if
we
have
to
call
this
flat
rate-
or
you
know,
foo
man
rates
or
whatever
we
want
to
call
it,
it
should
pull
that
in
in
a
programmatic
way
based
on
the
values,
the
estimates
that
we've
got
there
from
that
and
said:
that's
that's
kind
of
how
I
broke
this
out,
but
in
terms
of
the
visual
appearance,
I'd
love
to
kind
of
tack.
This
on
to
where
we
started
off,
with
a
at
least
the
beginnings
of
the
mini,
mini
cart
and
checkout,
and
at
least
allow
for
that
selection.
E
That
selection,
of
course,
would
then
carry
through
go
into
the
order
itself
and
then
be
added
to
to
the
orders
in
the
admin.
So
that's
that's
the
goal
for
this
one,
and
this
is
the
Associated
visual
again
we're
looking
at
this
from
a
shopper
shopper
perspective
the
you
know
this
would
start
off
with
a
get
by
within
the
mini
any
meaning
credit
experience
pulled
from
a
Magento
to
current
and
assumptions
and
tasks,
and
you
guys
keep
me
honest
on
this
one.
G
E
Are
not
cognizant
of
your
location
or
things
of
that
nature
that,
of
course,
we
want
to
get
into,
but
also
then
update
the
order
summary.
So
there's
going
to
be
a
price
differential
in
this
one.
Let's
make
sure
this
or
this
this
this
tests
that
case
and,
of
course,
the
Associated
tasks
with
with
the
updating
of
shipment
and
and
then
they're
just
verifying
along
the
way
so
yeah.
This.
I
C
Remember
is
build
the
UI
first
get
plumbing
the
data.
Where
necessary.
You
know
the
person
who
has
works
the
most
on
this
individual
piece
of
UI
that
will
be
augmenting
is
Jimmy
and
Jimmy.
If
you
have
any
caveat
or
any
concerns
about
the
addition
or
the
change
or
you
want
to
talk
about
what
that
might
entail.
This
is
your
time
also.
If
anyone
else
wants
to
weigh
in
feel
free,
I'm
gonna
have
to
take
a
few
minutes
break
because
being
asked
to
I'll
be
quick.
E
Excellent,
all
right
we'll
take
it
from
here.
So
let's
look
at
this
from
two
categories.
Is
this
define
well
enough
for
an
estimate?
So
let's
say
I
kind
of
talk
through
that
and
then
talk
through
the
assumptions
and
tasks
there
and
then
I
think
once
you
reach
consensus
on
that
one,
let's
talk
through
the
the
estimate
itself
so
on
this
one
do
we
feel
like
this
is
enough
to
out
to
get
started
any
questions
or
concerns.
E
All
right,
I'll
assume
that
I
assume
this
one's
this
one's
well
understood
at
least
to
get
started.
Then
you
know
Jimmy
key,
be
honest
on
this
and
I'm
building
a
bunch
of
the
things
you've
got
got
here
as
well,
but
then,
if
this
is
well
understood,
so
what
do
we?
What
are
we
thinking
in
terms
of
an
estimate
for
this
and
again
based
on
where
we
were
before,
whatever.
G
E
Yeah,
so
the
I,
so
all
about
the
the
the
mock
in
this
one's
a
bit
misleading.
We
do
not
want
to
do
the
dates,
and
maybe
you
know
what,
for
the
purposes,
clarity
on
this
one
date
would
of
course,
would
be
fantastic
for
the
purposes
of
an
MVP,
not
the
dates
not
included
right
and
because
that
would
have
to
be
done.
Programmatically
based
on
location,
it's
gonna
be
just
fixed
and
in
this,
and
we
can
get
a
quick
update
on
this
one
from
from
Salian
team.
E
It
would
just
be
the
method,
so
free
standard
shipping
would
be
a
fixed
value.
It's
basically
one
of
these
two.
It's
probably
gonna
be
flat
rate
or
best
way
much
like,
and
this
is
what
I
had
in
the
background
this
guy
right
here.
This
is
how
it's
done
in
venya,
we're
basically
doing
a
one
to
one
on
this.
One.
D
The
thing
the
real
question
is
it's
whatever
it's,
whatever
the
API
requires
in
order
to
give
us
a
list
of
shipping
methods
back
yeah.
So
if
the
shipping
method
API
requires
a
location,
then
it
requires
location
right,
okay,
I,
don't
you
know,
I,
don't
know
what
those
API
requests
require.
That's
part
of
you
know,
that's
part
of
the
work
involve
tears,
figuring
out.
D
E
D
Right,
so
all
the
in
all
the
patterns
for
this
kind
of
stuff,
the
making
of
the
form
in
UI.
You
know
the
navigation
back
and
forth
between
the
overview
there,
where
you
click
into
it
and
how
you
save
it
or
cancel
out
of
it.
They
make
the
API
requests
wire
up
the
Redux
actions.
All
that
stuff,
you
know,
is
sort
of
proved
out
with
the
address,
and
so
this
is
basically
the
same
steps.
The
same
pieces,
just
a
different
API
request
and
a
different
slice
of
state.
D
E
D
E
F
D
E
I
would
say
down
yeah
and
just
for
everybody's
knowledge.
We
are
tagging
things
to
ethics.
We
do
have
milestones,
milestones
are
actually
our
sprints,
as
this
gives
a
sign
just
look
for
that
as
it
does
assign
these
very
clearly
and
then
releases.
So
for
those
who
aren't
following
forward
around
releases,
the
the
releases
themselves
mapped
to
quarters,
and
so
this
is
something
that
I.
You
know
ideally
we'd
love
to
get
done
by
the
end
of
September.
E
E
G
E
Let's
do
our
very
best
to
think
about
the
beginnings
of
payments,
so
payments
the
tricky
one
but
but
but
but
I.
Think
if
we
look
at
this
in
a
very
static
way,
which
again
you
know
we're
not
gonna
start
with
visa.
Here
we're
gonna
be
looking
at
something
that
is
more
akin
to
the
lumo
reference
store,
because
you're
calling
Luba
reference
store.
E
The
only
payment
method
is
programmatically
pulled
as
a
check
or
money
transaction,
and
so
we've
made
some
assumptions
in
the
the
current
instance
of
any
of
doing
so,
but
we
don't
want
to
be
able
to.
We
could
you
know,
for
example,
the
testing
of
this
could
could
choose
from
multiple
static
methods.
Maybe
it's
maybe
it's
that
check
or
money
order.
Maybe
it's
you
know
an
IOU
or
something
like
that.
E
So,
just
just
throwing
that
out
there
yeah,
because
on
the
on
the
concept
here,
we
do
show
visa,
because
because
this
was
a
kind
of
advanced
concept
here
as
well
for
that
with
that
in
mind,
based
on
what
we
talked
about
before
I'm
gonna,
make
that
super
clear
here
in
the
assumptions
and
then
but
but
essentially
what
we
want
to
do
very
similar
to
shipping
methods
is
to
be
able
to
choose
a
program.
It
hasn't
very
simple
and
then
be
able
to
see
that
through
in
the
checkout,
all
the
way
down
to
the
border.
Yeah.
E
So
while
I
finish
this
assumption,
outs,
I
mean
I
could
walk
through
this
weekend.
We're
all
talking
about
future
considerations
for
other
things,
we're
talking
about
this
being
programmatic,
we're
talking
about
selecting
this
within
that
pay
with
that
that
pay
with
experience
again
on
the
on
the
other
concepts
here
which
we
can
at
which
we
can
walk
through
here.
Give
me
just
a
second.
E
Right
here,
so
the
pay
pay
with
on
this.
Do
it
I?
You
would
activate
that
here
and
it'd
be
a
lot
of
the
same
interactions
that
we've
talked
about
with
with
other
things
that
we've
groomed
today,
but
that
is
the
that's
the
intent.
So
any
questions
about
this
while
I
finish
out
this
assumption
any
any
concerns
anything
we
want
to
add
on
the
API,
or
at
least
maybe
some
some
discovery
work
on
kind
of
we'll
see
what
we
get
on
the
methods
or
something
of
that
nature.
Well,
the
first
question.
C
I'm
just
making
sure
it's
not
like
a
dog,
the
the
payment
request.
Api
is
going
to
be
a
great
way
of
simplifying
and
smoothing
out
the
checkout
process
for
a
developer,
as
well
as
a
great
way
to
add
some
trust
for
the
consumer,
and
we
know
all
that.
But
right
now
we're
gonna,
try
and
implement
these
according
to
the
UI
spec,
because
in
any
event,
we
will
need
to
fall
back,
certainly
because
Vinnie
is
supposed
to
work
on
desktop
settings
and
and
for
people
who
have
not
added
their
payment
details
to
such
a
system.
C
E
G
E
E
E
G
C
Bear
in
mind
this
API
integration
is
not
actually
the
main
part
of
the
story.
We
do
want
to
consider
how
it
would
operate,
but
in
Magento
is
in
mini
shopping
carts.
There
is
a
payment
option
that
emergen
can
choose
to
configure
of
cash
on
delivery
or
or
check
to
be
mail.
You
know,
there's
the
e-commerce
stores
that
exist
for,
like
old
people
to
trade,
haunted
dolls
and
they
don't
trust
credit
cards
they.
You
know.
We
know
this
to
be
true,
it's
the
fact,
and
so
there's
no
stripe.
There's
no
venmo,
there's
no
visa
checkout!
There's!
C
I
C
E
E
C
E
With
you,
I'm
always
hesitant
on
ones,
unless
it's
like
the
splash
page
or
something
like
that,
even
then,
apparently
we'll
have
a
little
be
some
some
something
we
discovered
along
the
way
so
yeah
I'm
feeling
3ne.
Is
there
any
consideration
for
a
5
on
this
one?
In
terms
of
again,
you
know
any
adjustments,
any
documentation,
some
basics
of
testing
and
the
unanticipated
discovery
work.
Anything
like
that.
That
would
make
it
feel
more
comfortable
with
us,
or
do
we
feel
pretty
good
about
this
yeah.
C
I
feel
good
just
again,
knowing
that
it's
as
broad
and
as
an
ambitious
of
a
topic
as
Pena's
is
that
we
have
a
very
limited
scope
here,
yeah
and
I
think
maybe
it
would
help
us
to
enhance
the
description
of
the
story
with
that
kind
of
caveat
in
boldface,
like
I
think
this
is
a
broad
topic.
This
just
addresses
the
creation
of
a
UI
workflow
that
allows
things
to
be
selected
about
this
I'm.
Just
thinking
about
that,
let's
change
the
title.
E
Now,
because
we
could,
you
know
we
could
keep
going,
but,
as
you
start
to
kind
of
see
these
between
your
own
local
set
up
and
then
with
that
design,
there's
work
to
go
around
for
everyone
and
it's
gonna
be
depend
up
on.
You
know
your
comfort
ability
or
somebody
is
graphic.
You
well
UI
things
of
that
nature,
but
we
use
as
a
basis
for
these
move
for
it
and
then
also
a
wave
again
for
us
to
identify.
You
know
some
of
the
discovery,
work,
I'd
love
to
get
your
feedback,
so
I
have.
F
A
quick
question
concerning
this
payment
methods,
so
both
the
payment
methods
and
pay
with
and
get
it
by
fields.
Presumably,
we
want
those
to
have
similar
sort
of
selection.
You
X
experiences.
How
is
that?
How
does
that
work?
When
we
have
two
separate
issues
that
may
be
assigned
to
different
people?
Well,.
G
C
Make
you
guys
fight
and
no
I
mean
it
sucks
right?
Then
it's
not
a
top-down
sort
of
design
system
that
we
have,
but
that
I
think
should
lend
itself
to
doing
a
very
simple
implementation
that
is
as
far
down
to
the
basics
as
possible.
Now
Jimmy,
if
you,
if
our
list
component,
for
instance,
is
the
right
choice
for
something
that
it's
not
in
use,
then
that's
an
indication
that
we
need
in
the
developer
facing
Docs
to
have
the
list
component
more
adequately
explained
in
right
now
in
our
quantity
selector.
C
It
says
it's
select,
this
select
element.
If
you
just
go
there
and
then
you
know,
move
upwards,
it's
necessary,
then
that
that's,
you
know,
that's
probably
going
to
produce
the
least
duplication,
but
it
as
it
is.
We
expect
for
these
parallelized
stories
for
there
to
be
some
duplication
of
work
and
and
alternate
api's
for
the
same
thing.
We
think
of
that
as
a
feature
of
the
process
and
cause
for
discussion
and
then
upon
close
of
the
sprint
yep.
E
Absolutely
and
I
think
we've
got
three
major
resources
here.
Right
we've
got
the
global
Styles
work,
that's
underway.
That
is
a
nice
foundation
for
those
questions.
If
that's
not,
you
know,
if
that's
in
and
that's
you
know
just
the
beginnings,
but
if
there's
a
question
beyond
that
that
you
know
you
know,
then
we're
definitely
pretty
easy
to
find
so
that's
kind
of
the
second
method
and
the
third.
E
The
third
is,
you
know,
potentially
as
we
source
these
and
assign
these
we're
hoping
to
align
these
two
similar
folks,
like
let's
say,
if
you're
doing
this
may
be
the
same
person
does
this
as
would
be
doing
the
shipping
methods,
and
so
inherently
there
would
be
some
consensus
consistency.
We
can't
guarantee
that,
of
course
based
on
availability,
but
but
one
of
the
things
we'd
like
to
do
at
overtime
is
to
to
make
similar
assignments,
which
should
make
these
a
little
bit
easier.