Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
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
Misc
- What are the advantages / disadvantages of a responsive website vs. a mobile website vs. a native app?
- Links:
- Web-only: A 'responsive' website vs. a separate mobile website (eg 'm.facebook.com').
- StackExchange - Developing cross platform mobile application
- StackOverflow - making a mobile application from an existing website
- Responsive web vs. native apps:
- Thinkapps.com - Responsive web vs native apps
- responsive design has two main advantages: time and money.
- While responsive web is able to self-adapt to any device automatically, adaptive web has pre-set sizes in which it is able to be shown.
- Drawbacks of responsive web:
- Responsive web needs an Internet connection to work.
- Responsive web usually suffers from poor performance on mobile devices because certain components — such as images and animations — are too slow and heavy.
- Moreover, users will have to wait for the browser to download the entire page and its elements in order to see it. This can lead to a huge consumption of data, battery, and also time.
- if you build an app that is going to be the same for each OS and the web, it will never feel native to users. They likely won’t use your product for long because it just won’t feel natural.
- Lack of Push Notifications, Other Functionality
- Overall, native apps are a better (but more expensive) option than responsive web.
- [NW: This seems like a clear overstatement.]
- if your site is just about company information and you would like to invest a small budget, a responsive website might work fine. But, if you are looking for an engaging experience, and your site is transactional, needing more interactions than read and go, I would highly recommend [you] invest in a native application.
- ModoLabs - My website is responsive, so why do I need a mobile app?
- I didn't find this extremely persuasive.
- users prefer the experience of a native mobile app
- they present navigation, content, and functionality in a way specifically optimized for the measurably different ways in which people actually use their mobile devices
- Native apps can engage users with push notifications and integration with platform and device capabilities unavailable on display-only websites
- Users who encounter mobile web experiences that force them to tap, search, copy, and navigate too many times will often give up on their original task. The deep-linking capabilities of a native app keep users focused, allowing them to complete their goal quickly and efficiently.
- app performance is a significant improvement over a responsive web site, saving end-users time and frustration.
- Misc opinions
- "I actually am hugely in favour of "web-apps" .. mobile optimzied web... philosophically. In certain cases one or the other is better of course." - John-Paul