The web design industry moves in cycles. Progressive Web Apps (PWAs) are big news. Here are a few resources to guide you through them.
The PWA checklist
Native apps were lauded for their swift and nimble response to user input. Use single-page applications and status bars to replicate this experience on your PWA.
Users can (and should) add PWAs to their devices’ start screens. This requires the presence of a metadata file, whose contents regulate the presentation of content.
Allow deep links
PWAs differ from native apps due to their more expanded ‘social’ features. One neat aspect involves ‘deep links’, which enable users to share parts of the application with friends and colleagues.
Analyse with LightHouse
Space constraints prevent us from providing a complete list of all PWA to-do items. LightHouse automates the checklists for you. It happily runs from the shell, from Node.js or from the Chrome Developer Tools.
Ideally pwas must be served over HTTPS. This prevents annoying man-in-the- middle attacks, which happen frequently on public Wi-Fi networks.
What about AMP?
Implementing AMPs does bring benefits in mobile search rankings – if your site is SEO-dependant, investing some effort might pay off.
What is Firebase?
While providing storage, initially, is not a problem, fast website growth usually leads to scaling problems. Fortunately, deploying Google’s Firebase storage service is a quick way to work around the problem. In addition, Google also provides market-leading authentication, cloud messaging and real-time data management solutions.
Deploying Google’s authentication service is beneficial in that it unburdens end users: instead of having to remember multiple user accounts for each site, a Google or Facebook account can be used in a cross-service fashion. Google can also take care of phone number verification and similar problems for a modest fee.