►
From YouTube: PWA Community Meeting Oct. 18th, 2019
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
A
B
Shopping
cart,
shopping,
cart,
so
just
to
set
some
context.
So
we
have
many
a
version.
That's
out
there,
that
everybody
can
see
after
a
lot
of
research
and
both
looking
at
competitive
sort
of
contemporary
shopping
experiences,
as
well
as
talking
to
folks
in
the
community
agencies
and
merchants,
we
going
back
to
revisit
the
site
Albania,
and
this
will
be
the
first
in
this
in
a
series
of
designs
that
you'll
see
kind
of
unfolding
over
the
course
of
the
next
few
months.
B
I
guess,
which
includes
some
of
the
learnings
we've
had
from
this
research
and
kind
of
a
new
design
perspective,
and
so
it's
mainly
Scott
Hensley,
seeing
a
UX
designer
on
my
team
and
myself
that
I
won't
on
this
Scott's,
been
focusing
on
shopping,
cart
and
I've,
been
focusing
on
checkout,
we'll
be
looking
at
checkout
next
week,
but
Scott's
going
to
demo
shopping
cart.
Today,
yep,
oh.
C
C
And
functionality
for
the
thing,
and
not
so
much
about
technically
how
things
purple,
but
so
those
sorts
of
things
also
should
mention
that
the
plan
is
to
take
these
into
testing
soon.
So
really
have
somebody
go
through
these
wireframes
and
really
see
if
the
things
we
think
are
true
are
true,
so
that
we're
gonna
try
and
start
lining
up
next
week.
C
There
are
still-
maybe
some
fuzzy
areas
in
here
that
we're
working
on
those
work
in
progress,
obviously,
but
but
pretty
close
to
done,
I
think
so
yeah
and,
of
course
this
is
all
kind
of
geared
toward
a
toward
parity
with
the
functionality
that
luma
provides
today.
So
I'll
just
start
off
here
there
is
a
desktop.
There
are
desktop
wireframe
designs
as
well,
but
I
thought
we
just
show
this
some
kind
of
a
mobile
experience
just
for
the
sake
of
time.
C
So
first
you
know
today
or
with
little
bit
there's
the
move
to
wishlist
function,
pretty
straightforward.
This
introduces
kind
of
this
concept
of
panels,
which
I'm
sure
you
guys
are
are
implementing
to
some
degree
anyway,
but
they
click
this
any
wish
list
they
have
or
the
ability
to
add.
One
I
select
boom
and,
of
course,
that
item
leaves
the
cart
and
goes
and
lives
in
their
wish
list.
Remove
kind
of
behaves
the
same
way
except
it
just
takes
it
out
a
card,
all
the
other
other
things
like
edit
would
send
you
today.
C
Looma
actually
goes
to
kind
of
a
modified
product
details
page.
So
we
still
need
to
do
some
thinking
around
that.
If
that's
the
experience
we
want
to
continue
or
or
something
maybe
a
little
more
a
little
more
unique.
If
you
will
for
the
for
the
card
experience,
but
essentially
they
would
have
the
ability
to
go
to
that
product.
Make
some
changes
to
the
configuration
of
it
apply
those
those
here
in
the
card
as
well,
and
then
really
you
know
things
are
pretty
straightforward.
C
Nuance
here,
but
you
know
I,
think
our
expectation
is
that
this
will
behave
pretty
much
like
this,
regardless
of
product,
at
least
in
terms
of
these
controls,
maybe
so
anyway,
I
guess
next
is
really
just
these.
These
kind
of
features
or
function
functionality
for
the
shopper
things
like
if
they
want
to
sort
of
have
a
good
understanding
what
their
shipping
is
before
they
sort
of
proceed
in
to
check
out
what
are
the
options,
etc.
In
this
version,
I
haven't
collapsed,
but
I
think
really.
C
Our
thinking
is
more
that
this
would
be
expanded
or
available
in
sort
of
in
line,
if
you
will
so
that,
so
that
the
user
can
see
these
to
be
aware
of
those
shipping
options
right
away,
but
I'll
just
so.
Imagine
then
that
something
like
this
is
actually
presented
in
line
in
cart.
But
essentially
what
happens
is
you
know
if
we
could
detect
their
sort
of
current
location?
C
We
might
pre
fill
those
things
which
would
then
help
with
the
calculation
of
those
shipping
costs
they
would
we've
even
default
to
the
cheapest
or
or
best
whatever
best
is
the
merchant.
Maybe
is
able
to
configure
that
so
that
would
be
kind
of
pre-selected,
so
ideally
a
user
when
they
open
this
just
goes
yeah,
that's
cool
with
me.
I
have
a
sense
of
what
the
other
options
are
and
what
they
might
cost
and
apply
that
and
then
that
just
becomes
represented
here
in
the
pricing
stack.
So
today,
just
for
context
and
luma.
C
Where
the
control
to
remove
it
is
actually
kind
of
right,
along
with
the
indication
that
that
it's
been
in
the
pricing
stack
so
here,
rather
than
having
to
go
back
into
that
module
or
whatever
does
for
a
little
bit
and
coupon
same
kind
of
thing.
We
just
feel
like
that
again
sort
of
shown
that
it's
happened
to
remove
is
down
here.
C
I
guess
some
of
the
thinking,
there's
at
least
on
my
part,
is
the
assumption
that
if
this
feels
a
little
clunky,
let's
say
to
have
it
removed
there
or
for
the
remove
to
be
you
know,
maybe
not
the
most
most
effective
target
for
somebody
that
my
assumption
is
that
if
they've
added
something
that's
reducing
the
price
of
their
order,
they're-
probably
not
too
likely
to
to
remove
it,
but
I
could
be
wrong.
We'll
see
again
testing.
They
bear
that
out.
C
Finally,
gift
options:
things
like
this
gift
receipt
printing
card,
those
kind
of
things
all
kind
of
happen
in
the
panel
they
go
there.
They
do
this
and
the
indication
of
that
and
from
there
you
know
once
they've
kind
of
done
everything
they
want
to
do.
They
they
kind
of
proceed
to
checkout,
which
is
an
experience.
I
guess
we'll
we'll
talk
about
another
time.
So
this
is
unauthenticated,
cart,
so
sort
of
guest
checkout.
C
If
you
will
for
a
authenticated
user,
there's
a
couple
of
other
options
that
may
be
manifest
here
that
are
related
to
their
account
specifically
rewards
points
and
store
credit
or
to
other
sort
of
options
or
modules
that
may
be
represented
here,
and
that
would
sort
of
bring
them
forward
the
balance
of
those
things.
How
many
reward
points
they
have?
They
could
see
it,
maybe
from
here,
maybe
even
a
collapsed
state
to
encourage
them
to
use
those.
C
Tour
credit
give
them
a
dollar
amount
and
the
ability
to
kind
of
open
that
and
apply
that
to
the
order
to
so,
but
essentially
they
would
behave
much
the
same
way
as
say
gift
card
or
coupon
line,
and
really
that's
that's
kind
of
it.
I
could
show
desktop
version
of
this.
If
you
just
wanted
to
see
the
layout
pretty
traditional
I'd
say,
but
I
could
do
that
as
well.
Otherwise,
that's
really
kind
of
the
high,
the
quick
and
dirty
on.
C
Page
yeah
so
right,
yeah
yeah,
so
there
is
I
guess
that
is
a
an
important
call
out
for
desktop
that
there
is
the
mini
cart,
which
you
know
for
desktop.
We
wouldn't
necessarily
we're
saying
that
there
wouldn't
be
a
mini
card
that
would
just
be
card
so,
whereas
desktop
you,
you
can
have
that
little
sort
of
mini
card,
that's
stripped-down
version
of
just
things
like
show
you
what
you
have
in
there:
the
ability
to
remove
them
or
increase
the
quantity.
D
D
C
A
Yeah
I
think
the
bigger
call
out
here
for
the
wider
audience
on
the
call.
Is
that
not
only
you
know
I
think
previous
previously,
especially
this
obvious
point,
we
heavily
indexed
towards
mobile
design
right
going
forward
as
we
start
to
develop
these
new
vania
features.
We're
not
only
we're
not
only
accounting
for
the
mobile
first
kind
of
mindset,
but
we're
also
coming
back
and
looking
at
desktop
and
making
sure
that
we
have
rounded
out
the
experience,
Desktop
viewport
as
well
so
yeah.
That's
the
important
call
out
here,
regardless
of
or
appeared
in,
show
choir.
B
B
C
But
but
yeah
as
you
can
see,
this
is
kind
of
that
that
drawer,
if
you
will
limited
functionality,
not
a
lot
of
not
a
lot
of
what
you
get
from.
You
know
in
cart,
sort
of
indexing
on
the
idea
that
people
from
here
will
want
to
just
jump
in
to
checkout,
but
if
they
want
it
to
a
little
effort,
they
can
get
down
here
to
edit
cart
and
go
to
a
dedicated
page
for
cart,
where
there
is
a
lot
more
room.
C
For
instance,
we're
kicking
around
the
idea
for
testing
that
on
desktop,
maybe
these
sort
of
recommended
products
product
recommendations
come
in
here,
whereas
perhaps
in
on
a
mobile
experience,
we
would
want
to
not
do
that
or
do
it
in
some
other
way
that
isn't
sort
of
run
the
run
the
risk
of
taking
somebody
out
of
that
the
checkout
process.
So
again
things
concepts
to
kind
of
test
and
verify
so,
but
but
yeah
I
mean
I,
don't
kind
of
I
kind
of
act
like
I.
Don't
know
what's
going
on
here,
but
these
things
are.
C
F
But
a
while
now
me
and
Andy
have
been
working
on
the
performance
stuff
for
Vidya
and
the
tasks
I
took
up
was
making
the
service
circle
of
people
comment
and
help
the
UI
be
more
actress,
like
caching,
also
saving
up
time
on
round-trip
times
for
the
server.
So
the
first
task
was
to
change
the
serviceworker
into
a
composable
for
destructive,
because
previously
it
was
just
one
file,
it's
very
hard
to
maintain
one
file
and
like
I,
all
sorts
of
things,
new
functions
and
stuff.
It's
hard
to
maintain.
F
So
the
first
task
was
to
actually
convert
the
serviceworker
into
its
own
folder
structure
and
make
you
can
have
utilities
in
everything.
So
if
you
see
it's,
it's
like
this,
but
once
that
Pakistan
it
creates
just
one
service,
polka,
dot,
JS
file
and
just
like
previously
to
use
to
ugly
nothing
changes
from
the
working
set
point
and
that's
the
first
part,
and
the
second
is.
F
F
But
now
with
the
service
for
them,
irrespective
of
any
page
that
you
go
to
it
just
downloads,
one
HTML
file
and
if
it
already
has
that
HTML
file
cache
stuff
because
of
the
exact
same
file,
so
we
are
saving
up
one
kilobyte
or
further
requests
and
also
each
request
has
its
own
round-trip
time.
That's
what
gives
saving
upon.
If
you
look
at.
F
It
may
be
requested
for
veneer
bottoms.
It
only
requested
for
the
slash
which
is
like
the
t45
signal
is
actually
getting
all
those
files
in
the
first
place
and
the
second
way
you
can
verify
that
this
go
to
offline
application,
and
this
is
this
one
read
that
file
do
a
refresh
on
the
page
and
the
page
still
loads,
even
though,
if
it's.
G
F
So
what
happens
is
in
the
past
like
it
is
part
of
any
down
the
keeps
most
exact
same
html5,
even
though
it
already
has
it
in
the
cache,
so
we're
just
wasting
experience
and
network
bandwidth
now.
The
only
difference
is
that
the
serviceworker
has
a
route,
but
all
the
his
tml
files
and
the
default
router
aegislash.
F
Irrespective
of
any
HTML
file,
you
request
in
Thomas
xx
and
if
it
already
has
it,
it
returns
you
the
existing
file.
But
now
the
problem
arises
when
you,
when
you
return,
whatever
you
have
in
the
cache
and
if
let's
say
that
the
HTML
file
changes
in
the
back
end
you're,
nothing
like
a
stale
version
of
it.
For
that
we
implemented
the
messaging
API.
Let's
go
back
online.
H
F
F
I
Congratulate
ourselves
great,
but
let's
congratulate
ourselves
for
having
extensible
and
good-looking
UX
pattern,
because
we
went
a
long
time
not
having
that
where
robots
would
have
had
to
work
hard
to
make
something
that
would
look
different
than
everything
else.
And
now
the
toasts
look
fantastic
here
and
if
you
have
to
go
public
with
it,
I
think
we're
all
comfortable
with
that
see.
G
F
G
F
C
D
C
C
B
What
happens
during
checkout
if
you
were
to
go
offline
once
we
have
all
of
those
I
mean
to
Scott's
point
I
think
we
need
to
talk
through
the
use
cases
yeah
and
then
come
up
with
a
more
comprehensive
strategy
of
how
big
is
that
we
may
hit
that
same
type
of
situation
at
different
points
in
the
shopping
experience,
and
we
need
to
talk
through
those
to
make
sure
that
we
have
consistency
where
we
needed
it.
Yeah.
F
K
B
You
know
those
types
of
notifications
or
errors,
or
you
know,
pay
attention
shopper
type
scenarios.
If
we
allow
them
the
more
number
of
operations.
We
love
you
offline,
the
more
coverage
we
need
when
the
system
does
come
back
online,
right
and
so
I
think
we
need
to
discuss.
You
know
how
much
do
we
want
to
allow?
What
do
we
want
to
allow?
How
do
we
want
to
manage
when
something
goes,
not
as
planned,
yeah
and
so
on?
So
it
would
be
nice.
F
Yeah,
but
the
thing
is
in
the
past
that
Appling
we
used
to
load
up,
even
if
it's
even
today,
turn
because
exact
same
Peter
stood
up
for
the
exact
same
file
is
not
available,
then
you
stir
just
crash
like
it
would
give
you
the
standard,
pronator,
saying
you
offline
or
check
the
network
thanks,
but
at
least
now
we
have
a
working
ad
unit
if
it's
offline,
even
though
it
use
case
of
it.
Even
the
capabilities
of
it.
F
B
F
I
That's
it,
they
were
all
incredible,
I
mean
a
big
thing
about
this.
Is
that
the
serviceworker,
now
being
part
of
the
bill
process,
can
respond
to
different
environments,
qualities
out
bill,
so
I,
really
kind
of
I.
Think
you
undersold
how
big
of
an
improvement
this
is.
You
showed
probably
the
right
thing
to
show,
which
is
it
fulfill
some
scenarios,
but
I'm
thinking
like
and
you
know
we
can
make
the
current
state
where
you
don't
have
a
service
worker
in
development.
I
F
B
D
Like
purely
I,
get
was
just
I
do
mean
I
had
some
discussions
about
how
we
might
approach
extend,
extending
the
UI
providing
an
extension
framework
in
the
UI,
so
this
code
and
what
you
see
is
may
never
see.
Production
I'll
show
it
off
anyways
because
it's
kind
of
cool,
so
there's
one
thing
called
there's
probably
several
ideas
of
extension,
Magento
and
so
I
want
to
make
sure
like
relatively
being
relatively
new
here.
I
might
talk
about
it
different
than
what
people
think.
D
But
what
I'm
talking
about
here
is
a
is
sort
of
UI
blocks
like
in
injecting
content
in
the
UI
and
the
sort
of
like
react
extensions.
Well.
So
so,
just
as
an
example,
I
wrote
up.
I
wrote
up
to
like
a
like
some
some
some
react
components
that
we
could
use.
But
let's
just
say
that
you
were
you
wanted
to
extend
your
category
page
or
your
or
your
main
page,
with
some
some
some
like
product
recommendations,
and
you
would
like
you'd
want
it
to
exist
right
here
in
this
big,
empty
white
space.
F
D
So
the
basic
concept
here
is
that
we
have
in
many
a
in
many
a
concept
we
exposed
this
extension
component
that
takes
in
props
and
those
props
can
be
the
children
or
the
target
ID
and
all
it
does.
Is
it
just
shoves
into
this
map
those
children
based
on
the
key
by
that
target,
ID
and
there's
nothing
else
so
inside
your
pet
inside
your
root
file,
your
index
file?
D
This
is
in
many
a
concept,
you
might
have
an
extensions
folder
and
you
might
have
a
product
recommendations,
folder
that
does
some
stuff
and
renders
some
images
and
then,
in
your
main
and
your
in
your
index
file.
Underneath
that
context,
you
would
just
render
it
you'd
say:
I
want
to
extend
in
them
in
this
naming
is
all
for
bait,
but
this
is
like
the
location
of
where
the
extension
will
be
and
I
want
to
put
product
recommendations
there.
This
is
this:
we
would
like
publicize
this,
this
API,
probably
in
sailing.
D
If
this
is
a
list
of
these,
these
extension
points-
and
this
is
where
they
exist-
where's
my
file
so
much
science-
that
main
component
yeah,
what's
up
those
IDs
know
so
I'm
gonna
get
there.
So
this
is
the
main
component
in
many
of
you.
Why
so
you're
out
has
a
bunch
of
structure
in
it
and
eventually
there
is
a
main
component
in
there
somewhere
and
if
you
looked
at
the
at
the
react
here,
you
would
see
that
this
is
the
main
component
right
here
and
it's
got
header.
D
But
what
we,
what
we
would
do
in
our
in
our
UI
components,
is
we
would
sprinkle
portals
it's
a
component
and
just
says
my
ID.
Is
this
thing,
and
so
we
happen
to
put
a
one:
that's
before
children,
we
happen
to
put
one:
that's
after
children,
you
can
see
how
the
naming
was
created
here.
It's
the
main
class
extension
point
and
it's
after
the
children
here.
So
so
you
might
go
in
your
in
your
code.
You
would
say:
okay,
I
know
that
may
that
may
need
P
after
children.
D
D
This
one
just
needs
a
route
like
a
route
portal
and
that
welcome
toast
code
uses
some
stuff
that
we've
exposed
recently
like
the
toasts
and
a
user
context,
and
all
this
does
is
it
says
if
the
users
logged
in
show
them
a
welcome
toast,
so
this
extension
I
in
and
when
they
sign
in
but
I,
have
a
welcome
toast.
That's
an
extension,
so
these
are
all
just.
These
are
all
just
react
components
that
are
targetable
to
certain
areas
within
the
code
that
we
have
designated
beforehand.
B
D
Together,
so
so,
I
don't
know
if
it's
possible
in
our
Magento
to
to
have
liked
extensions
targeting
the
same
point
if
both
exist
or
if
they
overwrite
each
other
in
the
UI.
But
this
one
just
like
this
is
one.
This
is
two
separate
extensions.
I
just
brought
some
JSX
that
says
I'm,
not
even
extension,
I'm
just
and
done.
Here's.
D
D
These
the
spike
exists
in
an
issue,
so
if
you
have
any
ideas
or
your
thoughts
about
it
feel
free,
this
is
I
wrote
this
up
before
writing
the
code.
These
are
some
questions
about
things
that
I
wanted
to
answer
in
this
bike.
Obviously,
I'm
done
pros
and
cons
yet
and
then
I
have
the
actual
the
actual
PRS
to
show
off
that
code,
but
yeah.
F
I
A
Emily
you
starts
next
week.
We
have
a
contribution.
Okay
on
Monday,
we
have
the
official
event
starts
on
Tuesday,
which
you
should
definitely
go
and
catch
the
PWA
talk
by
mister
zetlen
and
early
Tuesday,
and
then
we
have
two
lab
sessions
on
Wednesday
morning,
we'll
be
running
through
hands-on
time
with
PwC.
Okay,
it's
customizing
go
on
so
forth.
So
if
you're
going
to
be
at
Emily,
you.