Let’s say you’re big company like the one I work for. It almost doesn’t matter what product the company actually sells, there are orders, there are customers, there are deliveries and there are problems and phone calls to support.
It’s logistics. And wouldn’t it be nice to know the exact location of your entire fleet from an app at the depot?
We’re pleased to find that our most Progressive Web App, listingslab.com has finally achieved the magic 100% in a Google’s Lighthouse audit.
What is Lighthouse?
Lighthouse is an open-source, automated tool for improving the quality of web pages. You can run it against any web page, public or requiring authentication. It has audits for performance, accessibility, progressive web apps, and more.
You can run Lighthouse in Chrome DevTools, from the command line, or as a Node module. You give Lighthouse a URL to audit, it runs a series of audits against the page, and then it generates a report on how well the page did. From there, use the failing audits as indicators on how to improve the page. Each audit has a reference doc explaining why the audit is important, as well as how to fix it.
The technology we use is all open source with a thriving community of users and maintainers keeping it secure and up to date.
WordPress makes up 32% of all websites on the internet. The majority of these are forgotten personal blog projects, but there are many, many businesses who’s entire web presence is on the WordPress platform.
So what’s our point?
Point is that with this approach there is no need to change or decommission the existing WordPress site, the PWA merely sits on top of that as an optional enhancement.
It also replaces the need for iOS & Android apps and the stores in the way because it’s a PWA
We’ve developed a simple rule of thumb to follow on this question;
“Don’t. Use. Bloody. PropTypes. They’re just annoying.”
Why do people use PropTypes?
It doesn’t. If you want a typed language for some reason, use typescript. There’s a time & a place for PropTypes. The time is in the past and the place is in the bin.
Why NOT to use them?
They cause crashing errors all the damn time, bloat your code and generally put barriers in the way of clarity and efficiency. If PropTypes are helping you, you should look at how you’re developing.
Learn more about what PropType means from the horses mouth (reactjs.org)
At it’s core, PWA is nothing more than a set of guidelines set down by our good friends at Google.
When a chrome browser requests a page which meets the criteria of being a PWA it gets treated as such. Other browsers are adopting this standard. Even Safari.
A PWA needs a manifest. This is a strict JSON file which lets a device know how the app would like to be rendered, has information on colour and where to find icons used when adding the app to the home screen.
A PWA needs a Service Worker. These are clever things which we will go into later