Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/mike-works/pwa-fundamentals

πŸ‘¨β€πŸ« Mike & Steve's Progressive Web Fundamentals Course
https://github.com/mike-works/pwa-fundamentals

course javascript mobile-web progressive-web-app pwa service-worker web-performance workshop

Last synced: about 1 month ago
JSON representation

πŸ‘¨β€πŸ« Mike & Steve's Progressive Web Fundamentals Course

Awesome Lists containing this project

README

        



















This is the example project used for the Mike and Steve's PWA Fundamentals course.

# Course outline and slides

- [View course outline here](https://mike.works/course/progressive-web-fundamentals-0d74af5)
- [View slides here](https://docs.mike.works/pwa-fundamentals)

# About This Workshop

Progressive Web Apps become superheroes when they can, while still providing a great baseline experience on less modern browsers. They're reliable, fast, engaging, and although they can do many of the things users expect from native apps, they don't take up a lot of space, or require a long install process.

In this workshop, we'll begin with a "classic" single page app, that's a bit bulky in size, has a slow initial load, doesn't work offline, and provides a very "basic" mobile web experience. We'll then enhance it in several ways, so that when key technologies are supported in your users' browsers, their experience ends up being substantially better!

# What will we do?

First, we’ll add any mobile-specific metadata to the app, and look at how we can use android studio and the iOS simulator to test out our improvements. In order to reduce our page weight a little bit, we'll discuss how to choose between image types like png and jpeg, and some recent advances in compression.

Next, we'll add a service worker, and apply a few caching strategies to ultimately allow our app to work offline! Additionally, we'll take advantage of IndexedDb, so that new data created on a mobile device can be stored as a structured record, available both in our application and service worker scopes.

Then, we'll make use of Web Push and Notifications to engage our users bring them back into the app, and explore encryption and signing techniques that ensure our web clients only get messages that originate from our servers.

Finally, we’ll use Background Sync to further reduce our app’s dependency on a network connection, enabling it to be a free-standing piece of software that synchronizes with the rest of the world when possible.

### By coding along in this workshop, you will…

- Learn how to audit a web application for β€œProgressive Web Fitness" with Lighthouse, and to measure important performance metrics like "time to first load" and "time to interactive"
- Take a "classic" client-side-rendered single-page app, and make it work offline, without changing a single line of the app's code.
- Get hands-on experience with IndexedDb, a worker-friendly nosql database that's built in to most browsers.
- Build an example of the App-Shell architecture, where large portions of the UI load almost instantly
- Learn what you can do to keep your JavaScript code fast, by taking a look at some aspects of JavaScript engines, and taking advantage of some tools to keep us on the speedy path.
- And much more...

# Setup

Please make sure you have the following software installed before arriving at the workshop or beginning the course.

#### General Packages

Please make sure you have the following general software installed

| Required | Library | Version Range | Notes |
| -------- | ----------------------------------------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| βœ” | [Node.js](http://nodejs.com/) | >= 7.10 | [nvm](https://github.com/creationix/nvm) is highly recommended for managing multiple node versions on a single machine |
| βœ” | [Visual Studio Code](https://code.visualstudio.com/) | >= 1.14 | We'll be using several specific features of the VS Code editor. We can't force you to use it, but you'll miss out if you don't! |
| βœ” | [Yarn](https://yarnpkg.com/) | >= 0.24 | An alternative to [npm](https://github.com/npm/npm) |
| βœ” | [Firefox](https://www.mozilla.org/en-US/firefox/new/) | >= 50 | We'll need Firefox briefly in order to create certificates. |
| βœ” | [SQLite 3](http://sqlite.com/) | >= 3 | Embedded database |

#### VS Code Extensions

Additionally, to take advantage of syntax hilighting, static code analysis and other editor features, you'll want to install the latest version of the following VS Code extensions

| Required | Extension | Notes |
| -------- | ------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| βœ” | [sass-indented](https://marketplace.visualstudio.com/items?itemName=robinbentley.sass-indented) | Syntax highlighting and code completion support for [Sass](http://sass-lang.com) stylesheets |
| βœ” | [eslint](https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint) | Static code analysis for JavaScript and JSX files |
| βœ” | [jest](https://marketplace.visualstudio.com/items?itemName=Orta.vscode-jest) | Syntax highlighting for [Jest snapshot testing](https://facebook.github.io/jest/docs/snapshot-testing.html) and in-editor test pass/fail statuses |
| | [vscode-icons](https://marketplace.visualstudio.com/items?itemName=robertohuertasm.vscode-icons) | Better file and folder icons |
| | [rest-client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) | An in-editor REST client, so we can experiment with our API effortlessly |

#### Global Node.js Packages

Make sure you have these npm packages installed globally. This can be done by running

```
npm install -g
```

| Required | Library | Version Range |
| -------- | ----------------------------------------------------------------------- | ------------- |
| βœ” | [babel-eslint](https://github.com/babel/babel-eslint) | ^7.0.0 |
| βœ” | [eslint](https://github.com/eslint/eslint) | ^4.0.0 |
| βœ” | [eslint-plugin-babel](https://github.com/babel/eslint-plugin-babel) | ^4.0.0 |
| βœ” | [eslint-plugin-react](https://github.com/yannickcr/eslint-plugin-react) | ^7.1.0 |
| βœ” | [web-push](https://github.com/web-push-libs/web-push) | ^3.0.0 |

#### Project setup

Finally, while in the top-level folder of this project, download the and install this project's dependencies by running

```
yarn
```

We'll also need some certificates so we can run a development webserver over HTTPS. You can generate them by running

```
yarn prepcerts
```

To start the server, run

```sh
yarn watch
```

(Pro tip: If everything looks like it works, but you can't access the page in your browser, make sure you're using _HTTPS_. Try [https://localhost:3000/](https://localhost:3000/).)

# Files and Folders

This is a free-standing client/server Progressive Web App system, including

- A database
- A REST API
- A web client, which starts out as a conventional single-page app, and becomes a progressive web app you progress through the workshop

```
Project
β”‚
β”œβ”€ client/ πŸ“± React.js web client
β”‚ β”œβ”€ components/ πŸ“Š React components
β”‚ β”‚ β”‚
β”‚ β”‚ β”œβ”€ my-thing/index.jsx Component implementation
β”‚ β”‚ β”œβ”€ my-thing/index.test.js Component tests
β”‚ β”‚ └─ my-thing/styles.scss Component styles
β”‚ β”‚
β”‚ β”œβ”€ routes/ πŸ” Top-level React components, each corresponding to a "page" in our app
β”‚ β”œβ”€ sass/ πŸ’… Global Sass stylesheets
β”‚ β”œβ”€ app.jsx 🎁 React "App" component
β”‚ β”œβ”€ index.js 🎬 Web client entry point
β”‚ └─ index.ejs πŸ“„ Template for web client index.html
β”‚
β”œβ”€ db/ πŸ’Ύ SQLite databases
β”œβ”€ dist/ πŸ“¦ Web client development/production builds
β”œβ”€ server/ πŸ›’ Node.js API to support the web client
β”œβ”€ webpack/ βš™οΈ Build configuration
└─ .vapid.json πŸ” VAPID private and public keys
```

# How to use it

#### Generate x509 Certificates for serving over HTTPS

`npm run prepcerts`

#### Start the Development Server

To start the development server, run

```sh
npm run watch
```

If you want, you can start the API and UI independently, by running

```sh
npm run watch:api # API only
npm run watch:ui # UI only
```

#### Build Development Assets in the `/dist` folder

This will be an un-minified version of an exercise, and will include some webpack-specific tooling, intended only for development use

`npm run build:dev`

#### Build Production Assets in the `/dist` folder

This will be an an optimized version of the exercise

`npm run build:prod`

#### Run tests

`npm test`

#### Clean old builds

`npm run clean`

# What are the pieces?

- [Webpack 3](https://webpack.js.org)
- [Babel](http://babeljs.io/) 7.x, setup with the [babel-preset-env](https://github.com/babel/babel/tree/7.0/packages/babel-preset-env) plugins, compiling to ES5 JavaScript
- [ESLint](https://github.com/eslint/eslint) for linting JS and JSX
- [sass-loader](https://github.com/webpack-contrib/sass-loader) for traditional management of [Sass](http://sass-lang.com/) styles
- [extract-text-webpack-plugin](https://github.com/webpack-contrib/extract-text-webpack-plugin) so compiled styles are external stylesheets instead of inline style blocks
- [React](http://facebook.github.io/react/) as a component library
- [MUI](https://www.muicss.com/) as a lightweight (6.6K) Material Design inspired UI kit
- [Jest](http://facebook.github.io/jest/) as a testing platform
- [SimpleHTTP2Server](https://github.com/GoogleChrome/simplehttp2server) as a HTTP/2 proxy (for development only)
- [SQLite3](https://www.sqlite.org/) - as a lightweight, embedded database (for API)
- [Express](http://expressjs.com/) - as a HTTP server for our API.

# License

While the general license for this project is the BSD 3-clause, the exercises
themselves are proprietary and are licensed on a per-individual basis, usually
as a result of purchasing a ticket to a public workshop, or being a participant
in a private training.

Here are some guidelines for things that are **OK** and **NOT OK**, based on our
understanding of how these licenses work:

### OK

- Using everything in this project other than the exercises (or accompanying tests)
to build a project used for your own free or commercial training material
- Copying code from build scripts, configuration files, tests and development
harnesses that are not part of the exercises specifically, for your own projects
- As an owner of an individual license, using code from tests, exercises, or
exercise solutions for your own non-training-related project.

### NOT OK (without express written consent)

- Using this project, or any subset of
exercises contained within this project to run your own workshops
- Writing a book that uses the code for these exercises
- Recording a screencast that contains one or more of this project's exercises

# Copyright

Β© 2017 [Mike Works, Inc.](https://mike.works) and [Steve Kinney](http://www.stevekinney.net), All Rights Reserved

###### This material may not be used for workshops, training, or any other form of instructing or teaching developers, without express written consent