Progressive Web Apps
- 1. “We live in an era of rapid change”
- 2. 2005
- 3. 2007
- 4. Why do developers need a native app?
- 5. Performance Offline access Periodic background processing Notifications Sensors OS-specific feature Why do developers need a native app?
- 6. 08.17.10
- 7. • 13% installed only one app per month • In 2016 half of the smartphone users in the United States didn’t install any new apps • The average retention rate for mobile applications is only 25% after 90 days
- 8. Building mobile apps became harder and harder each time because of: Mobile device fragmentation Multiple operating systems The relevance of information
- 9. 04.20.16
- 10. “We live in an era of rapid change. The Web as we know it, has gradually evolved into something really impressive”
- 18. Checklist • Site is served over HTTPS • Pages are responsive on tablets & mobile devices • The start URL (at least) loads while offline • Metadata provided for Add to Home screen • First load fast even on 3G
- 19. Checklist • Site works cross-browser • Page transitions don't feel like they block on the network • Each page has a URL • Site's content is indexed by Google • Push notification https://developers.google.com/web/progressive-web-apps/checklist
- 21. Service Worker AppCache API • Script that your browser runs in the background • Opening the door to features that don’t need a web page or user interaction • Include features like push notifications and background sync
- 22. Service Worker
- 23. Manifest W3C specification defining a JSON-based manifest to provide developers a centralized place to put metadata associated with a web application 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
- 24. App Shell
- 25. When it make sense to develop a PWA • Most of your users use PWA supported browsers (Chrome, Firefox, and Opera) • Your app is content driven, so doesn’t require mobile device functionality • You already have an IOS app and need to create one for android
- 27. Limitations • Native code beats interpreted code when it comes to complex app • PWAs can’t access all device specific functions
- 28. @yatendrasinh yatendra.joddha@gmail.com +919825861871 Yatendrasinh Joddha Software Developer at InfosenseGlobal Inc.