►
Description
This discussion is taken from the monthly SharePoint Developer call on 13th of August. We wanted to have a discussion around the future of the SharePoint Framework. SharePoint Framework was initially released back in February 2017 and is by far the most widely used extensibility model in Office 365 for extending and customizing the user interface capabilities in SharePoint or in Microsoft Teams.
Discussion participants - Pat Miller (Microsoft) @PatMill_MSFT, Luca Bandinelli (Microsoft) and Vesa Juvonen (Microsoft) @vesajuvonen.
Full details on the community call from https://developer.microsoft.com/en-us/sharepoint/blogs/sharepoint-dev-community-pnp-august-2019-monthly-community-call-recording/
More details on the SharePoint Framework from http://aka.ms/spfx.
More details on the SharePoint dev community calls from http://aka.ms/sppnp.
A
A
B
A
B
B
I've
been
in
Microsoft
for
almost
20
years,
which
is
a
lot
of
time
started
in
matters
of
consulting
service
back
in
2000
in
Italy,
then
I
first
gig
was
basically
building
base
support
the
readiness
for
Tahoe.
That's
what
it
was.
So
look
at
that
then,
after
that
I
moved
at
Europe
level
with
what
was
called
the
shift
point.
Rangers
was
one
of
them
future
plan
Rangers,
together
with
versa,
one
point
in
Europe
and
chemo
and
aku,
and
then
moved
to
the
product
group.
Where
I
built
this
point.
B
Captain
then
I
built
the
office
365
customer
advisory
team
and
now
I
am
in
the
SharePoint
framework.
That
and
I
am
the
PM
of
SharePoint
framework.
What
it
means
is
that
the
official
description
is
I
work
as
part
of
the
feature
crew
in
order
to
be
able
to
design
the
right
features
and
functionalities,
providing
the
feedback
and
the
customer
angle
to
the
engineer
so
that
the
engineers
can
breathe
can
can
build
the
great
software
in
reality.
C
Pat
Miller
I'm,
the
engineering
manager
Deb
lead
for
the
SharePoint
framework.
My
background
company
I
worked
for
in
Vancouver
got
bought
by
Microsoft
in
2001.
We
became
content
management
server.
Did
that
for
a
couple
releases,
then
a
replanted
and
rewrote
it
to
run
on
top
of
SharePoint
for
the
2007
release.
I
did
the
page
model
navigation
caching
stuff.
For
that,
then
it
did
the
taxonomy
system
for
a
release
or
to
did
some
search
stuff
and
then
joined
the
developer
platform
team
and
made
thanks.
A
Think
about
the
framers
three
questions
which
came
actually
on
the
chat
window
already
and
if
there's
any
questions
which
people
are
interested
to
ask
feel
free
to
use
time
window
I'm
catching
those
as
we
as
we
tone
now.
If
we
take
about
trip
framework,
we
are
now
waiting
for
ship
on
frame
of
1.9
to
get
back
released,
which
is
one
of
the
things.
That's
probably
one
of
the
questions
which
people
would
be
asking
already
done.
I
want
to
use
library
components,
I
want
to
go
to
GA
and
production
with
them.
C
Yeah
so
one
nine
one
should
come
out
this
week
we
found
one
other
hiccup
with
the
new
edge
chromium
browser
and
the
local
workbench
that
we're
trying
to
see
if
it's
a
quick
fix,
I
realize
there's
some
people
using
that,
but
it's
not
a
released
browser
per
se.
So
we'll
see
what
the
issue
is
around
that
and
then
we'll
get
it
out.
There
should
be
quite
soon
this
week,
yep.
A
A
Now,
one
of
the
things,
if
you
think
about
you,
have
on
the
framework
it's
now
three
two
and
a
half
year
old,
which
is
actually
kind
of
cool
we
are
closing
into
the
third
year
and
what
is
both
of
your
kind
of
a
take
on
this
random
discussion
point
well,
where
people
are
always
saying
that
much
stuff
comes
up
with
a
new
developer
model
in
every
single
three
years.
Will
that
happen
this
time.
B
So
no
ininin
pad
please
check
on
that,
a
China
on
that,
but
we
are
completely
dedicated
and
committed
on
the
SharePoint
framework
and,
as
I
hope
you
guys
are
seeing.
There
is
very
much
intentions
and
actions
to
expand
the
broadness
of
SharePoint
framework.
Above
and
beyond
SharePoint.
We
release
the
themes.
Integration
later
I
mean
at
one
point.
This
year
we
worked
with
and
still
working
with
the
office
client
and
office
web
client
that
team,
in
order
to
be
sure
that
the
reason
evolution
gonna
facade
instead
include
the
SharePoint
framework.
B
We
please
at
some
preview
on
SPC
last
time
in
May.
So
absolutely
not
only
we
are
committed,
but
we
are
also
working
very,
very
hard
to
consolidate
the
SharePoint
framework
across
office
and
max
after
65,
so
that
we
can
adjust
and
evolve
the
framework
itself
to
be
able
to
fulfill
more
and
more
requirements
and
smartly.
A
And
obviously,
there's
there's
always
the
discussion
like
Paul
is
in
the
chat
window
sign
that
hub.
When
do
we
want
to
be
renamed
that
and
when
there's
a
tree
named
and
and
that's
actually
a
marketing
decision,
so
we've
we
not
gonna,
actually
talk
about
the
timings
of
potential
renaming
and
alignments
at
this
call,
but
I
think
the
number
one
thing
to
remember
is
that
we
keep
on
investing
actually
they're
increasing
the
investments.
A
C
So
effectively
what
happened
for
on
the
on-prem
release
was
the
entire
organization
took
a
snapshot
at
a
specific
time
and
said
this
is
what
is
going
to
be
part
of
the
2019
release
because
that's
been
running,
it's
been
stable
and
then
we
package
that
up
and
do
more
validation
testing.
Do
the
work
on
top
of
that
to
make
sure
that
it
doesn't
have
the
service
tendrils
and
stuff
in
it,
and
the
feature
set
at
that
time
was
one
point
four
and
at
catalogs
weren't
there
and
extensions
I,
don't
think
we're
there
either
they.
C
Okay,
I
thought
one
for
one
was
the
beta
for
extensions,
but
maybe
not
fair
enough.
Whatever
stuff
was,
there
is
what
is
ship
and
so
to
upgrade
or
to
bump
just
the
SPF
X
version.
I,
don't
know
1.9,
let's
say,
does
require
a
bunch
of
server
changes
as
well,
and
that
changes
and
it's
sort
of
a
cascading
thing-
that's
not
something
that
the
SPF
X
team
can
do.
It
has
to
be
something
that
the
entire
organization
has
to
do,
because
the
ramifications
are
that
everything
has
to
get
a
bid.
A
C
A
Two
la
nieta
you're
answering
the
question
at
between
the
lines
and
we
can
actually
pretty
much
say
that
we're
not
looking
into
upgrading
the
shape
and
framework
version
for
SharePoint
2019,
that's
what
it
means.
Basically,
what
that
the
same,
because
the
the
implications
of
changing
diversion
would
be
too
traumatic,
oh
and
that
would
require
basically
a
rewriting
off
the
ship
and
2019.
So
it's
not
an
option
for
us.
A
C
The
socket
IO
hammer,
what
actual
component
is
called
video
descriptions,
ga
so
I
believe
that
should
be
coming
soon,
that
the
reason
why
it
wasn't
GA
to
begin
with
is
that
the
API
that
is
based
on
in
the
back
end,
wasn't
GA
and
so
shipping.
Our
component
is
GA
when
it's
based
on
a
beta,
endpoint
didn't
seem
like
the
right
thing.
I
believe
that
that
the
endpoint
is
I
would
have
beta
so
basically
as
soon
as
the
beta.
C
Soon
as
the
endpoint,
it's
out
of
beta,
we'll
remove
our
beta
preview
flag
on
it
and
it'll
be
G
yeah.
As
for
the
batch,
so
we
spent
some
time
with
the
community
talking
about
the
HP
client
batch
and
making
that
go.
Ga
right
now,
there's
a
couple
problems
with
it
without
deals
with
nested
promises
and
promises
not
getting
resolved,
which
is
a
bad
pattern,
and
so
we
had
a
couple
different
solutions
for
how
to
do
that.
That
changes
the
API
to
some
extent,
but
honestly,
the
feedback
we
got
from
most
people
was.
C
A
C
So
yes,
on
the
generator,
that's
something
that
we
have
control
over
and
that's
on
our
list
of
things
to
consider
we're
not
opposed
to
that.
In
any
way.
The
first
party
webparts,
open
sourcing
them
becomes
a
bit
more
tricky.
We
can't
just
open
source
what
we
have
right
now,
because
it's
full
of
internal
telemetry
and
monitoring
and
that
sort
of
stuff
which
wouldn't
make
any
sense
or
be
compiled
about
I,
don't
know
what
what
the
story
is
for
that
yeah.
Well,.
A
C
A
C
Mean
it's,
it
is
on
the
list
of
things.
It's
not
I'll,
be
honest.
It's
not
particularly
high
on
the
list
of
things
yeah,
the
yeah,
the
future
of
that
does
it
make
sense
to
have
extensions
there.
What
extensions
do
you
actually
mean?
If
it's
simply
hey,
we
have
the
top
placeholder
and
bottom
placeholder.
That's
one
thing:
if
it's
can
you
support
list
customizations
in
the
workbench?
C
A
Cute
question,
then
we
have
you
kind
of
let's
say:
content
management
related.
What's
the
SharePoint
frameworks,
role
in
the
biggest
game,
serpent
framework
is
the
UX
development
capability
and
sharepoint
online
or
in
on-premises.
So
it
everything
what
we
see
is
being
built
on
SharePoint
framework,
using
search
developed
by
first
party,
which
is
the
engineering
on
developed
by
third
party,
which
is
the
community,
so
customers
importance
now
looking
into
noting
any
specific
questions
there.
We
are,
though,
also
running
out
of
time,
so
I
think
it's
actually
time
to
close
up
now.
A
So
we
could
actually
have
a
separate,
potentially
separate
community
call
so
separate
a
mas
around
the
people
who
own
a
specific
functionalities
in
the
SharePoint,
because
that
would
then
give
more
insights
on
where
we're
heading
and
why
we're
heading
and
and
also
understanding
the
decision
implications,
because
I
think,
even
though
it
would
be
an
external
consultant,
it's
probably
valuable
to
understand
the
reasoning
behind
of
the
decisions,
which
is
definitely
a
good
thing.
So
please
do
give
us
feedback
on
that
when
I
and
I
already
say
something
on
the
chat
as
well.
A
But
okay,
we
are
running
out
of
time.
So
thank
you
Luke
and
that's
not
a
super
long
chat.
Thank
you
for
both
of
you
on
introducing
who
you
are.
These
are
the
people
who
are
running
the
day-to-day
program
in
the
engineering
side
or
making
things
happen
or
whether
there's
a
larger
group
of
engineers
than
writing
the
actual
code,
because
VMs
are
not
allowed
to
write
any
code,
but
you
are
allowed
to
write
some
code
right.