►
From YouTube: Magento PWA Backlog Grooming, 24 August 2018
Description
Weekly product backlog grooming for Magento PWA.
A
B
A
A
They
create
that
account
experience
that
you
typically
have
seen
in
Magento,
but
then
start
to
enable
us
on
some
things
both
on
the
store,
but
also
the
integration
part
or
things
like
retrieving
orders
and
other
aspects
that
in
time
will
be
great
great
stories
for
us
to
do
to
groom,
but
also
to
tackle
so
here's
the
current
state
of
the
backlog.
Just
a
quick
housekeeping
note,
we
have
added
a
new
label
for
things,
they're
going
to
be
groomed
on
Fridays,
and
so
anybody
wants
a
sneak
peek
as
to
what
we're
about
the
groom.
A
We
have
added
a
a
grooming
label
here,
so
just
a
quick
demonstration
for
grooming
voila.
So
that's
what
we
talking
about
talking
about
today
in
the
midst
of
our
closing.
It
was
4:23
today
and
then
the
beginning
of
sprit
twenty-four
on
on
Monday,
with
a
highly
anticipated
demo
of
upward,
amongst
amongst
many
things
and
so
I.
So
for
today
we're
going
to
talk
about
again
the
specification
and
just
as
a
reference
point
going
through
going
through
kind
of
the
old
and
new.
A
Our
goal
is
to
take
into
consideration
this
experience
right
here,
which
you
typically
would
get
to
from
a
header
type
of
experience,
but
also
at
the
end
of
completing
in
order
and
I
think
from
an
experience,
standpoint
I
think
we
may
have
some
work
and
some
opportunities
to
to
find
a
better
way
to
do
that
versus
having
to
have
created
in
accounts
who
pull
the
order
down.
The
road
there's
probably
a
reasonable
way
to
do
that,
but
with
p2a.
A
Maybe
we
can
do
some
things
differently
there,
but
ultimately
we
we
just
need
to
and
from
an
MVP
standpoint
use
an
existing
accounts.
Veronica
Costello
is
the
one
that
ships
with
the
sample
data
and
that
that
enabled
that
and
then
future
stores
in
the
act.
Of
course,
the
creation
of
such
the
edits
and
validations.
A
The
past
group
password
strength,
meter
and
all
kinds
of
things
we
would
see,
including
things
like
forgetting
your
passwords
as
well,
and
so
again
these
are
key
enablers
but
we're
gonna
start
very
small
gonna
break
these
down
the
smallest
story
as
possible
that
we
can
either
work
with
the
community
to
assign
but
also
assign
to
ourselves
and
but
then
also
identify
again
part
of
this
exercise
identify
things
that
may
need
some
attention
or
help
along
the
way.
So
this
is
this
is
kind
of
the
before
and
then
Sammi.
A
Those
are
clearly
great
ideas,
but
but
they're
more
further
down
the
road
you've
got
to
get
the
account
first.
He
first
done
and
you've
got
to
be
able
to
retrieve
something,
because
it's
done
first
so
we'll
be
doing
that
a
little
bit
in
parallel
to
pardon
the
dust
there,
but
again
for
those
who
are
following
along
with
both
the
prototypes
and
then
kind
of
what
we're
doing
in
the
previous
world
with
luma.
That's
going
to
be
talking
about
today.
Any
any
questions
before
we
get
started.
A
So
that's
a
fantastic
segue
to
do
essentially
the
the
beginnings
of
beginnings
of
everything
here,
which
is
a
basic
log
and
the
idea
here
again,
it's
not
necessarily
even
two
again:
we've
made
some
annotations
to
to
show
that
we're
not
using
Google
and
Facebook,
and
here
in
Story
number
249.
We
just
want
to
be
able
to
use
something
that
exists
again.
Stable
data
comes
with
an
existing
username
and
password.
A
So
look
for
more
of
these.
These
gems,
in
the
future
grooming,
so
but
Tammy
will
have
a
story
of
worker
saw
starting
next
does
want
to
take
a
look
at
it,
much
more
simplified
version.
That
is
a
little
bit
closer
to
the
mechanics
of
this
than
what
you
would
see
in
this.
Let's
walk
through
the
story
stuff.
A
We
want
to
log
into
the
venue
storefront
using
email
and
password
something
with
freebies
are
created
so
that
he
or
she
can
access
previous
orders
subscriptions
and
other
features
that
are
typically
associated
with
account
at
the
very
least
or
she
just
need
an
email
and
password
and
an
NB
p
stage
we're
not
even
thinking
about
edits
and
validations.
Yes,
certainly
we'd
love
to
have
those.
A
Certainly
the
the
API
will
pull
back
some
interesting
messaging
here
and
there
on
the
situations
where
that
may
not
be
correct
and
what
that
might
be,
but
the
various
the
MVP
version
of
it
doesn't
worry
about
any
of
that.
Yet
maybe
we
can
do
something
basic
like
okay
or
something
of
that
nature
will
build
this
full
of
all.
This
will
make
that
messaging
a
little
bit
more
interesting
beyond
that.
A
But
it's
just
most
important
for
us
to
get
this
thing
working
using
the
live
user
information
a
lot
of
password
so
that
we
can
enable
other
parts
of
the
theme
so
in
terms
of
assumptions
again
we're
using
an
existing
account
or
friend,
Veronica
Costello,
which
you'll
see
shirts
from
UC
and
others
asking
who
is
Veronica
Costello.
Just
a
quick
side
note!
Yes,
they
secure
messaging,
which
we
just
talked
about
forget
password,
which
is
a
future
consideration
and
separate
stories.
A
The
creation
of
account
also
a
separate
story
that
we'll
cover
later
today
and
again,
the
basics
of
edits
and
validations.
If
you've
left
a
field
open.
If
you
have
a
mistake
and
password
all
the
things
that
would
start
off
and
the
basics
of
where
we
left
off
with
Lou,
but
from
a
UX
standpoint,
we've
got
nothing
but
the
highest
expectations
from
Sonia
to
make
those
to
make
those
experiences
great,
as
well
as
some
of
the
great
forms
work
from
Jimmy
and
that
I
think
can
be
applied
to
this
situation
as
well.
A
So
those
assumptions
that
ask
themselves
again
once
the
once
those
assumptions
are
clear:
some
some
discovery
work
again
similar
to
what
we
did
with
that
with
Jonathan
and
Paul
on
kind
of
learning
how
this
might
work
with
the
API?
How
might
this
work
Mikey
pulled
us
pulled
us
information.
You
know.
All
types
of
considerations,
of
course,
are
on
security
and
clear
taxing
things
on
password.
Let's,
let's
understand
that
so
they'll
be
assessed
at
the
next
will
be,
of
course,
displaying
any
relevant
error
messaging.
We
might
get
that
for
free.
A
So,
let's
see
what
that
looks
like
and,
of
course,
implementing
it,
which
we
can
add
there-
that's
probably
pretty
obvious,
but
then
of
course,
testing
and
documentation.
Looking
for
looking
for
any
items
that
we
would
then
kick
off
and
get
some
help
with
from
James
here
on
the
again,
hopefully
not
too
much
of
the
obvious
but
a
one
date,
you
guys
come
back
on
this
one.
A
I'm,
adding
one
task
just
so
the
implementation
piece
of
that,
so,
okay,
we're
good
so
as
I
type.
This
up
so
be
thinking
about
what
an
estimate
looks
like
this
again
this
so
on
so
give
yourselves
just
a
few
minutes
here
we
will
last
you
sexually
and
and
then
we'll
pull
together
the
average
of
the
estimates
approximately.
A
D
E
A
And
do
you
feel
like
so
now
having
gone
through
this
kind
of
last
week
compared
to
this
week?
Do
you
feel
like
that?
You
feel
better
about
those
types
of
estimates.
This
was
just
the
beginnings
is
essentially
a
form
that
old,
email
and
password
from
the
live
data,
so
the
style
and
the
approach
is
probably
not
dissimilar
from
what
you
were
doing
around
shipping
and
payments
and
the
basics
of
which,
which
would
not
include
any
niceties
around
edits,
validations
and
things
like
that.
So
we're
keeping
it
super
simple.
So
if
you
feel
pretty
good
about.
A
A
week,
so,
basically
a
point
is
basically
a
day.
We
do
account.
For
you
know
we
do
account
a
little
bit
for
overhead
in
our
larger
estimate,
when
we
try
very
hard
not
to
have
13,
which
are
just
you
know,
you're
often
very
big,
spikes
along
the
way,
but
yeah
about
half
a
week
as
a
three
there
yeah.
So
that
sounds
good
to
me.
Yeah.
It
doesn't
excellent.
Anybody
want
to
add
a
second
that
three
or
or
raise
it,
raise
it
a
five
or
lower
to
a
one.
A
It
feels
good
to
me
relative
to
what
we
had
last
week.
If
for
for
what
that's
worth
and,
of
course
we
find
it
to
be
bigger
than
that.
You
know
we
are
kind
of
learning
this
together,
we're
getting
better
at
the
estimations
every
week
and
as
we
identified
some
dependencies,
we
can.
You
know
we'll
check
those
off
the
separate
stories,
so
cool
excellent
I've
read
it
could.
B
I
just
ask
a
few
qualifying
questions
or
in
this
yeah.
So
at
the
moment
is
this:
assuming
that
all
API
calls
that
are
needed
are
in
place
and
you're
not
having
to
to
update
anything
correct.
A
B
F
A
E
A
A
If
the
approach
will
take
four
things
right
and
so
authentication
I'm,
not
sure
with
what
you
know
what
the
the
ETA
is
for
on
that
one,
but
we're
we
would
be
using
rest
rest
until
that's
where
any
of
so
that's
the
clerk
will
take
here
and
the
hybrid
kind
of
hybrid
approach
on
things.
So
that's
a
good
call
out
and
it's
a
good
reminder
that
you
know
of
these
assumptions
along
the
way.
A
All
right,
perfect,
all
right,
and
so
it's
a
good
a
good
additions
there
in
terms
of
the
assumptions
and
so
again
just
kind
of
going
back
out.
So
the
team
does
do
any
of
these
assumptions.
Change
they
ask
them
at
the
free
on
this.
Does
that
it's
still
feeling?
Okay
about
that
or
you
feel
like
would
be
an
extra
extra
day
or
so
seems.
A
Perfect
anything
else
on
this
one,
any
other,
any
other
questions
or
comments
on
this
one.
From
from
a
team's
perspective,.
A
All
right,
this
one
is
sort
of
it.
Thank
you
everybody.
So,
let's
take
a
look
at
some
of
the
some
of
the
related
ones.
These
actually
should
be
a
little
bit
more
straightforward.
Let's
start
off
with
with
the
simple
one
here
first,
and
so
this
one
is
forgot
password'.
This
is
likely
not
as
important
as
creating
an
account,
but
the
purposes
of
kind
of
building
on
the
momentum
that
we
just
did
in
terms
of
the
the
basic
log
and
I
thought.
A
A
Make
sense,
and
then
for
those
who
were
you
know
following
along
with
the
existing
experience.
This
is
what
we've
got
today:
super
basic
the
curveball
and
this
one's
going
to
be
CAPTCHA
on
this
one
I.
You
know
I
can't
they
claim
that
on
terms
of
the
progressive
considerations
for
something
like
that,
since
it
does
go
outside
to
that,
so
it
may
be
some
discovery
work
there
and
in
in
terms
of
the
the
actual
scenario
based
approach
again,
we'll
throw
this
out
here
as
a
shopper.
A
You
want
to
be
able
to
reset
your
account
password
of
any
of
these,
that
you
forgot
that
and
send
it
to
my
registered
email
address.
So
for
this
to
nothing
too
fancy
in
terms
of
sending
to
mobile
or
like
that
we've
experienced,
but
something
very
kind
of
the
the
MVP
style
would
be
simply
just
a
an
email,
not
worrying
it
about
whether
or
not
that
that
account
exists
or
not.
That
alone
is
probably
a
security
question.
Our
security
concern
in
terms
of
people
trying
to
find
a
counselor
exists,
I'm
not
worried
about
that.
A
But
then
I
think
CAPTCHA
is
still
I.
Think
that's
in
play
that
helps
out
a
lot
and
so
I'd
like
to
consider
that
unless
we
feel
like
that,
that
blows
the
estimate
by
a
week
but
I
think
they'll
be
some
research
there
to
see
if
that
changes,
anything
in
terms
of
our
kind
of
page
weights
and
things
of
that
nature.
So
simple
on
that
one
says:
separate
experience,
email,
CAPTCHA
and
then
and
then
send,
and
then
the
assumptions
on
that
would
be.
A
Of
course
it
again
existing
accounts
I
think
we
can
use
a
Veronica
for
this
one
and
then
give
a
secure
messaging.
If
anything
comes
back
and
again
to
count
this
and
just
personally
think
that's
a
bit
of
a
security
opening.
But
let's
see
if
it
comes
back
for
that
one
and
and
then
we'll
proceed
proceed
as
normal
week.
We
may
make
that
static,
saying
if
an
email
exists,
we'll
send
it
to
you
and
that's
that
that
seems
to
be
pretty
standard
fare
for
that
one.
A
So
the
task
himself
and
this
one
again,
the
big
one's
gonna,
be
discovery.
I
think
it'll
be
a
little
bit
playing
around
with
this
understanding
the
mail.
The
way
that
nail
is
hooked
up
into
a
Magento
instance,
because
I
fires
that
off
some
some
research
in
the
implementation
on
captcha-
hopefully
that's
straightforward,
maybe
maybe
not-
and
of
course,
looking
out
for
mister
Calculon,
here
testing
and
documentation
as
appropriate,
don'ts
we've
got
again
in
terms
of
the
experience
itself.
We
probably
want
to
put
a
concept
in
here.
We
don't
get.
A
C
C
A
That
something
we're
discussing
at
this
point
good
question
they
would
beyond.
That
would
probably
be
a
separate
story
in
terms
of
maintaining
state
from
the
previous
one
that
we
just
did
on
actually
authenticating
itself.
I
know.
Traditionally
we
haven't
done
that
I'm,
not
saying
it's
but
I,
don't
know
what
that
would
entail.
Yeah.
C
A
For
the
steak
over
with
their
current
velocity
and
then
the
MEP
approach
on
this
one
I
like
the
idea
I
think
we
should
document
it,
but
I
think
we
we
would
still
be
okay
without
it.
But
if
we
happen
to
find
a
a
burst
of
help
that
can
help
us
tack
that
on
so
the
story
has
talked
about
I.
Think
it's
I,
think
it's
absolutely
so
I'm
gonna
I
think
we
basically
would
have
a
consideration.
A
C
More
question:
yeah
I
know
that
Magento
and
luma-
and
all
of
this
have
happy
this
pattern
of
that
required
mark
so
ever
on
a
sign
on
a
authentication
form
which
only
has
user
name,
email
and
then
path,
username
or
email
and
password,
it
seems
redundant
to
say
they
are
required,
because
how
else
would
you
sign
in?
Are
we
in
general
for
form
fields?
C
F
F
Do
you
have
the
recovery
code,
you
have
to
factor,
authentication
enter
your
coveri
code
or
a
two-factor
out,
or
will
text
you
so
I.
Don't
think
that
it's
guaranteed
that
all
possible
future
variations
on
this
form
will
have
all
fields
you
required
right.
So
if
we
went
to
a
thing
where
it's
all
fields
are
required,
if
it
doesn't
show
required,
no.
C
F
A
Could
have
this
I
would
say
it's
at
least
a
larger
consideration.
I
think
that
I
think
that
essentially,
that
standard
should
be
part
of
the
global
style
work
yeah,
that's
why
I
think
is
probably
coming
from
yeah
I
would
say
from
a
product
standpoint:
I
wouldn't
want
to
only
note
the
exception.
Now
the
exceptions
could
so
I'm.
Writing
the
fence
a
little
bit
on
this
one,
whether
it's
required
or
optional,
but
I,
don't
I,
don't
I
personally!
Think
it's
it's
a
lesser
experience.
A
C
A
C
B
C
A
Worry
so
I'll
put
the
a
global
style
note
in
the
assumptions
on
this
and
I
think
that's
a
good
boilerplate
for
a
lot
of
the
work
that
we're
doing
here
so
that
references
the
taste
standard
in
that
so
I
think
that
I
think
we're
covered
there.
But
yeah.
Let's
dig
in
a
little
bit
more
on
that
one
I
think
for
the
purpose
of
this
story:
Carolee
agnostic,
I
think
we
can
both
assume
them
to
be
required.
A
The
presentation
itself,
I
think
will
just
be
a
you
know,
will
be
tentative
until
we
come
back
around
to
that
one.
So
I'm,
okay,
with
that
the
purposes
of
least
testing
to
restate
reset
capability
and
then
fast.
Following
with
what
you
know,
what
would
be
the
better
kind
of
global
style
across
the
board
so
and.
A
On
that
note,
I
think
in
terms
of
the
the
US
I
would
I
have
to
believe.
There's
a
there's,
a
there's,
an
easier
capture.
That's
out
there,
I've
used
this
in
several
times
before
and
I
feel
like
I'm
squinting
more
than
the
average
person,
and
so
that
I'm
certainly
open
to
suggestions
in
the
implementation
of
ones
that
are
a
little
bit
more
user
friendly
but,
of
course,
open
source
along
the
way.
F
A
All
right,
I
think
I
good
discussion
on
some
of
the
boundaries
here
again,
I
think
we've
got
a
note
on
global
styles.
I
think
we
have
a
hopefully
a
push
on
the
uncaptured.
That
makes
it
a
little
bit
more
interesting.
Any
other
questions.
Any
other
questions
comments
assumptions
that
we
should
think
about
for
this
initial
experience.
A
A
F
That
their
security
comes
that
we
have
to
blink
through
carefully
I.
Don't
immediately
see,
what's
going
to
take
so
long,
but
I
can
tell
you
that
first
of
all,
displaying
a
caption
and
then
refreshing
that
captcha
image
in
a
PWA
context
will
have
to
be
an
API
yeah.
Because
you
know
be
damn
sure
that
if
you
are
refreshing,
a
caption.
F
You
have
to
be
careful
with
it.
We
need
to
make
sure
that
it's
done,
that
is
denied
and
I
better
to
be
consulted
about
it,
but
I
want
to
be
very
I
want
to
be
very
conservative
at
estimation
and
I
think
also
that
that
opens
the
floor.
If
anyone
here
thinks
you
can
do
it
as
a
5,
then
do
it
as
a
5
and
laugh
in
my
face.
F
F
B
Yeah
well,
I
also
maintain
the
the
PHP
buy
it
library,
for
we
capture,
so
I
have
a
vested
interest.
I
feel
like
I
should
just
declare
that
now
and
then
the
other
bit
that
I'd
follow
up
on
on
this
does.
Does
this
story
include
the
target
pages
from
this?
So
if
I
forgotten
my
password
and
I
get
the
email
and
I
follow
that
link.
Is
that
in
this
story?
Is
that
a
change
or
reset
password
story.
A
A
Do
I
would
like
to
bring
I
like
to
bring
in
the
email
piece
of
this
because
I
think
before
the
testing
demo,
even
if
it's
a
very
basic
it
should
this
should
fire
off
an
email
that
does
this
I'm
much
worried
about?
Initially,
the
presentation
of
that
I
think
would
probably
leverage
what's
already
done
in
m2,
we'll
come
back
around
to
that
it
early
in
a
in
a
separate
story.
Are
you
guys
does
that
sound
good
call
out
that
it's
not
there
but
I
like
to
add
it
for
this
one,
but
pull
I'm.
A
B
And
actually
I
think
my
question
as
well
was
that,
like
I
assumed
the
I
assume,
the
email
was
already
part
of
the
the
Magento
back-end
and
that
that
would
just
stay,
as
is.
It
was
about
the
the
actual
password
reset
link
that
I'm
clicking
when
I
returned
to
the
venya
theme.
If
that
is
this
story,
or
if
it
is
a
separate,
a
rate
which
is
reset
password.
A
Also
I
would,
unless
you
guys,
to
give
a
better
way
to
break
this
up.
I
would
find
it
hard
to
test
we're
not
without
something
basic
there
of
actually
creating
that
other
than
that's
just
kicking
off
the
email,
but
I
do
understand
that
that
makes
things
a
little
bit
larger,
but
is
there
a
way
for
us
to
include
a
very
basic
version
of
us
look.
F
This
is
not
a
popular
sentiment,
but
do
you
know
what
confers
business
value
a
link
that
pops
a
dialogue
that
says
this
isn't
actually
possible
online
and
you
need
to
call
us
I
know
you
all
hate
that,
because
that's
what
happens
when
we
try
to
cancel
cable,
but
it
does
at
least
communicate
that
it
is
possible
to
recover
your
account
information.
So
I
would
say
that
that's
actually
an
implementation
of
this
story
that
I
would
expect,
and
that's
just
a
liberation
like.
Let's
not
do
a
research
spike
and
I
find
out.
F
C
F
A
A
H
B
Was
gonna,
say:
I
do
agree
with
you
on
this
one
because,
as
well,
I
think
the
Forgotten
password
functionality,
something
I'm
seeing
more
and
more
often
is
not
actually
a
reset
password
form
that
just
email
me,
a
one-time,
login
link.
So
by
separating
out
these
stories,
you
enable
that
possibility
as
well.
So
this
is
very
much.
The
I
forgot
my
password
you're,
covering
off
the
validation
of
the
email,
the
talking
to
the
backend
to
trigger
that
email
and
then
the
links
in
that
subsequent
email,
a
separate.
A
H
It
I
mean
I
think
that
implementing
mail
relay
for
testing
purposes
might
be
a
toughy.
So
let's,
let's
say
this:
can
we
change
the
story's
definition
to
implement
account,
recovery
or
venĂa
and
then,
instead
of
as
a
shopper,
I
want
to
reset
my
account
password
I,
just
as
a
shopper,
I
want
to
be
able
to
recover
access
to
my
account
with
the
venĂa
store,
even
if
I've
forgotten
my
credentials
and
then
you
could
satisfy
that
with
a
link
to
a
contact
form
at
the
absolute
minimum.
A
I
do
like
this,
an
area
that
Rowan
and
talked
about
where
we
separate
the
actions
from
the
email
itself.
I
do
like
the
duration
of
that
as
a
is
a
nice
outcome
and
then
separating
what
happens
next,
you
know
I,
don't
know
the
like
a
magic
link
of
some
sort
of
it.
I
think
that
would
certainly
be
an
improvement
even.
A
H
A
A
A
The
grab
bag
of
stories,
but
with
with
kind
of
low
kind
of
a
low,
very
entry
task
of
so
discovery,
implement
a
basic
screen.
Discovery
form
elements,
lots
of
a
little
sample,
email
and
then
testing
and
documentation.
So
I
think
the
basics
are
probably
there
for
you
to
go
several
several
of
those
different
ways.
What
does
everybody
think
is
that
you
feel
like
that's
good.
Does
that
capture
this
not
capture
it,
but
capture
this
any
questions
or
I.
H
H
Duze
research
spike
or
something
just
to
directly
backlog
right
now,
I
again,
because
PW
a
studio
is
about
consuming
services
which
might
be
able
to
do
something
like
a
mail
relay.
It's
not
in
our
scope.
But
if
we
want
to
strongly
advocate
for
it,
because
Rowan
is
right
that
it's
the
best
practice,
then
that
may
be
our
artwork
to
do
and
then
we
would
go
and
yell
at
graph
QL
to
do
it
and
I
do
mean
Gail.
We
would
scream.
H
H
A
A
A
A
A
You
know
very
specific,
but
I
think
we
open
it
up
into
what
I
think
is
a
much
more
a
much
more
meaningful
during
ironic
recovery.
So
all
right,
so
we've
got
a
we've
got
11
minutes
left
I,
let's
give
this
a
shot,
so
this
is,
this
is
create
account,
so
create
account
is
again
once
everything
is
done
again.
You
know
this
is
something
to
consider.
This
is
by
default,
got
to
be
larger.
A
A
Here
super
basic,
first
name,
last
name
again:
global
Styles
considerations
from
from
staff
again
on
this
one,
there's
a
there's
quite
a
few
required
field.
All
these
annotations
on
that
one
that
could
be
visually
simplified
to
sign
up
for
a
newsletter
which
I,
don't
necessarily
gives
NVP,
but
it
might
be
a
kind
of
a
nice
to
have
if
we
can
get
that
for
free,
and
then
you
know
in
traditional
password
and
complication,
I
think
all
brandy
P
as
much
as
I
like
the
demeanor.
That
also
is
probably
not
necessarily
under
being
we
can.
A
B
C
D
C
A
Future
consideration
because
again
we're
thinking
about
enable
enablement
for
viewing
orders
imagining
a
world
we
can
view
and
order
without
authentication,
which
is
fairly
typical
right,
which
I
think
we
think
even
further
out
or
on
progressive.
This
idea,
where
the
order
itself,
but
I,
think
your
owner
appreciates
this
becomes
almost
a
a
notification
or
something
that
would
actually
be
added
to
a
home
screen.
A
C
C
A
Those
are
good
ones
so
and
then
also
things
like
terminology,
and
it
will
get
some
feedback
from
Brendan
of
how
we
call
that
begins
and
that's
I
think
there's
a
whole
content
suite
on
this
one
as
we
as
we
look
through
this,
but
again
for
the
purposes
of
having
some
things
that
are
up
and
running
to
work
from
two
to
kind
of
prove
this
out.
There's
some
there's!
Some
flexibility
here
are
from
well,
so
the
smooth
got
so
again
just
think
about
people
for
experience
and
then
how
will
eventually
come
around
us
for
the
after?
A
So
so
this
one
as
a
shopper
I
want
to
create
an
account
with
venĂa
so
that
they
can
access
previous
order
subscriptions
and
other
features
associated
with
the
account
first
name.
Last
name
subscription
again.
If
that
comes
for
free
email,
password
and
confirm
I,
think
to
our
previous
story.
There
may
be
some
considerations
around
security
that
we
might
want
to
break
this
up
in
different
ways
and
certainly
opens
it
up
and
I
think
for
things
like
password
strength
and
others.
Those
are
going
to
be
any
Vanetta,
some
validations,
making
sure
that
you've
got.
C
A
A
Here
those
are
future
considerations.
Those
are
great,
we'll
get
there.
We
got
to
be
able
to
create
this
thing
first,
because
that
is
a
test
of
the
API
is
and
how
this
works
with
via
with
the
backend.
So
so
we've
got
that
I
did
add
basic
error
messaging.
We
may
get
something
interesting
for
me:
yeah
if
we
don't
that's,
okay,
flipped
up
it
and
then
also,
of
course,
testing
in
documentation.
A
So
so,
let's
move
that's
again
the
focus
here
in
just
the
creation
experience
but
but
I
think
there's
enough
to
map
from
the
existing
at
least
think
about
how
this
might
work
and
maybe
child
options
security.
Now
the
things
that
we've
done
previously
so
was
everybody.
Take
any
any
any
questions.
Comments
am
I
missing.
Anything.
H
Yes,
it
does
it
does
so
through
the
background
session.
It
does
a
cart
merge
if
I'm
not
mistaken,
and
there
are
a
couple
of
folks
I
think
Alex,
even
Anton,
who
can
correct
me
there,
but
that's
been
my
experience
that
it
does
a
cart
merge
completely.
On
the
back
end,
there's
there's
no
specific
method.
You
need
to
invoke
to
do
that.
Vienna,
Namaskar,
I
think
there's
some
occasions
where
conflicts
might
occur
like
a
discount
code
or
something
and
I
think
it's
always
just
resolved
as
the
con.
A
E
H
I'm,
sorry,
you
outing
yourself
as
someone
who
cares
about
security.
Well,
not
understanding
it!
Oh,
oh,
oh,
okay!
Well,
that's
responsible
to
do
I
think
its
claims
to
understand
security.
That
would
be
worrisome,
though,
if
you're
implementing
a
forgot
password,
you
know
form
I,
think
you
first
of
all
have
to
make
sure
you're
not
allowing
XSS
to
access
the
sensitive
information
like
username
like,
and
that
if
there
is
a
password
form
field,
that's
you've
got
it
secured
that
you
have
autocomplete
turned
off.
H
H
B
H
Absolutely
am
I
right
now
our
Magento
REST
API
client
does
not
debounce
posts
for
the
reason
that
they're
not
safe,
right
impotent,
but
you
can
instruct
it
to
do
so
very
easily.
There's
a
single
flag
that
you
can
call.
It
says
multicast
this
request,
whether
or
not
you
think
it's
safe
to
and
a
forgot
password
request
might
be
the
perfect
thing
to
multicast
it's,
because
it's
really
there's
no
chance
that
you
want
two
of
those
in
flight.
At
the
same
time
and.
H
I
mean
yeah,
the
thing
is:
multitasking
involves
matching
that
the
two
requests
are
identical
and
you
don't
have
an
arbitrary
way
to
key
off
of
them
without
just
doing
something
that
you've
like
taking
a
checksum
of
the
headers
in
the
body
and
if
there's
something
that's
time
dependent
or
if
there's
something
that's
random,
about
it
and
etc.
But,
right
now,
I
think.
The
thing
we
can
do
is
just
use
the
flag
to
say:
D,
balanced
and
multicasts.
This
requests,
and
that's
just
multicast
true
when
you
run
the
fetch.
H
H
Not
the
rest
of
you
guys,
though,
that's
nice
to
have
definitely
but
I
mean
the
rest.
Api
client
that
I
wrote
for
use
talking
to
REST
API
it's
today.
They
ultimately
will
replace
it
with.
You
know:
gradual
transformation
of
the
same,
the
client
that
I
wrote
should
be
in
PW
a
student.
You
can
go
to
the
PW,
a
studio,
posit
or
II.
H
H
A
B
A
H
A
Make
sense
all
right,
well
good
progress
guys
this
is
our
room,
continue
to
get
really
really
strong,
so
I
appreciate
everybody's
input,
their
participation
I
know
it's
late,
especially
in
Europe.
So
thank
you.
So
much
I
really
appreciate.
I
continue
to
be
humbled
by
all
the
input
and
all
the
folks
here
by
all
means.
Let
us
know,
if
have
any
questions,
we'll
send
out
the
recordings
here
for
those
who
were
unable
to
join
us
or
in
the
meantime,
having
a
have
a
great
rest
of
your
day
and
afternoon
and
we'll
talk
soon.
Thank.