Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Progressive Web App
Similaire à Progressive Web App (20)
Dernier
Dernier (20)
Progressive Web App
- 1. The web isn't Dead.
- 2. Introduction Let’s start with Native Apps 1
- 3. Native Apps ● Performance ● Offline access ● Periodic background processing ● Notifications Sensors ● OS-specific features. 3
- 4. Distribution of Apps ● Distributing Native apps is Hard and Lengthy ● Heavy in size (MBs) ● If it has weak network, there are chances that the user will not download, and hence you will lose a customer. 4
- 5. Reducing Friction 5 ● Every Step Costs You 20% of Users --Gabor Cselle Gabor, work with Google
- 6. In India 6 Slow Internet Users of Small towns and rural areas are using slow internet Approx. 63% of Indian internet users use 2G network to access the web.
- 7. Big concept Progressive Web App (PWA) 7
- 8. “A Progressive Web App uses modern web capabilities to deliver an app-like user experience. Developed by Google for Chrome Engine. 8
- 9. Why PWA? Progressive Work for every user, regardless of browser choice because they’re built with progressive enhancement as a core tenet. Responsive Fit any form factor, desktop, mobile, tablet, or whatever is next Connectivity Independent: Enhanced with service workers to work offline or on low quality networks 9 a
- 10. Why PWA? App-like Use the app-shell model to provide app-style navigations and interactions.. Fresh Always up-to-date thanks to the service worker update process. Safe Served via TLS to prevent snooping and ensure content hasn’t been tampered with. 10 b
- 11. Why PWA? Discoverable Are identifiable as “applications” thanks to W3C manifests and service worker registration scope allowing search engines to find them. Re-engageable Make re-engagement easy through features like push notifications. Installable Allow users to “keep” apps they find most useful on their home screen without the hassle of an app store. 11 c
- 12. All you need to know 12 1 Web App Manifest Add to Home Screen Banner Service Workers Push Notifications 2 3 4
- 13. Web Manifest ● The name of the web application ● Links to the web app icons or image objects ● The preferred URL to launch or open the web app ● The web app configuration data for a number of characteristics ● Declaration for default orientation of the web app ● Enables to set the display mode e.g. full screen 13
- 14. 14 This is how Manifest looks like… The Manifest for Web applications is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in the areas that they would expect to see apps (for example the device home screen), direct what the user can launch and more importantly how they can launch it
- 15. Add to Home Screen ● Chrome on Android has support adding in your site to the home screen for a while now, but recent versions also support proactively suggesting sites be added using native Web App install banners. 15
- 16. These are the steps… 16
- 17. Service Workers ● A service worker is a script that runs in the background, separate from your web page. ● Capable of handling the push notification easily ● Synchronize data in the background ● Receive centralized updates 17
- 18. Service workers Service workers are powerful for offline caching but they also offer significant performance wins in the form of instant loading for repeat visits to your site or web app. Place your screenshot here 18
- 19. Push notification ● Push notifications allow your users to opt-in to timely updates from sites they love and allow you to effectively reengage them with customized, engaging content. 19
- 20. “ ● It's important to remember that Progressive Web Apps work everywhere but are supercharged in modern browsers. 20
- 21. PWAs are ● Reliable - Load instantly and never show the downasaur, 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. 21
- 24. Hybrid and PWA ● Can anyone guess what are the differences? 24
Notes de l'éditeur
- The web isn’t dead, it just need to evolve. It just need to adapt mobile devices. Until 2015 Android and iOS have almost a million apps on their app store. Users are using it like anything.
- Native Apps are always successful digital product as it uses almost all native OS functionality. Share Panel, Keypad, Camera, GPS etc..
- Why developers and business choose Native Apps, they have fantastic advantages for the user. Performance is excellent, user can access the app offline, receive notifications from the app, also they can access almost all OS features. If we talk about distribution of Native Apps, how difficult for any business it could be. Do they really reach out to every user in there market? If we go back in time, when we used to have Floppy Disks for distribution, how much time it takes to install or how complicated was the process. They DVDs and CDs and Pen drives.
- Now, lets talk about the distribution of Native Apps, How it is hard? If someone ask you to install one of App which I have created from the App store, let’s say ”XYZ” can you expect the exact result what are you looking for, there is a possibility my app doesn’t appear on the first page. Yes, the best way is to ping the URL. URL is very powerful when it comes to Distribution and Reach.
- There are 5 steps we follow initially when we installs any app, App Store View- if reviews and comments are ok you will download. Installs: If internet speed or you have sufficient data balance if you will install. Open App: If it takes too much of time or asks you a lot of questions you will close the app. SignUp: If there is not One Touch Signup you will not sign up. So, like that you see the chart, people lose there interest on the very first step. What this shows, We have to make user reach out to our app very quickly. According to recent comScore study, The average user installs zero app per month.
- Still India have 63% users who use 2G-3G network. It’s a huge number, so now business always want to target this huge number of the users. Now the question is, can we build an App which can solve problems which I had shared you in my last slides.
- We will need a big concept. Progressive Web Apps.
- Specifically Native App like functionality. Taking all good features from Native Apps and put in a Mobile Websites.
- The Manifest for Web applications is a simple JSON file that gives you, the developer, the ability to control how your app appears to the user in the areas that they would expect to see apps (for example the device home screen), direct what the user can launch and more importantly how they can launch it
- Its an API