Web &

Mobile@jcemer
I work on
GloboPlay.

globo.com
This talk is about
two important
subjects and their
intersection.
Mobile devices
are dominating
the Internet.
Companies should
focus on a mobile-
first approach 

for their websites.
https://speakerdeck.com/jcemer/
1. Mobile
Web versions
Facebook and
Google are trying
to filter and classify
the Web.
Instant Articles
are a new way for any
publisher to create
fast, interactive
articles on Facebook.
The average load
time was between 

0 and 300 ms,
compared with 

3.66 seconds for
similar web articles.
No ads can appear
above the fold.
This would help
with rapid initial
loading.
The biggest mistake
we’ve made as a
company is betting on
HTML5 over native.
@Zuckerberg, 2012
The key to Instant
Articles' functionality is
the strictly formatted
HTML5 which is
optimized for faster
loading.
https://developers.facebook.com/

docs/instant-articles/reference/
37% + reach
22% + shares
83% + Likes
57% + link clicks.https://blog.hootsuite.com/started-using-facebook-
instant-articles/
As with any publishing
platform, the value of
Instant Articles greatly
depends on your
business model 

and goals.
https://blog.bufferapp.com/facebook-instant-articles
Users won't have
to click out of
Facebook to
view an article.
AMP-HTML is simply
HTML5 with a set of
specifications
(requirements and
restrictions).
https://github.com/ampproject/amphtml
The big players are
trying to restrict 

and split the Web.
AMP and Instant
Articles create
different versions
of a same website.
2. Mobile
Apps
No-one is going to
install an app for
each service, your
mobile Web
experience has to
be good.
Deepest engagement
for the longest period
of time happens in
Apps, so Apps matter.
http://venturebeat.com/2015/09/25/wait-what-mobile-browser-
traffic-is-2x-bigger-than-app-traffic-and-growing-faster/
Native apps 

might survive.
Progressive
Web Apps
Progressive Web
Apps have the reach
of the web, and are
reliable, fast and
engaging.
https://
dev.opera.com/
1. Deliver a
Mobile-friendly
design™
<meta name="viewport" 

content="width=device-width">
@media screen and (max-width: 1000px) { 

/* Styles */ 

}
@media screen and (max-width: 560px) { 

/* Styles */ 

}
Designing in the
browser allows the
designer to keep
checking the results
in different devices.
16:1
3:42:3
2. Apply
progressive
enhance
The app should
works for every
user, regardless of
browser choice.
Responsive
Design != one
size fits all.
@Brad Frost
Don’t get hung up
thinking that media
queries are the only
tool in your toolbox.
@Brad Frost
I work for
Booking.com,
and we support IE 7,
and I use flexbox.
@Zoe Mickley
Start with the
content and then
enhance the
experience.
Modernizr tells you
what HTML, CSS and
JavaScript features
the user’s browser
has to offer.
https://modernizr.com/
@Brad Frost
3. Ensure fast
page load
performance
0.1 second
reacting
instantaneously.
@Jakob Nielsen, 1993
1 second

user will notice
the delay.
10 seconds

users will want to
perform other tasks
while waiting.
Source:

Forrester Consulting 

http://bit.ly/1ttKspI
https://developers.google.com/
speed/pagespeed/insights/
https://
webpagetest.org/
4. Use a secure
network
connection
HTTPS ensures that
the contents of
communications
between the user and
site cannot be read or
forged.
The page that's
making the
Geolocation API call
must be served from
a secure context.
https://
letsencrypt.org/
5. Create a
manifest.json
Manifest enable 

add to homescreen
and a launch
experience more
comparable to
native apps.
https://www.w3.org/TR/appmanifest/
6. Allow the app
to be loaded on
offline/flaky
connections
Service workers
allow good
caching strategies.
Source: https://auth0.com/blog/creating-offline-first-

web-apps-with-service-workers/
https://
googlechrome.github.io/
samples/service-worker/
custom-offline-page/
http://www.slideshare.net/caelumdev/
serviceworkers-sergio
PWAs can also
benefit from 

push notifications, 

like native apps.
https://
pwa.rocks/
PWAs are in equal
parts new Web APIs,
design patterns, and
marketing fluff.
The Web
still matter…
Thank you!@jcemer

Web & Mobile