According to this article by CNBC, Nearly three-quarters of the world will use just their smartphones to access the internet by 2025.
Considering these stats, if you are thinking of building a new website or redesign one, you should consider developing your website as PWA with no doubts.
Starting from a PWA could be the perfect start for your projects, you don’t need too much effort and you can build one application that works for all platforms!
What is a PWA?
A Progressive Web App (PWA) is a hybrid of a regular web page and a mobile application.
A PWA combines features offered by most modern browsers with the benefits of the mobile experience. They are built using standard web technologies, including HTML, CSS, and JavaScript.
The functionalities include working offline, push notifications, and device hardware access and enabling creating user experiences similar to native applications.
You can add them to the home of your phone exactly like a mobile app.
Why should you build a PWA?
A few weeks ago, I was looking for more information about PWA, and I found a very cool website pwastats.com, it shows the stats of all the most famous companies which are using PWA.
It was impressive to find out how the companies improved the performance of their website, mostly more than 100%.
A Progressive Web App can cut load times, allow users to navigate offline, increase the time spent on the website, increase revenue, can be much smaller than a mobile app, and much more.
Who is already using PWA?
It’s interesting to see the companies which already have a PWA, some of the world’s biggest company such as Twitter, Instagram, Uber, Pinterest, Forbes, Alibaba and much more.
To know how to turn your website in a PWA in 5 minutes read the article on medium https://medium.com/notonlycss/turn-your-website-into-a-pwa-6aaecb95f8b9
Latest comments (17)
We encourage the entire article to be published on DEV.to (if you have proper rights), with a linkback if appropriate. Otherwise, we recommend original material, such as an original commentary on the article. From the Terms of Use:
Posts that are simply intended to encourage readers to view an external resource are discouraged.
Thank you.
I have PWA installed with good score on Lighthouse. But when I check it here -> pwabuilder.com/
I got a warning on this part ->
X Service Worker has a pushManager registration
Can you give me the code to fix this issue?
Their website itself is not optimized for the mobile. 😒
Is pwabuilder completely free?
Yes, it's free. Just enter your domain and follow step by step to install it on your website.
What do you mean for pwabuilder?
Lighthouse gives you all checked?
You can check my score here ->
webpagetest.org/result/191003_5Q_1...
That's cool :) I think it is correct then, I don't know what other tools need!
This was like a click bait. It used up one of my premium stories for medium this month. I'm sure that was not the intention, but a warning/heads up would be nice.
Just use incognito 🙊
Exactly. Medium didn't think well about their pay wall.
Incognito solves my problem easily. But now I can't provide feedback on claps or comments, which only hurts their platform on many levels...
One of the dumbest monetization strategies I've seen recently.
medium.com/notonlycss/turn-your-we... you can read here also ;) Sorry but I can't change the rules of medium :)
Welcome to modern marketing and content distribution ;-)
PS. Not that i visit medium often, but just in case you do, this is an interesting open source project: github.com/manojVivek/medium-unlim...
--
After reading the article i must say it has very limited practical value.
Caching google fonts css in SW that has references to fonts? Writing manifest by hand? I guess its good enough if you are aiming at green checkmark in lighthouse.
Looks like a typical article written because thats what is trending in the tech world and will increase chance of "building audience" or "building the following".
I don't think like that, don't you think that is useful to cache all the resources?
If you want to cache all the resources, open the css that you are caching in your article and see if you cached the fonts in there ;)
PS. Its much better to self-host fonts, you are reducing number of unique domains and one resolve, because you can define font-faces in your css, not ask google for it.
thanks for the feedback :)