Native Apps, like Flash, are a bridging technology. Progressive Web Apps are a new suite of technologies that combine the user experience of native, with the immediacy and reach of the web. Learn why we have them, and how to make them.
3. Why did apps come about?
• The Web wasn’t powerful enough
• Device integration
4. There’s an API for that
• Geolocation
• Touch
• Accelerometer
• Web Audio
• <canvas>, WebGL
• WebRTC
5. It's an App World.
The Web Just Lives in It
“Today, the U.S. consumer spends an average of 2
hours and 38 minutes per day on smartphones and
tablets. 80% of that time (2 hours and 7 minutes) is
spent inside apps and 20% (31 minutes) is spent on
the mobile web.”
blog.flurry.com April, 2013
10. Progressive Web Apps
• “install” to the home screen
• have their own icon (defined by the web developer)
• can launch full-screen, portrait or landscape
• but “live” on the Web
11.
12. Manifest file
stores metadata for your web
app:
icons, description, colors, and
related info that lets browsers
create high-quality experiences for
the launcher icon, task switcher,
and splash screen.
13. To tell the browser about our
Web Manifest,
we add this to the <head>
<link rel="manifest"
href="/manifest.json">
39. Opera differences
• HTTP-hosted sites will only display with browser UI,
regardless of what the manifest states
• When the user follows a link that takes the user out of the
domain of the installed app, a new tab is spawned, with
browser chrome. (Chrome shows a small address at the
top of a standalone-app. We prefer to make it more
obvious to the user that they have gone outside your
app.)
• Opera doesn’t (yet) support background_color; this will
be added in a forthcoming release.
42. Service Worker
• Service Worker allows developers to cache assets
when connected, and intercept failed calls to network
when offline, so user experience can be maintained.
• Faster loading of assets, even when online.
• https://developers.google.com/web/fundamentals/
primers/service-worker/
• https://www.smashingmagazine.com/2016/02/
making-a-service-worker/
48. Push notifications
• Web Apps with Service Workers can also use Push
Notifications to drive engagement, even when the
browser/ app isn’t open.
• https://developers.google.com/web/fundamentals/
getting-started/push-notifications/?hl=en
49. Beyond the Rack
• 72% increase in time spent for users visiting via a
push notification
• 26% increase in average spend per visit by
members arriving via a push notification
• +50% repeat visits within 3 months
50. Where does this work?
• Opera for Android
• Chrome for Android
• Firefox for Android (soon)
• Safari/ iOS (non-standard)
51. Progressive Web Apps
• live on the server so no update distribution lag
• require no app store or gatekeeper
• can work offline
• are a normal website on browsers such as Opera
Mini, Safari, Windows phones
• searchable, indexable, linkable
52. Flipkart Lite
• 40% returning visitors week over week
• +63% conversions from Home screen visits
• 3x time spent on FlipKart Lite
53. The UX of apps +
the reach of the Web
=The Future