►
From YouTube: Magento PWA Community Meeting, 11 January 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
This
is
a
little
bit
of
an
ad
hoc
meeting,
given
that
the
team
is
still
planning
to
go
through
comm
on
training
next
week,
we're
still
working
through
one
of
all
of
our
new
ceremonies
will
be
going
into
2019,
but
I
think
is
important
to
get
this
meeting
on
the
board
and
kind
of
just
give
a
brief
update
on
we'll
start
off
with
kind
of
demo,
and
some
of
the
things
that
the
team
has
been
working
on.
We'll
talk
about
what
our
current
priorities
are,
give
a
quick
update
for
mr.
A
zetlen
and
then
talk
about
kind
of
next
steps
for
us
and
then,
as
we
move
forward
with
the
rest
of
this
meeting
and
then
we'll
kind
of
end
it
from
there.
So
I
don't
think
it'll
take
the
full
time,
but
I
guess
it
depends
on
how
deep
we
go
on
some
of
these
topics
so
for
demo.
I
think
I
have
the
team,
as
some
things
prepared
that
we
want
to
show
so
I
will
turn
it
over
to
anyone
that
wants
to
volunteer
to
go.
First
I
can
go
there.
B
Okay,
good,
okay
cool,
so
yesterday
this
is
work
in
progress,
but
yesterday
I
put
up
a
PR
for
to
update
the
checkout
flow
with,
so
we
could
process
credit
card
payments,
so
Braintree
is
a
preferred
partner,
so
they
have
like
a
little
widget,
that's
built
on
top
of
web
requests
and
the
payment
requests
API.
So
I
brought
up
a
little
thing
about
that.
There's
some
links
in
the
pr
if
you
want
to
check
it
out,
but
just
to
demo
it.
B
So
if
we
come
in
here,
I've
already
added
an
item
to
the
shopping
cart
if
I
go
into
checkout
I've
already
added
some
shipping
information
here
too
becoming
here
where
there
used
to
be
a
just,
a
simple
select
drop-down
that
said:
I
want
to
pay
with
check
or
money
order,
and
there
were
no
other
options
in
there.
There's
now
a
credit
card
form
that
that
shows
up.
So
this
has
some
all
provided
by
Braintree
by
the
way
some
validation
built-in.
B
B
Let
me
just
fill
all
this
stuff
out.
The
expiration
date
has
to
be
just
be
some
date
in
the
future
and
it'll
accept
that
and
then
the
CVV
can
be
any
three
digits
and
that's
fine.
Let
me
actually
show
you
if
you
don't
fill
out
all
the
forms.
It'll
give
you
a
overall
error
down
here
at
the
bottom.
Please
check
your
information
and
try
again
so
that
if
I,
do
you
fill
in
it'll
save
that
it
updates
the
kind
of
summary
display
here.
Here's
your
credit
card
you're,
paying
with
a
credit
card.
B
C
Thanks
know
for
those
of
you
maybe
who
need
some
of
the
context,
because
this
seems
pretty
Elementary
and
I
understand
that
there
is.
There
is
a
payment
request,
API
dependency
here
and
that's
very
much
intentional.
The
PWA
studio
mission
has
always
been
to
focus
quality
efforts
on
the
browsers
and
the
user
agents
and
the
devices
which
we
know
are
going
to
be
in
most
people's
hands
in
the
world
in
the
next
couple
of
years.
C
That
allows
us
to
focus
more
of
our
efforts
in
a
smaller
and
more
efficient
team,
on
getting
things
very,
very
right
and
very,
very
good
for
the
next
generation
commerce,
and
that
means,
of
course,
that
we
focus
on
things
like
payment
request,
API
at
the
expense,
at
least
initially
of
traditional
checkouts.
That's
not
always
been
the
case,
but
you're
gonna
see
this
from
the
future
work.
It's
always
gonna
be
focused
on
the
the
the
new
we
were
first
and
then
we'll
move
on
to
backfilling
other
functionality.
C
B
D
D
Addition
of
payments-
you
guys
see
my
screen
I-
think
so
yeah
I
just
added,
so
we
use
an
icon
library
called
feather
right
now.
C
D
Think
that's
gonna
be
changing
soon
for
veneer
to
material,
but
the
way
it
was
done
was
by
importing
basically
the
entirety
of
the
feather
library
it
just
because,
by
virtue
of
how
how
it
was
written,
it
just
has
like
a
single
export
that
that
that
is
about
17,
K
gzip.
So
what
I
did
is
I
went
through
and
I
found
this
this.
This
implementation
called
react
feather,
which
basically
just
react
if
I'd,
better
I,
feather
library,
I,
also
added
a
cool
build
tool
for
us
to
look
at
the
bundle
stats.
D
So
that's
what
you
saw
just
a
second
ago.
You
just
run
NPM
runstats
venĂa
from
the
from
the
root
and
it'll
run.
This
bundle
analyzer.
So,
as
you
can
see
here,
this
is
the
previous
output,
from
the
build
like
before
the
the
for
my
PR
17
kg,
zip,
the
feather
and
then
I
ran
it
again
afterwards
and
we're
down
to
with
the
react,
feather
implementation,
we're
down
to
1.2
KB
gzipped.
But
overall,
it's
not
that
big
of
an
impact
when
you're
looking
at
the
entirety
of
the
build,
but
it's
still
relatively
I.
D
B
B
A
F
Okay,
so
that
updates
I
improved
the
check
out
implementation,
dot
page
it's
you
know
it's
here
and
of
any
section.
Basically
I
took
what's
currently
the
state
of
the
check
out
implementation
and
did
a
deep
dive
into
it
and
added
a
lot
more
technical
details
on
what's
happening
behind
the
scenes
and
I've
provided
links
to
the
source
code,
so
you
can
follow
through
what's
happening,
also
link
to
the
relevant
REST
API.
D
So
I
have
been
working
on
a
post
even
seen,
yeah
we
implementing
the
upward
server
spec
in
PHP,
so
that
is
this
entire
library
me
and
Tommy
been
working
out
together
for
past
few
weeks
we
have
most
there's
Oliver's,
coordinate
over
think
right
now
we
are
still
waiting
on
the
the
proxy
resolver
and
the
matching
resolver
Bazaar,
your
red
X
matching.
C
C
D
G
Cool
it's
on
the
right
guy
I
wasn't
sure
if
it
was
stuck
all
right.
So
what
I
was
working
on
for
the
last
couple
weeks?
I
guess
is
turning
us
into
having
support
with
Dockers
so
that
we
don't
have
to
be
stuck.
Anybody
on
any
kind
of
platform
can
build
and
work
with
PWA,
so
I
set
up
a
reverse
proxy
with
nginx
so
that
we
could
actually
have
HTTP
support
locally
with
our
own
custom
URL.
G
G
One
outstanding
thing
that
is
next
on
my
list
is:
it
was
working
with
mounting
a
volume
file
for
local
so
that
it
would
hop
reload
on
any
changes.
You
had
locally
with
just
the
docker
file,
but
appears
that
the
docker
file
way
of
mount
volumes
is
slightly
different
with
docker
compose,
which
is
what's
running
both
of
the
nginx
reverse
proxy,
as
well
as
our
application
here.
So
I
have
to
do
a
little
bit
of
work
to
get
that
to
figure
out
how
that's
not
gonna
overwrite.
G
All
of
the
previous
work
done
in
the
docker
file
builds,
but
other
than
that.
The
only
way
to
the
only
thing
you'd
have
to
do
to
get
this
up
and
running
locally
would
be
to
run
a
docker
compose.
Just
you
know,
docker
and
compose
builds,
and
then
you
would
do
just
a
docker
compose,
but
once
you
are
ready,
so
we
can
see
here
also
that
all
of
the
requests
are
coming
in
through
the
nginx
proxy
itself.
So
that's
what
I
got
for
this
session.
At
least
you
have
any
questions.
Let
me
know
thanks.
Gabe.
D
A
This
was
kind
of
an
ad-hoc,
I,
think
demo
for
us,
and
it
really
was
just
based
on
the
fact
that
I
think
we
haven't
really
had
one
over
the
last
few
weeks
with
the
holidays
so
exciting,
to
see
all
the
good
work
that
that
has
happened
over
the
last
few
weeks,
thanks
Steven
for
the
cat
and
and
obviously
there's
a
number
of
new
team
members,
including
myself,
so
a
great
opportunity
to
see
some
of
the
work
that
some
of
the
new
team
members
are
starting
to
contribute
already.
So
up.
A
Next
I
wanted
to
turn
it
over
to
mr.
Zetland
to
talk
about
anything
outside
of
what
we
already
seen
in
terms
of
the
team's
work.
Obviously,
we've
been
heads
down
on
reviewing
open,
pull
requests
and
getting
some
of
that
work
merged,
and
the
team
has
been
really
doing
a
great
job
on
burning
down
that
that
backlog
of
pull
requests.
But
if
James
you
want
to
give
an
update
on
anything
on
the
top
of
your
on
the
top
of
mind.
For
you
sure.
C
C
We
have
been
waiting
for
added
an
additional
help,
sort
of
from
an
internal
core
engineering
perspective
that
we
can
put.
We
aren't
asking
quite
as
much
of
our
extraordinarily
generous
community
members
who
are
on
this
call
and
we've
we've
received
it.
We
have
some
fantastic
new
team
members
and
we've
achieved
a
velocity
that
will
allow
us
to
terminal
please
so,
there's
no
MIDI
in
this.
It's
late,
there's
no
on
board
sound
with
these
are
know.
C
If
you
guys
know
that
you
need
a
MIDI
connection,
so
it's
it's
controller
to
drive
some
sort
of
synthesize
soft
synth.
In
this
case,
we
have
gotten
into
the
velocity
to
achieve
a
release
of
PW
a
Studio
2.0
point
o
called
that
because
of
the
big
architecture
change,
but
it
will
be
the
first
official
release
that
is
not
a
pre-release
or
candidate
and.
B
C
Maybe
maybe
that
doesn't
help
that
much
but
yeah
I
wanted
to
say
that
we
we
are
confidently
targeting
an
initial
release:
state
PWA,
Studio
2.0
for
the
end
of
January.
What
this
mostly
means
is
that
we
have
a
real
and
integrated
solution
for
deploying
a
storefront
with
the
Magento
supported
PWA
in
our
enterprise
cloud
and
that's
huge,
because
that
puts
real
load
on
our
systems
and
then
we'll
increase
the
turnaround
and
the
feedback
cycle
for
improving
our
performance
and
so
as
a
as
a
result.
C
Stephan
introduced,
pull
request
which
maintained,
exact
functionality,
parity
and
reduced
bundle
size
by
20%,
and
so
I.
Don't
have
it
to
demo.
Our
next
job
is
to
take
these
200k
on
average
images
and
shrink
them
and
resize
them
using
responsive
image
techniques,
which
should
land
very
shortly,
and
we
have
something
that
seems
to
produce
about
30
to
40%
less
payload
overall.
C
So
what
that
amounts
to
is
the
final
stretch,
we're
very
excited
about
it
and
we
we're
doing
all
hands
on
deck,
which
is
partly
why
you
haven't
heard
as
much
from
us
on
social
media
as
it's
typical
and
when
we
come
out
with
that
release.
I,
you
know,
might
always
in
cloud
so
I'm
the
most
excited
about
what
that
frees
us
up
to
do
for
the
next
big
changes.
C
The
next
big
advancements
that
release
being
out
will
put
us
in
a
maintenance
cycle
for
the
2.0
point,
o
code
and
start
to
stabilize
the
AP
is
that
you
were
using,
which
I
know
everyone's
been
waiting
for
so
I'm
super
excited
about
it
and
we'll
keep
you
updated.
What
is
work
when
detail
emerges
about
what
feature
sets
will
be
in
that
initial
two
point:
0.0
release
and
that's
the
main
thing:
that's
what
I
got
that
and
I
will
issue
a
double
secret.
A
Alright,
so
as
James
kind
of
talked
about
there,
you
know,
there's
been
a
little
bit.
We've
been
a
little
bit
light,
I
think
on
reviewing
the
the
exact
backlog
and
in
actual
issues
and
grooming,
but
that
has
been
purposeful
to
some
degree
and
again,
as
I
mentioned
on
the
beginning
of
the
call
like
the
team
is
going
through
Kanban
training
next
week,
and
so
we're
expecting
some
of
our
internal
processes
of
change
and
obviously
that
has
kind
of
a
cascading
effect.
A
So,
thank
you
for
I,
don't
if
anyone
has
any
other
open
items
or
open
questions,
I'll
give
a
quick
second
quick
pause
for
that
all
right.
So
thanks
for
joining
us
today
then,
and
thanks
everyone
for
all
of
the
the
hard
work
and
the
demos
and
then
I'll
pass
out
I'll
send
out
an
update
after
this
and,
of
course,
we'll
post
the
video
but
I
guess
we
will
end
17
minutes
early
18
minutes
early,
fantastic.