►
From YouTube: PWA Studio Community Meeting 17 January, 2020
Description
New development for the Cart Experience, a sneak peak at upcoming Checkout Experience, and PWA Studio 5.0.0 release resources
A
B
At
a
high
level
and
talk
about
what
resources
are
available
for,
if
you're
interested
in
checking
out
more
about
the
release
and
then
we'll
save
some
time
at
the
end
to
come
right
over
questions
open
new
topics,
anybody
that's
on
the
line
so
to
get
us
started
today
we
have
Tommy
who's
going
to
demo.
Some
of
the
cart
work
that
we
has
been
underway
for
the
last
couple
weeks.
Great
thank.
D
You
am
I
sharing
my
screen.
You
are
not
I
will
yes
boom
all
right,
so
cart,
page
I
think
we
demoed
like
some
kind
of
scaffolding
of
this
last
week
and
in
the
span
of
a
week,
we've
made
a
lot
of
progress,
kind
of
fleshing
out
all
these
components,
and
then
we
also
held
up
our
end
of
the
bargain
when
we
demoed
some
kind
of
Reno
stre
factors
both
we
said
some
nicer
solutions,
we're
coming,
and
this
is
kind
of
the
first
phase
of
leveraging
Apollo
and
kind
of
using
its
cash.
D
So
we're
gonna
go
over
kind
of
one
method
of
kind
of
automatically
updating
components
based
on
mutations
and
things
like
that
graph
QL,
which
is
all
very
neat.
So
very
first.
This
is
kind
of
a
dead
page
right
now
you
can't
get
to
it
for
anywhere
else,
so
it's
gonna
remain
that
way
until
until
all
these
features
are
done,
but
here's
just
a
new
cart
page.
It's
a
full
page
experience,
it's
responsive
and
all
that
fun
stuff.
So
to
get
started.
Let's
go
ahead
as
products
see,
the
mini
card
is
still
like
the
default.
A
D
D
All
right,
and
just
to
kind
of
mention
very
briefly,
you
might
have
seen
that
the
loading
indicator,
but
we
had
already
been
on
this
page.
Ideally,
you
should
only
ever
get
them
at
work.
When
you
expect
data
to
change
and
from
there
you
should
not
have
to
hit
the
network
in
or
self
like
other
mutations,
and
things
should
automatically
update
your
cache.
We
have
some
aggressive,
fetch
policies
in
here
right
now
that
we
expect
this.
D
So
you'll
see
here,
I
actually
just
noticed
right
before
this
demo.
Our
mocks
had
these
images
size
to
be
square
hundred
pixels
and
none
of
our
demo
data
images
are
actually
that
aspect.
I
just
noticed
that
I'm
like
squashing
these,
so
we
are
we're
gonna
need
to
do
like
some,
some
change
there,
I
don't
know
if
this
is
just
getting
rid
of
heighten
this
container
or
what
but
I'm
gonna
do
some
some
demos
with
UX
after
this.
So
you
can.
Please
ignore
the
squashed
images
right
now,
so
they're
perfect
squash
she's,
just
a
little.
D
A
really
cool
work
here,
the
product
listing-
is
kind
of
the
feature
I
supposed
to
cover,
but
you
can
also
see
there's
a
new
kind
of
subtotal
section
here,
again
everything,
responsive
and
fun,
and
then
some
some
other
features
here
related
to
like
shipping
methods
as
the
accordion
component.
That
I
think
was
also
and
then
from
here.
The
only
actions
that
I
went
ahead
and
hooked
up
that
existed
before
we're
removed
from
we're
gonna
have
like
a
new
cart
product
page
experience,
so
that's
kind
of
dead
right
now,
favorites
like
before
is
just
client-side.
D
E
F
D
Nicely
kind
of
like
some
ideal
state
where,
if
we
do
want
to
persist
things
in
the
maybe
there's
graph
QL
coverage,
that's
not
there
yet
or
like
something
we're
waiting
on.
We.
We
have
a
lot
of
power
to
start
using
Apollo
to
store
that
and
then
with
our
Apollo
cash
persist
that
will
actually
persist
and
local
storage.
So,
even
if,
like
you
close
your
browser
and
come
back,
the
Apollo
cash
will
be
read
free
prize
than
it
is
from
metal
storage.
D
Alright.
So
this
is
the
cool
part
where
mutations
now
automatically
update
data,
I
think
to
the
user
insistent
that
cool.
For
me,
this
is
really
awesome.
Where
now,
when
you
do
mutation,
I
did
not
like
refetch
her,
this
component
didn't
say
like
or
maybe
or
more
used
to
redux.
Where,
like
we
would
do
a
mutation,
we
would
manually
do
another
refetch
and
then
buy
a
cache.
That
would
all
happen
now.
D
D
The
car
data
alright
comentary,
renders
that's
the
yeah.
The
other
big
thing
is
that
we
were
constantly
like
persisting.
Loading
suits
again
over
and
over
again,
whereas
that
could
have
been
happening
in
the
background
and
we
really
just
need
to
re-render.
What
is
that
that
new
refetch
comes
back
or
if
the
refetch
comes
back
and
the
data
didn't
change?
You
don't
show
anything
to
the
user.
D
D
So
when
you
nothing
different
here,
we're
still
using
the
Apollo
hooks
to
set
up
all
of
our
data
manipulations
from
the
component
itself.
We
get
what
those
queries
are:
there's
still
a
separation
of
Peregrine's
not
having
knowledge
into
the
data.
It's
fetching,
though,
it's
starting
to
have
overlaps,
but
then
all
you
have
to
do
in
your
mutation
is
say:
I
need
to
reach
these
queries
once
you
complete,
and
then
that
automatically
updates
the
the
Apollo
cache
and
that
will
automatically
trigger
re-renders
it
kind
of
just.
D
It
just
feels
a
lot
cleaner
and
we
experimented
with
their
there.
Obviously,
honestly,
there
are
several
ways
to
actually
do
this,
and
this
is
kind
of
just
one
of
the
ways
we're
experimenting
with
right
now,
there's
another
method
of
using
like
named
fragments
and
sharing
those
between
all
of
your
components.
So,
in
a
mutation,
this
mutation
returns
a
cart
object.
D
Kind
of
fragment
matching
is
really
neat,
so
that
allows
you
to
like,
if
you
use
the
same
name
fragment
the
ippolit.
Cache
can
like
magically
line
up
as
that
response
object
with
the
cache
and
updated
automatically
re
trigger
those
rear,
Enders
there's
another
method.
The
API
I
think
can
also
return.
You
like
a
reef
fish
function
in
its
response,
maybe
not
a
mutation,
but
a
query
will
return.
You
like
a
reef,
fetch
callable,
and
then
you
could
kind
of
like
prop
drill
that
down
or
store
that
in
context
or
something.
D
And
then
when
a
mutation
happens,
you
just
call
the
reef.
Fetches
essentially
would
do
about
the
same
thing
here,
except
for
your
kind
of
you
can
orchestrate
it.
If
there's
like
a
specific
order,
you
want
to
trigger
those
fascism,
but
this
is
kind
of
like
the
first
step
in
leveraging
Apollo
to
do
all
of
our
cash
updates
and
re-renders
Steven
and
I
have
been
kind
of
going
back
and
forth
on
this
for
a
long
time
and
it's
nice
to
kind
of
see
it
in
action
now
and
it
does
feel
a
lot
lot.
D
Cleaner
I'll
be
in
touch
Redux
at
all
in
this
new
yeah.
This
is
yeah
zero,
Redux
I,
don't
know
if
we're
like
dead
set
on
like
removing
Redux
like
it
definitely
has
its
purpose
in
that,
but
we're
finding
in
the
scope
of
like
data
fetching
we're
trying
to
remove
its
role
and
the
scope
of
data
data
should
live
in
Apollo.
We
are
replicating
a
lot
of
what
Apollo
was
doing,
so
this
is
kind
of
just
we're
now,
using
our
tools
correctly,
it
should
should
make
things
a
lot
easier
in
the
future.
D
D
C
So
if
you're
making
something
new
use
Redux,
if
that's
what
makes
sense
to
you,
but
we
don't
have
any
demands
that
you
use
Redux
if
you're
contributing
as
a
community
member,
if
you
can
find
a
way
that
you're
very
proud
of
it's
very
simple
to
maintain
state
instead,
ideally
with
react,
Oaks
go
for
it.
We
are
open
to
that.
Those
redux
is
or
what
people
understand
current.
That's
all.
F
A
D
E
D
D
We
have
this
issue
here
where
Peregrine
does
actually
have
to
be
aware
of
what
this
query
is,
because
it
needs
a
variable,
so
we're
kind
of
crossing
paths
here
already
we're
probably
going
to
need
to
configure
three
fetches.
They
require
variables,
but
kind
of
this
is
kind
of
that.
First
step,
we'll
nail
it
down
a
little
more
and
we'll
have
like
a
consistent
way.
E
D
Yes,
so
there's
kind
of
a
future
phase
of
this
as
well
or
we're
not
doing
any
optimistic,
UI
stuff,
but
yeah
I
mean
something
like
a
remove
is
a
perfect
example
for
use
of
optimistic
UI,
because
the
remove
will
either
succeed
and
you
can
just
leave
that
idea
from
the
cache
right
now
or
it'll
air
out.
But
an
error
probably
indicates
that
that
items
not
in
your
carton
more
anyway.
D
D
That'll
probably
be
like
a
future
future
future
as
well,
where
we
start
making
the
UI
a
little
more
snappy
I.
Think
there's
a
big
UX
portion
to
that
as
well,
because
sometimes,
when
you
eyes
are
too
snappy,
it
just
feels
wrong,
like
you
might
have
to
put
a
delay
in
there.
That's
it
like
animation,
yeah,
yeah,.
C
F
D
B
B
But
obviously
this
current
work
that
we're
demoing
with
Demmel
ass
compilation
will
contain
a
demo
like
so
it's
complete
as
a
part
of
our
effort
to
really
revisit
venya
and
the
kind
of
vendhya
completeness,
and
that
has
all
been
based
on
feedback
that
we've
gotten
from
developers
from
the
community
partners
that
are
implementing
nibbly
projects
right
about
wanting
a
more
kind
of
comprehensive
cart
experience,
which
is
why
we're
tackling
that
first
coming
into
2020.
So
that's
what
you're,
seeing
right
and
I
think
a
couple.
B
Other
cool
parts
of
this
is
our
that,
obviously,
from
a
UX
and
implementation
perspective,
we're
thinking
about
the
complete
responsive
design.
So
where
we've
got
feedback,
we've
gotten
questions
about
desktop
right
and
why?
Well
previously,
we
have
heavily
indexed
towards
mobile
you're
now,
seeing
that
in
the
new
future
work
that
we're
delivering
right.
It's
a
design
that
comes
from
the
desktop
and
the
mobile.
B
It's
really
cool
about
the
work
that
we're
demoing
here
and
so
saying
the
stage
for
our
next
topic
right,
not
only
we
working
on
the
card
experience
but
as
we
continue
to
move
forward,
we're
revisiting
areas
of
begin
and
ask
ourselves
where
are
there
gaps
as
compared
to
I?
Think
the
experience
that
you're
typically
used
to
in
Magento
that
being
looma
right?
And
so
next
up
we're
going
to
move
into
the
checkout
experience
and
building
out
a
more
comprehensive
checkout
experience.
E
B
G
So,
just
to
set
a
little
bit
of
context
for
design
we've
done
a
lot
of
discovery
on
checkout.
Looked
at
a
lot
of
websites
online
been
through
many
design
iterations,
and
what
I'm
about
to
show
you
we're
also
testing
with
sort
of
end
users
in
a
couple
of
weeks,
just
to
make
sure
that
it
it
all
works
and
and
as
always
as
as
you
as
I,
go
through
this.
If
you
have
feedback
or
you
think
things
that
you'd
like
to
share,
please
do
note
them
down
and
I'm
on
the
community
slack
channel.
G
G
Listings
and
you
have
a
proceed
to
checkout
button
once
you
hit
that
there
is
also
an
easy
way
to
go
back
to
cart.
If
you
want
to
in
the
header
we've
put
the
you
know
what
could
be
considered:
Express
Checkout,
which
would
be
things
like
PayPal,
and
also
an
assigned
in
experience
at
the
top
I'm
gonna
go
through
guest
checkout,
first,
so
with
guest
checkout,
we've
split
the
form
for
address
into
contact
information
and
shipping
address.
G
So
you
would
have
email,
these
are
all
just
form
fields
you
would
fill
it
in
and
one
thing
we're
testing
is
to
collect
zip
or
postal
code
first,
so
that
you
know
in
the
event
that
were
able
to
auto
populate
city,
state
and
country
based
on
zip.
It
would
save
the
user
quite
a
bit
of
effort
once
they
hit
that
once
they
fill
out
that
from
the
hit
continue
and
we
kind
of
start
building
a
checkout
summary
for
them.
G
If
they
continue
and
the
same
thing
happened
is
very
shipping
method,
summary
kind
of
bills
and
they'll
be
able
to
edit
that
then
they
come
to
payment
method
with
credit
card
they
can
enter,
enter
the
information
and
then,
by
default
billing
same
as
shipping
is
checked.
If
they
uncheck
it,
then
it
surfaces
the
address
form
they
can
fill
in
whatever
address
they
want.
G
Then
you
have
a
summary
and
then
finally,
you
see
your
pricing.
You
see
any
coupons
or
gift
cards
that
you
may
have
applied
in
cart.
We
also
offer
that
offer
the
option
to
do
that
in
check
out,
but
it
would
be
the
exact
same
experience
as
cart,
so
I'm
not
going
through
that,
then
they
could
place
order
and
they
get
an
order.
Confirmation
page,
one
of
the
things
that
we
are
trying
to
get
more
information
on
is,
if
they
were
official
work,
was
to
say
it
create
account.
G
What
information
are
they
comfortable
having
passed
over
and
saved
into
their
default
accounts?
Your
contact
information
shipping
address?
Maybe
yes,
maybe
not
payment
information.
We
don't
know
that
for
sure.
So
we're
gonna
do
some
testing
around
this.
So
that's
authenticated
check
out
having
unauthenticated
check
out.
G
Ok,
I
will
proceed
to
off
then
so,
at
the
top
of
the
page,
we've
got
sign-in
to
your
menu
account.
If
you
hit
that
you
go
to
the
sign-in
page
that
we
have
now
you
sign
in
and
basically
what
you
will
see
is
a
summary
view
that
was
progressively
built
during
yes
check
out.
You
see
the
default
contact,
information
default,
shipping
address,
default,
shipping
method
and
any
saved
payment
information
that
you
have
if
you
wanted
to
edit
your
shipping
address.
G
This
would
be,
of
course,
part
of
the
address
book
from
my
account,
but
you
would
see
a
list
of
many
pre
saved
addresses
you
have
you
could
either
just
select
one
of
those
and
apply
it
or
in
the
event
that
you
were
gonna,
add
a
new
address.
You
could
choose
that
option
and
you
would
have
the
ability
to
add
a
new
address,
save
it
or
make
it
your
default,
and
then
you
would
apply
that
and
you
would
see
that
update
and
then,
assuming
that
you
unpay
minh
works
exactly
the
same
way.
G
If
you've
got
any
payment
information,
you
would
that's
already
saved,
select
that
or
you
would
apply
a
new
one
and
then
you
have
Auto
somebody
and
you
just
hit
a
SCADA.
The
one
difference
in
the
order.
Confirmation
page,
is
that
if
you
do
have
an
account,
we
have
the
ability
to
link
your
order
to
your
purchase.
G
C
B
G
Yes,
it
isn't
an
Adobe
XD.
We
have
been
encouraged,
naturally
to
use
more
Adobe
products.
I
mean
we
do
still
have
teens
here
within
Adobe
that
you
sketch
and
envision,
but
since
XE
allows
for
both
design
and
prototyping
and
allows
us
to
collect
feedback.
Have
we
have
a
development
mode
where
we
can
share
some
of
the
specs,
and
so
on?
We've
been
using
that
as
a
tool,
both
Scott
and
myself.
B
H
E
I
I
I
D
Yes,
so
we
might
be
undocumented,
but
we
always
aim
to
be
minimally
compatible
with
the
last
release.
So
we
are
releasing
this
in
parallel
with
two
three
four,
so
this
is
minimally
compatible
with
two
three
three,
so
we
don't
take
advantage
of
any
two.
Three
four
only
features
in
this,
and
that
should
be
the
case
going
forward.
Oh.
B
B
Day,
if
you
have
any
any
questions,
obviously
there's
a
lot.
It's
a
big,
it's
a
pretty
large
released
just
in
terms
of
the
amount
of
peers
of
emerge.
Of
course,
it'll
take
time
for
people
to
kind
of
parse.
Do
that,
but
Timothy
has
pointed
out
the
resources
where
you
go
check
that
out.
If
you
have
questions,
feel
free
to
hit
the
team
in
the
community
slack
or
github
and
sure
we'll
be
happy
to
address.
J
F
B
B
All
right,
well,
I,
think
that's
it
for
our
agenda
topics,
so
we'll
just
open
up
generally.
If
there
are
any
questions,
comments
for
anybody
that
has
a
PWA
do
project
you're
working
on.
If
you
got
questions
Oh
mister,
is
that
little
be
here
or
Jimmy
who's
on
the
line,
the
hot
topics,
it's
kind
of
open
forum.
C
Awkward
silence
minutes
not
that
expensive
accession
I
mean
like
an
overload
people
with
things,
but
it
is
going.
Okay,
I
can
present
the
first
few
diagrams
for
how
interception
would
work,
but
idea
Meteora
like
see
now
no
PR
yet
because
we,
after
the
spike
for
extensibility
as
the
concept
with
vertical
functionality
and
revin
completed,
but
we
got
business
value
out
of
that
now.
C
We
can
go
forward
from
that
to
make
a
couple
of
underlying
like
plumbing
stories
for
technical,
plugins
or
iterating
through
them
for
connecting
to
the
build
and
then
we're
going
to
build
out
some
initial
again
neatly:
business,
valuable
use
cases
and
what
I'd
rather
do
is
just
show
people
the
tickets
when
they
arrive.
But
I
can
say
right
now
that
the
first
things
we're
starting
with
are
making
it
possible
to
do
a
color
theme
on
video
with
minimal
changes,
making
it
possible
to
attach
an
analytic.
C
B
Just
to
set
some
context
there
again
for
everybody
who's
on
the
call
or
watch
this
video.
Last
week
we
demoed
the
new
kind
of
concept
for
extensibility
framework
with
the
PWA
studio.
He
is
working
through
that
you're
interested
in
that
content.
You
can
go
to
last
week's
video
to
see
it
or
you
can
ask
questions
within
the
community
side
before
misters
that
learners
self
specific
concerns
are
again
questions
about
extensibility,
all
right,
so,
barring
any
other
last-minute
topics,
it.
E
E
Despite
discuss
a
lot
of
witnessed,
and
currently
we
wanted
to
do
something
in
the
future
thing
optimistic,
you
know
and
stuff
you
mentioned
a
couple
of
cash,
it
would
tell
Apollo
cash.
This
is
the
optimistic
change
that
I'm
making,
but
if
something
was
wrong,
rollback
or
something
like
that-
and
these
be
tied
up
together
early
and
the
community
start
using
it.
A
D
All
just
baked
in
there's
just
like
a
special
tag,
use
like
a
client-
and
that
indicates
like
this-
is
a
client-side
variable.
I'm,
never
gonna
hit
the
network
to
get
this
and
then
it
kind
of
knows
it
still
behaves
exactly
like
you're
doing
a
network
bastard.
That's
like
you,
there's
almost
pills
your
own
schema.
F
There's
a
good
example:
they
have
about
this
yesterday
because
we
were
talking
about
if,
if
someone
is
on
the
cart
page
and
they
refresh,
but
they
are
like
the
shipping
section
or
like
one
of
those
suggested
inspections
that's
expanded
and
they
refresh
right
now
and
always
refresh
the
initial
statement.
First
thing
will
be
expanded,
but
ideally
the
page
would
remember
where
they
were
so
we
can
create
like
a
local
variable,
instead
of
sending
that
variable
to
redux
and
maintaining
a
battery
tax.
Just
stores
it
in
local
storage
Apollo
also
looks
cooler
towards
a
little
storage.
F
F
C
Asked
you
one
of
the
things
that
Apollo's
talked
about
a
lot
of
their
documentation
is
the
potential
to
unify,
like
every
piece
of
data
that
you
retrieve
like
this
content
data
state
into
a
graphical
API.
Part
of
the
reason
that
we're
like
Redux
might
go
away
is
because
the
future
may
be
when
that
API
is
a
little
more
vague.
C
Then
you
would
use
graph
QL
to
query
and
mutates
local
state
as
well,
and
the
way
that's
different
types
like
one
for
local
state
and
then
one
for
actual
remote
state
would
unify
it
is
the
graph
QL
client
would
detect
the
type
that
you're
dealing
with
and
then
direct
one
query
out
to
the
graphical
API
over
the
network.
Maybe
another
query
internally
to
a
state
manager
that
have
the
graph
QL
anywhere
library
to
see
some
of
the
ideas
they
have.
But
it's
still
pretty
preliminary
a.
D
Feature
that
may
hit
this
person
like
recently
viewed
like
that's,
not
a
concept
in
Magento,
that's
something
that
we
can
persist
in
Apollo
like
you
go
and
view
a
product.
We
throw
it
into
this
mutation
into
the
Apollo
cache
and
then
recently
beautiful,
query.
Query
that
exactly
like
it
did
exist
in
magenta
and
it
can.
We
can
just
write
things
for
Apollo
every
time.
B
Podcast
using
the
publication
is
a
hot
topic
for
you
as
well
feel
free,
10
again
discussing
the
team
in
the
community
slideshow.
So
we
are,
we
are
about
a
complete
year.
I,
don't
think
that
I
see
any
other
questions
coming
and
so
I
would
just
say
thanks
for
joining
this
week,
we'll
make
sure
we
get
the
recording
up
and
running
onwards
and
upwards
much
like
and
subscribe
Punk.
If
you
like
it.