Le Progressive Web Apps (PWA) sono la prossima grande tappa nello sviluppo del web, poiché portano esperienze di tipo "mobile like" ai tuoi utenti senza richiedere loro di installare un'app dall'Apple/Play store.
PWA è il termine che riassume tutte le caratteristiche che ti consentono di offrire esperienze di tipo mobile-like.
L'argomento è molto di tendenza ed è anche un argomento che è qui per rimanere!
Non solo è fortemente promosso da Google, ma è adottato da grandi aziende come Twitter o il Washington Post.
Domande a cui risponde il talk:
- Quali sono i punti forti di una PWA?
- Vantaggi e Svantaggi
- Oggi è importante avere un'app progressiva?
- App ibride invece di app native possono essere il futuro nel campo mobile?
- Service Worker: uno strumento fantastico ma ... cosa possiamo davvero fare?
4. What are the
Progressive
Web
Applications
4
Reliable: Load instantly and never show the downsaur, even in
uncertain network conditions.
Fast: Respond quickly to user interactions with silky smooth
animations and no janky scrolling.
Engaging: Feel like a natural app on the device, with an
immersive user experience.
8. But: Do you really want to Build a Native App?PWA
vs
Native Apps Learn two new programming languages
8
80%of time spent happens in User’s Top 3 Apps on Device
14. Requirements:
Manifest file
in depth
14
A. name,
short_name,
icons
These are used to
compose the home
screen icon and title.
B. display
There are different
display modes you can
select: fullscreen,
standalone, minimal-ui
and browser.
C. start_url
It defines the page
loaded when the
customer launches your
progressive web app
from their homescreen.
Properties Overview
D. theme_color
It’s used to set the
splash screen's
background color
E. background_color
It’s used to set the splash
screen's background color
17. Requirements:
Service Worker
17
Service Worker Overview
Basic features
- Caching
- Offline
Intermediate features
- Push Notification
- Loading cached content for
new user
Advanced features
- Background sync
- Geo-fencing
41. SEO
and
Accessibility
41
BEST PRACTICE AND ACCESSIBILITY SCORE IN PWA
◦ Use of HTTP/2
◦ Do not use front-end JavaScript libraries with known security vulnerabilities (older
versions)
◦ App’s `short_name` must be less than 12 characters to ensure that it’s not truncated
on homescreens.
◦ Do not log errors that can come from network request failures and other browser
concerns.
◦ Avoid Application Cache or WebSQL DB because both are deprecated
◦ Avoid requesting the geolocation permission on page load
◦ Display images with correct aspect ratio
43. What are
developers
saying?
43
Their preferences for building PWA
◦ 40% use Angular 2.X, 37% ReactJS and only 27% VueJS
◦ Bootstrap (50%), Material UI (33%) and Semantic UI (10%) are
the most used CSS frameworks
◦ The most important PWA features: Caching/Offline (over 80%).
66% recognize “Add to HomeScreen” or App Install Prompt as
being mandatory in a PWA whereas 60% consider Push
Notifications as being key to building PWAs.
45. Case History 2018
George.com
45
George.com enhances the mobile customer
experience with new Progressive Web App
◦ 3.8x - Faster average page load time
◦ 2x - Lower bounce rate
◦ 31% - Increase in Conversion Rate
◦ 20% - More page views per visit
◦ 28% - Longer average time on site for
visits from Home screen
46. Helpful Links
46
◦ Web App Install Banners
◦ The Web App Manifest
◦ Installable Web Apps with the Web App Manifest in Chrome for Android
◦ Your First Progressive Web App
◦ Introduction to Service Worker
◦ Adding a Service Worker and Offline into your Web App
◦ Web App Manifest
◦ Progressive Web Apps with Service Workers
◦ Progressive Web App Checklists
47. 47
PWA is the next step in web development.
So try it out and be ready for the Future!
48. That’s all folks!
Ci sono domande?
Non dimenticare di segnarti la mia email:
info@dreaming-lab.com