This is a guide kit is designed to show how to make a Progressive Web App(PWA) and PWA features in React.js development environments. Customized and opinionated tools and build process are optimized to achive high-performed web application which is audited by strict auditor, Lighthouse. Moreover, this guide kit is also backed by Firebase for hosting, realtime database, and also push notification.
Demo is working on firebase hosting. Please take a look.
- Material Design and AppShell: Responsive, fit any form factor, desktop but the first is mobile. AppShell architecture implemented wearing material design got bressed by material-ui.com
- ES6 via Babel: You can use ES6 feature with same babel-preset to create-react-app and dynamic module importing
- Remarkable configurations: Webpack configuration file has been written in configurable, optimzied and easy settings
- Developing Progressive Web App: You can check them of optimized bundling for PWA including code-splitting, multiple chunk and preload. As developing, reloading changes instantly by webpack-dev-server, also it is working well with service worker
- HTTPS: Deploying to Firebase Hosting to run perfectly on HTTPS with PWA features
- Web Push: Web Push demo also is branded at this app by Firebase Push Messaging
- Service Worker: Generating service worker scripts is completly intergrated in build process with Webpack 2 and plugins
- Web Manifest: Have a look how to installable webapp work by Web Manifest
- Realtime Database: We featured firebase to show PWA how to work with fetched data and cached data via service worker
- Server Side Rendering: Deprecated in favour of using code splitting and react-router 4
Presenting intial page in short time is an important issue. This guide kit includes simple server side code for demonstration. Buidling PWA for Server Side Rendering version landed You can take a look what is different between both of versions
- React Lite Support: To achieve minimal vundle size at initializing time of the app, we support for building with react-lite. Simple, you can get another version of app running on
react-liteif you could add the additional argument on build command when you build
To use filrebase cli tool, you must setup firelbase cli and then logged into firebase by
firebase login. To do this please refer to firebase cli guide. And then you need to create a new project on firebase and get the intialize codes from firebase, which are API_KEY, MESSAGING_SENDER_ID, DATABASE_URL, to save at .env. If you're not familiar with a brand new filrebase? you can have a look for official guide
# install dependencies yarn install # firebase init, input with following answers # > select `hosting only` # > select `your project` or `create one` # > input `build` as your public directory, which is default build path # > answer `no` for configuration as a single-page app # > no overwrite any files in source firebase init # copy into .env and update values in the file with the intialize value you get from firebase in compliance with loading env as you build cp .env.example .env
We support three versions of build, production, development(debug) and ssr. All of build files will be in
# build in production npm run build # build in debug npm run build:debug
Run PWA on Server
# starting app by webpack-dev-server npm start
Deployment when you ready for production
You need to check that configuration again. You must have a project on firebase, this project have the suitable settings for firebase generated by fireblase cli and .env file must be exist with the initialize code from firebase
# make sure that run `yarn build` before you try to deploy the app to firebase npm run deploy
Testing Firebase Cloud Messaging for Push
This guide-kit use Push Messaging built on top of Firebase Cloud Messaging.
Notification page will show you peer token to send push message to current opened tab. To do this,
fcm-cli is a really simple and powerful tool for testing FCM on terminal. This video will cover how to deal with fcm-cli and FCM (Korean)
Registering a Service Worker without a trusted SSL Connection will fail with: Failed to register a ServiceWorker: An SSL certificate error occurred when fetching the script.
webpack-dev-server --https will use a self signed certificate, which is not trusted.
Using Google Chrome, use the following flag to ignore
Lighthouse Audit Result