►
From YouTube: Mass Adoption and Use-Cases: Intro to Extensions
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
Remember
this
so
that
developers
can
create
easily
tasks
that
will
be
focused
and
optimized
for
mobile
environment,
so
mostly
to
initiative
and
I
will
go
over
them
and
just
try
to
explain
how
it
can
help
you
and
we
can
ensure
that
depth
just
already
optimizing,
interesting
and
mobile
environments.
So
the
first
initiative
we
have
is
optimized
for
statues
and
it's
kind
of
some
evolution
of
the
current
web
apps
ecosystem
and
the
other
one
is,
in
my
opinion,
more
interesting
and
it's.
A
Okay,
so
the
first
few
words
around
optimized
for
stages,
so
the
idea
is
well
when
you
created
that,
probably
you
will
rely
on
the
web
3
API,
which
is
some
JavaScript
object
that
allows
you
to
interact
with
a
theorem.
So
we
kind
of
model
around
this
API
and
try
to
offer
developers
statues
specific
features,
so
not
only
accessing
everywhere,
not
only
accessing
while
ads
or
creating
connections,
but
also
eventually
being
able
to
access
statutes,
contacts
or
being
able
to
to
send
a
chat
message
and
so
yeah.
A
The
idea
is
to
make
this
available
to
any
tab,
and
if
you
go,
that
is
optimized
hostages
once
you
will
run
it
inside
status,
it
will
benefit
from
those
features.
So
it's
the
a
play.
It's
a
philosophy
on
the
web,
3
API.
So
if
you
are
used
to
the
wetware
PL,
you
should
be
pretty
familiar
with
with
this,
and
so
it's
something
which
reason
that
will
be
pushed
and
we're
still
interested
in
feedback
from
developers.
A
So
what
kind
of
features
we
want
to
offer
so
right
now
it's
still
pretty
limited,
but
then
now
it's
ready
depending
on
what
the
developer
needs
are.
We
will
just
add
a
new
API,
so
we
have
some
some
forum
actually
discuss
that
status,
that
I
am
and
so
the
number
of
different
posts
discussing
this
API
and
if
you
you
feel
like
or
if
you
have
some
specific
needs.
Well,
it's
just
as
simple
as
discussing
this,
and
eventually
we
will
add
those
new
APIs.
A
Yeah,
so
it's
just
noise
sample
to
show
you
that
it's
pretty
simple
and
it's
essentially
just
the
same
thing
as
the
regular
web-
try
every
interaction,
and
so
we
also
have
a
new
documentation
website.
So
that's
that
statute,
that
I
am
and
you
can
find
all
the
available
IP
I
and
details
on
how
you
can
use
them
on
this
documentation
site,
and
so
then
what
happened
inside
statue.
So
let's
say
your
that
we'll
use
some
statute
specific
a
polite
so
because
there
is
some
some
privacy
concern
or
security
concern
related
to
those
usages.
A
We
don't
offer
the
special
directly
as
is,
but
so
you
will
as
a
developer,
rely
on
the
API,
but
then
once
stitches
will
execute
all
that.
It
will
still
be
up
to
the
the
end-user
to
accept
our
notes
and
to
provide
the
access
to
specific
features,
because
you
don't
want
anyone
to
access
your
contacts,
for
instance,
or
you
don't
want
any
that
developer
to
be
able
to
send
a
chat
message
through
a
PID.
You
want
to,
as
a
user
you're
still
going
to
have
this
control
to
allow
or
deny
this.
A
So
this
is
the
kind
of
user
experience
we
all
right
now,
so
you
can
so
this
one
is
specifically
for
web
3,
but
for
or
status
API.
It
would
be
a
little
bit
more
avoid
because
then
you
have
different
type
of
permissions.
It
won't
be.
Is
everything
on
the
thing?
No,
it
will
be
a
little
bit
more
fine-grain.
A
Statues
is
a
mobile
application,
so
it's
running
on
your
mobile
device,
so
it's
valid
optimized
for
mobile
environment,
so
which
means
the
resource
consumption
will
be
different
but
and
the
user
experience
is
different
too,
usually
on
your
mobile
application
that
are
really
much
more
simplistic
and
they
have
a
very
different
just
feeling
design
at
some
level.
So
when
you
have
a
dog
running
inside
statues,
you
can
still
see
you
can
still
see
it's
a
web
application.
A
There
is
a
difference
between
just
bruising
a
web
application
and
a
mobile
and
just
using
like
a
regular
native
mobile
application.
So
that's
kind
of
the
idea
behind
extension
to
make
sure
that
there
is
no
difference
enable
both
in
terms
of
user
experience
but
also
of
performance
and
just
global
feeling.
A
So
what
it
means
is
that
actually,
you
will
be
able,
as
developer,
to
push
code
directly
running
within
statues,
but
not
as
some
kind
of
throwing
web
website,
but
just
directly
within
every
feature
that
we
provide
as
a
as
a
product.
You
will
be
able
to
play
your
own
logic,
so
there
are
some
trade-off
here,
because
then
it
means
there
is
no
clear
distinction
between
like
the
mobile
application
status
and
that
they
both
kind
of
become
broad.
So
so
it
means
we
have
to
pay
extra
attention
to
security
and
privacy
concerns.
A
So
the
the
world
model
of
extension
is
really
focused
first
on
privacy
and
security,
and
it's
also
produced
first
on
distant
realization,
because
we
are
talking
about
distance
relate
and
they
don't
realize
it
happen.
So
we
want
them
to
be
distant
right,
but
then
the
reality
that
most
web,
that
that
they
are
not
really
dissing,
tries
because
the
Aesir
Alain
is
an
HTTP
servers
or
DNS.
A
So
we
want
to
move
away
from
this,
and
the
last
point
is
that
we
won't
want
anyone
to
create
extensions,
because
if
you,
if
you
have
to
create
a
full
web
application,
it's
actually
a
fairly
complex.
We
have
to
just
pick
up
whatever
number
of
different
framework
for
JavaScript
and
so
on,
so
which
way
to
to
be
very
opinionated
about
what
it
is
to
create,
adapt
and
then
we
simplify
drastically.
A
However,
you
can
create
that
so
some
some
potential
use
case
is
really
targeting
statues,
so
you
could
think
about
some
chat
comments
so
directly
when
you
are
chatting
with
someone,
you
can
execute
some
logic
that
that
will
potentially
target
the
person
you
are
talking
to
so
maybe
sending
some
tokens
or
exchanging
some
collectibles
or
swapping
in
something
so
really
focused
on
interaction
with
with
other
people.
But
you
can
also
think
about
eventually
streaming
video
directly
from
within
statues,
which
is
not
official.
It
will
offer
right
now.
A
Well,
it
could
be
available
as
an
extension,
all
those
things
die.
So
we
are
the
wallets
in
statues,
and
so
you
can
view
your
different
collection
birds,
so
you
could
also,
as
the
creator
of
some
collectible,
you
could
write
an
extension
that
would
customize
how
this
particular
collectible
is
displayed
inside
stages.
Oh
I,
don't
really
believe
that
which
is
a
reference
to
which
add
to
the
idea.
A
So
this
is
like
a
simple
diagram
just
to
to
to
clarify
what
is
the
difference
between
adapt
and
an
extension.
So
the
top
part
here
you
can
see
so
we
will
kind
of
a
schema
of
how
statues
is
implemented.
So
there
is
some
native
code
based
on
a
material,
because
that
just
is
a
full
light,
full
light
eater
of
node,
and
so
this
is
native
code
and
build
on
top
of
that,
using
like
the
mobile,
iOS
or
Android
API.
A
We
have
well
add
a
chat
in
the
browser,
so
all
of
those
are
really
not
cheap,
so
you
get
the
native
experience
from
those,
but
then
once
you,
you
bros,
adapt
like
crypto
kitty.
So
then
you
are
not
in
the
natural
world
anymore.
You
are
in
the
old
web
world,
so
there
is
a
clear
distinction
and
you
will
see
it
so
with
the
extension
we're
trying
to
move
away
from
this
model,
and
then
you
could
select
the
little
pink
square.
A
A
So
it's
purely
data
base,
so
there's
no
curve
that
she
will
inject
inside
your
statues.
It's
only
some
kind
of
advanced
configuration.
We
know
what
information
will
leak
to
this
extension
and
we
know
what
this
extension
is
trying
to
do.
So
it's
it's
necessary
to
to
guarantee
security
and
privacy
concept.
A
So
it's
very
simple,
no
a
noble
step,
so
we
don't
have
to
to
use
NPM
or
whatever
kind
of
building
language.
You
will
need
yeah,
it's
really
the
simplest
possible
and
then
you,
you
just
wrote
that
that
one
configuration
file-
and
you
get
your
extension
because
it's
very
much
focused
on
extending
statues
and
providing
small
features,
and
it's
not
like
for
full
web
application.
A
So
a
bit
more
details,
not
so
interesting
for
this
talk,
but
so
in
statues
we
have
to
decide
which
part
of
the
application
we
want
to
extend
that
if
we
want
to
provide
to
allow
developers
to
create
their
own
commands.
So
that's
something
that
we
have
to
to
decide
at
some
point:
the
statues
level.
So
this
is
the
concept
of
hook
and
one
extension
can
implement
several
hooks.
You
could
create
and
a
crypto
Kitty
extension,
but
we
provide
the
contract
address,
but
also
that
will
provide
eventually
a
particular
display
for
your
crypto
chichi.
A
So
those
are
different
concepts
and
there
are
different
hooks
inside
stages.
So
an
extension
is
composed
of
very
few
number
of
concept,
like
view.
So
this
is
how
you're
displacing
queries,
how
you
access
information
and
events,
how
you
perform
action
like,
for
instance,
have
if
you
want
to
create
or
send
a
transaction
and
material
information.
A
And
finally,
it's
leveraging
this
on:
try
storages,
x1
or
ipfs.
So
this
is
interesting
for
developers,
extension
developers,
but
then
as
a
status
user.
Then
you
will
access
your
extension
via
ENS
name
and
then
statues
will
dynamically
analyze
this
extension
and
provide
some
high-level
information
to
the
end
user.
So
you
can
decide
if
it
makes
sense
for
you
to
expose
this
particular
information
to
this
extension
or
if
this
extension
can
perform,
can
sign
in
transaction
or
that
kind
of
things.
This
is
a
simple
video
that
will
demo
just
what
is
an
extension.
A
A
But
you
have
a
crypto
kitty,
so
that's
something
that
was
not
part
of
statues
as
a
product,
but
after
you
load
this
extension,
so
here
it
was
a
base
than
some
specific
URL,
but
then
it
could
be
based
on
their
QR
code.
So
you
just
cannot
QR
code
and
then
you
get
extra
features
running
directly
within
your
statute.
A
And
so
this
is
how
it
looks
like
kind
of
the
the
definition
language
to
create
some
extension
see
it's
it's
Eden,
which
is
a
specific
data
format,
but
it's
very
similar
to
Jason
kind
of
advanced
jason.
So
it's
only
data
and
then
markup,
and
there
is
some
semantics
associated
to
this,
and
so
no
code
so
safe
and
you
can
analyze
this.
And
if
you
are
interested
in
just
knowing
more
about
this,
so
you
can
just
go
to
your
Doc's
websites.
Whether
there
is
a
tutorial
to
create
your
own
extension.
A
A
So
why
is
it
interesting?
Just
all
statutes.
So
if
you
push
this
model
a
lot
well,
you
can
consider
that
everything
is
an
extension
and
that
statute
is
just
a
container
of
extension.
So
it's
really
interesting,
because
weather
is
the
big
problem
in
the
mobile
world,
which
is
the
dependency
on
app
stores.
A
So
if
we
shrink
the
mobile
application
to
the
maximum,
and
then
you
have
just
this
small
container,
then
we
don't
have
to
update
so
frequently
where
the
mobile
application
and
you
can
just
have
all
the
features
of
your
statues
or
the
mobile
application.
There
will
just
be
as
and
extensions
and
this
extension
they
are
stored
on
different
relay
storages.
So
then
you
completely
escape
like
the
potential,
some
censorship
of
app
stores,
and
eventually
you
can
also
consider
that
there
is
no
one
version
or
some
mobile
application.
A
A
Like
you
just
drag
and
drop,
and
then
you
can
see
real
if
you
haven't
formation
flowing
and
you
can
play
with
it
and
then
we
just
publish
your
extension
so
again
trying
to
push
in
the
direction
of
interacting
development,
and
so
it
would
be
a
really
good
fit
for
Statutes
desktop,
which
is
that
just
running
on
your
desktop?
Because
then
will
you
you
have
you
have
more
surface
place
to
just
create
things
and
see
information
flowing.
A
So
we
already
have
some
list
of
hooks
that
we
will
make
available,
but
then
we
are
potentially
we
want
to
get
feedback
from
developers
just
to
know
what
kind
of
things
you
would
think
could
be
extended,
but
then
the
result
or
whether
the
conflict
of
privacy
and
security,
because
you
don't
want
to
expose
yourself
so
much
so
we
want
to
initiate
this
discussion
well
or
website,
discuss
that
that
is
that
I
am
and
yeah.
You
just
make
sure
that
you
can
create
the
extension
you
want
to
create.