►
From YouTube: [Swarm Mini Summit] Swarm on mobile
Description
Attila Gazso, Mark Vujevits
There are different ways how you can use Swarm from a mobile app. In this presentation will talk about the different options (Light Node, existing libraries, using gateways), including the trade-offs and the level of maturity of each of them.
Biography - Attila Gazso
Attila has a background working on fault-tolerant, distributed and decentralized systems for more than a decade., Recently his main interest is decentralized apps on mobile. He is a fan of open-source and functional programming.
A
A
So
historically,
mobile
devices
were
very
limited
things
compared
to
what
we
have
in
2008.
That
was
the
second
generation
of
iphone.
It's
called
3g
for
some
reason
and
it
had
16
gigabyte
of
storage
space
compared
to
that.
What
we
have
now
is
an
iphone
xs
which
has
500
gigabytes
of
space
and
in
10
years
we
don't
even
know
how
a
mobile
phone
will
look
like,
but
we
can
predict
how
much
space
it
will
have.
So
if
we
assume
that
the
growth
of
the
storage
space
won't
stop,
then
we
can
assume
that
in
2028.
A
Also,
the
network
bandwidth
that
you
could
access
from
a
mobile
phone
increased
at
least
200
times
in
the
last
years,
and
if
we
assume
that
the
growth
is
not
going
to
be
200
times
again
only
10
times,
then
it's
still
four
gigabytes
per
second.
So
that's
pretty
much
cpu
yeah!
The
gigahertz
is
not
going
to
grow
anymore,
but
the
number
of
cores
are
going
to
grow.
That
means
that
the
capacity
what
we
have
on
a
mobile
phone
will
be
pretty
big.
A
So
that
means
that
eventually,
a
mobile
phone
in
your
pocket
will
be
a
good
device
to
run
swarm
nodes,
because
it
will
have
a
lot
of
capacity
and
resources
to
do
that,
and
also
it
will
be
able
to
store
all
your
personal
data
so
that,
if
you
don't
want
to
share
it
with
anyone,
you
can
just
have
it
in
your
pocket.
And
if
you
want
to
store
it
with
someone,
then
you
can
do
it
with
with
swarm.
But
we
are
now
in
2028
just
2018.
A
So
there
are
basically
a
few
ways
how
you
can
use
form
now,
but
basically
right
now
you
have
two
choices:
you
can
you
can
access
one
through
a
gateway
or
you
can
run
a
swarm
local
node
if
you
are
using
gateway.
You
trust
someone
else's
computer
to
meet
your
data
and,
as
you
heard
before,
you
cannot
use
encryption
and
features
like
that.
A
For
example,
we
have
the
command
line,
which
has
the
swarm
command
line
tool,
which
has
every
features
that
are
available
except
for
pss
and
but
it's
not
too
comfortable
to
use.
There
is
variables
from
mainframe,
which
is
a
bit
different
in
philosophy,
but
it
doesn't
support
that
much
features.
You
have
the
http
and
rest
apis
and
websocket
apis.
A
A
A
The
only
difference
is
that
web
gs
gives
you
a
lot
of
different
web
3
functionality
like
account
management
and
all
the
all
the
crypto
codes
are
there
and
everything.
So
it's
sometimes
you
want
to
use
that
and
then
you
get
a
big
package
of
everything
and
there
is
also
airbus
who,
as
you
heard,
that's
the
mainframe
library
and
their
philosophy
is
making
things
easier
and
I
think
that's.
What
we
heard
today
is
main
framework,
is
a
evolution
of
that
or
taking
it
to
a
higher
level.
A
Even
so,
this
ease
of
use
take
it
with
a
grain
of
salt.
It's
my
personal
subjective
judgment,
but
that's
what
I
experienced,
and
so
these
are.
These
are
the
client
libraries
and
there
is
also
another
way
to
use
pharma
mobile
because
so
because,
if
you
want
to
transform
right
now
on
your
mobile
phone,
what
will
happen
is
that
you
will
your
battery
will
die
soon
because
it
will
start
syncing.
A
It
will
fill
your
disk
space,
it
will
use
your
data
package
and
you
won't
be
too
happy.
So
somehow
we
need
to
introduce
some
kind
of
limitations
and
basically,
what
we
came
up
with
is
that
we
disable
thinking
we
don't
store
files
on
a
light
node
we
disable.
We
reject
the
subscription
messages.
We
reject
the
retrieval
messages.
A
A
How
does
this
work?
We
cross,
compile
the
go
library
and
we
create
native
language
bindings
to
it.
So
then
you
can
link
with
your
application
statically
and
then,
when
you
start
your
application,
you
start
some
swarm
inside
with
the
configuration
and
after
that
you
can
either
call
the
native
api
through
the
bindings
or
you
can
use
the
web
api
as
we
have
seen
before.
A
So
basically,
this
is
how
it
looks
like
your
application
lives.
There.
You
run
code
when
you
need
something
from
swarm.
You
can
choose
to
use
the
bindings
to
communicate
with
the
swarmlight
node
or
you
can
use
the
http
cause
through
the
web
api,
and
at
this
point
we
we
would
rather
keep
the
binding
small
because
most
of
the
functionality
you
can
achieve
through
the
web
api
and
for
a
light
node.
It's
not
it's
not
that
performance
critical
to
to
not
use
http,
for
example,
so,
and
by
keeping
the
binding
small.
A
So
that's
the
project
that
we
were
working
on
with
with
the
swarm
team
and
with
the
with
some
status
guys,
and
so
we
set
two
phases
and
several
tasks
in
phase
zero
and
in
phase
zero.
Our
goal
is
to
be
able
to
start
a
light
node
on
mobile,
so
that's
not
too
ambitious,
but
still,
and
the
second
goal
is
to
be
able
to
switch
between
light
and
normal
node
on
the
fly
so
where
we
are
in
this,
we
made
some
progress
already
with
the
handshake
protocol.
A
Disable
syncing
is
already
merged
and
the
codemlia
and
the
cross-platform
library
and
build
we
have
pull
requests
for
both
right
now
only
for
ios.
So
that's
why
it's
not
completely
ready,
but
we
expect
it
to
be
ready
by
end
of
this
year
and
by
the
first
quarter
of
next
year.
We
want
to
get
to
be
able
to
switch
on
the
fly
between
the
two
things
and
I
would
like
to
show
you
a
showcase.
I
worked
on
a
small
app,
it's
all
social
app
on
swarm.
A
A
If
you
press
this
button,
it
will
be
shared
it's
private
by
default,
so
you
have
to
explicitly
share
things
and
then
it
creates
a
feed
that
you
can
share
with
others,
and
then
others
can
follow
things
that
you
posted
and
right
now
it
uses
the
gateway.
So
everything
is
public,
but
eventually,
when
there
is
a
light
node,
then
we
can
add
more
private
features
and
also
it
has
a
feature
where
you
can
follow
other
feeds
and
also
rss
feeds
which,
interestingly,
it's
a
distributed
or
decentralized
web
2
technology
which
still
exists.
A
A
And
one
more
thing
I
wanted
to
talk
about
is
that
how
you
can
how
you
can
share
feeds
publicly
on
a
swarm?
It's
very
easy,
or
at
least
we
chose
to
do
it
very
easy.
So
imagine
you
have
three
posts.
You
create
a
feed
out
of
it,
and
you
put,
I
mean,
let's
say
that
you
we
create
a
feed
with
your
last
20
posts
and
then,
when
you
post
a
new
post,
then
we
remove
the
last
one
and
add
the
new
one
and
we
update
the
feed
with
your
last
20
post.
A
So
it
will
give
you
a
different
hash
and
we
shared
this
new
hash
on
the
on
the
feed
on
swarm
feed
and
then
others
can
basically
right.
Now
you
have
to
pull
the
the
swarm
feed
to
see
if
there
is
new
data,
but
since
you
only
store
a
hash
in
it,
it's
not
too
expensive.
So
and
also
if
this
the
hash
does
not
change,
you
don't
have
to
download
the
data,
because
you
know
that
you
already
have
it.
So
it's
very
simple
but
it
works.
A
Unfortunately,
I
cannot
show
you
it's
working
right
now,
but
I
I
was
working
on
this
since
last
wednesday,
making
smart,
especially
making
smart
feeds
working,
because
that
was
something
new
for
me
and
the
good
thing
is
that
storm
feeds
are
working.
The
bad
thing
is
my
app
is
not
working
at
the
moment,
but
I
will
still
work
on
it
this
week.
C
B
A
So
right
now
there
is
no
such
feature.
We
plan
to
do
it
later
right
now.
It's
actually
your
friends
can
can
share
feeds
with
you.
Basically,
by
showing
a
qr
code,
you
scan
it
and
then
you
follow
them
and
they
can
share
other
fields
with
you,
so
it
works
the
same
with
every
share.
It's
not
only
your
share,
not
only
your
feed
that
you
can
share
with
others.
So
if
you
have
like,
if
you
find
something,
then
you
can,
you
can
also
share
it
with
your
friends,
but.