| Child pages (Children Display) |
|---|
Related
Progressive Web Apps
How-to
- developers.google.com - Your First Progressive Web App
- Progressive Web Apps are experiences that combine the best of the web and the best of apps. They are useful to users from the very first visit in a browser tab, no install required. As the user progressively builds a relationship with the app over time, it becomes more and more powerful. It loads quickly, even on flaky networks, sends relevant push notifications, has an icon on the home screen, and loads as a top-level, full screen experience. (...) Progressive Web Apps have to be fast, and installable, which means that they work online, offline, and on intermittent, slow connections.
- 2015.08.11 - Medium - Progressive Web Apps: Escaping Tabs Without Losing Our Soul
- 2015.11.11 - Medium - Building Flipkart Lite: A Progressive Web App
- 2015.11.17 - GoneHybrid.com - Are Progressive Web Apps The Future Of Mobile Apps?
- 2017.07.07 - MXB - How to turn your website into a PWA
- Step 1: The Manifest.
- Step 2: Go HTTPS.
- Step 3: The Service Worker.
- Test your PWA
...
Criticisms / downsides of PWAs
- 2017.07.25 - Philly Devshop - Apple’s refusal to support Progressive Web Apps is a detriment to future of the web
- HN discussion
- Progressive Web Applications (PWAs) are one of the most exciting and innovative things happening in web development right now.
- Except for is one major problem — While Google has embraced the technology and added support for it in Chrome for Android, Apple has abstained from adding support to mobile Safari. All they’ve done is say that it is “Under Consideration.”
- [Paragraph summary: iOS still makes up a big portion of the first-world / upscale app market.]
- Service workers are what allow you to do all the awesome and exciting things that PWA’s represent. Mobile Safari’s lack of support for them effectively kills the the ability for PWA’s to work for half of all U.S. users — which in turn kills their feasibility as a whole.
- Here are a list of things you still can’t do with mobile safari due to Apple’s refusal to support them:
- Create an app loading screen
- Use push notifications
- Add offline support
- Create an initial app UI to load instantly
- Prompt installation to the home screen through browser-guided dialog
- I’ve tried pushing the apple ‘native-like’ experience in mobile safari as far as I could — but it has some serious bugs, and Apple just doesn’t care about them.
- Apple treats web apps like second class citizens because they don’t generate money like native apps in the app store.
- On Cordova: I’ve personally never been a fan. It feels like a hack to run my app in a webview/native wrapper. I tried learning and using Ionic/Angular, and it just never felt right to me. And as soon as you introduce a hybrid wrapper, you’ve still got to go through the app store.
- You do have one other option though, and it is an amazing one, from the engineers at Facebook: React Native. The navigation is fluid and native-like, and the entire app feels like a real iOS app — because it is one. I do think that in the future we will see some form of the tech behind PWA’s and React Native come together for the best of both worlds.
- Apple thinks you should learn a completely different and more complex programming language (Objective-C/Swift) and maintain a completely separate code base for iOS. This effectively hurts small dev shops, stifles innovation, makes startups much more difficult to get going.
- We can’t just hop on the PWA train and forget about native apps completely.
...