Are browser-based client applications important?

FYI:

Caveat: Unfortunately the course focuses on the App Shell PWA architecture (i.e. SPA) rather than on a progressively enhanced page with the network as a progressive enhancement which Alex Russell seems to be pushing for (the course is 2 years old but seems the be regularly updated).

Edit: The course has been deprecated and replaced:

Aside: The “Developer Experience” Bait-and-Switch

JavaScript is the web’s CO2. We need some of it, but too much puts the entire ecosystem at risk. Those who emit the most are furthest from suffering the consequences — until the ecosystem collapses. The web will not succeed in the markets and form-factors where computing is headed unless we get JS emissions under control.


Beyond single-page apps: alternative architectures for your PWA (Google I/O '18)

The StackOverflow sample PWA doesn’t seem to be using a rendering framework though it uses Workbox to simplify working with the non-DOM browser APIs (it does however use the server side HTML partials to update the page in browser rather than reloading the entire page).

Note: this should be treated as product placement for Google’s (web) Firebase and Cloud Functions for Firebase.


PWA starter kit seems to have seen a lot of activity before the presentation in May 2018.

So whether it’s going to be maintained in the long run is anybody’s guess. As such it serves as a vehicle to demonstrate of how Polymer’s lit-html web components can be used to build a PWA (with can optionally use Redux for state management).

The Redux option seems a bit odd given You might not Redux (2016) but it probably has to do with “tool addiction”.

There are lightweight alternatives like redux-zero (or unistore (original) with lit-html).


Opinionated:

2 Likes