angular-performance-checklist - Cheatsheet for developing ⚡lightning⚡ fast progressive Angular applications

This document contains a list of practices which will help us boost the performance of our Angular applications. "Angular Performance Checklist" covers different topics - from server-side pre-rendering and bundling of our applications, to runtime performance and optimization of the change detection performed by the framework.Some practices impact both categories so there could be a slight intersection, however, the differences in the use cases and the implications will be explicitly mentioned.

expenses - 💰Expense tracker using Google Sheets 📉 as a storage written in React

•    Javascript

💰Expenses is a progressive web application on top of Google Sheets 📉 written in React ⚛️. It is only a static HTML that works great on mobile 📱 and can be deployed anywhere.Check out the demo but please be considerate and don't break it for others.

awesome-pwa - Awesome list of progressive web apps! (PR welcomed ;))

Inspired by the awesome list thing. A Progressive Web App uses modern web capabilities to deliver an app-like user experience. They evolve from pages in browser tabs to immersive, top-level apps, leveraging the web's low friction.

service-workers - A collection of utilities for creating/testing/experimenting with service workers.

•    Javascript

A collection of service worker generation tools. Configurable and forkable. A node module for generating service worker files based on provided configuration options.

budgeting-sample-app-webpack2 - Budgeting - React + Redux + Webpack 2 (tree shaking) Sample App

•    Javascript

Production-ready React + Webpack architecture implemented on consumer web apps of some of the most successful enterprises in the world. Perceived performance and development experience are key factors in this setup. You can use this code base for learning or to scaffold your mission-critical project. See live demo.

offline-plugin - Offline plugin (ServiceWorker, AppCache) for webpack (https://webpack.js.org/)

•    Javascript

This plugin is intended to provide an offline experience for webpack projects. It uses ServiceWorker, and AppCache as a fallback under the hood. Simply include this plugin in your webpack.config, and the accompanying runtime in your client script, and your project will become offline ready by caching all (or some) of the webpack output assets.

offline-first - :electric_plug: Everything you need to know to create offline-first web apps.

Inspired by the awesome list thing. This specification highlights features (SQL, offline application caching APIs as well as online/offline events, status, and the localStorage API) from HTML5 and provides brief tutorials on how these features might be used to create Web applications that work offline.

sw-precache - A node module to generate service worker code that will precache specific resources so they work offline

•    Javascript

Service Worker Precache is a module for generating a service worker that precaches resources. It integrates with your build process. Once configured, it detects all your static resources (HTML, JavaScript, CSS, images, etc.) and generates a hash of each file's contents. Information about each file's URL and versioned hash are stored in the generated service worker file, along with logic to serve those files cache-first, and automatically keep those files up to date when changes are detected in subsequent builds. Serving your local static resources cache-first means that you can get all the crucial scaffolding for your web app—your App Shell—on the screen without having to wait for any network responses.

sw-toolbox - A collection of service worker tools for offlining runtime requests

•    Javascript

Service Worker Toolbox provides some simple helpers for use in creating your own service workers. Specifically, it provides common caching strategies for dynamic content, such as API calls, third-party resources, and large or infrequently used local resources that you don't want precached. Service Worker Toolbox provides an expressive approach to using those strategies for runtime requests. If you're not sure what service workers are or what they are for, start with the explainer doc.

PWA-Book-CN - 第一本 PWA 中文书

第一本 PWA 中文书

budgeting - Budgeting - React + Redux + Webpack (tree shaking) Sample App

•    Javascript

Production-ready React + Webpack architecture implemented on consumer web apps of some of the most successful enterprises in the world. Perceived performance and development experience are key factors in this setup. You can use this code base for learning or to scaffold your mission-critical project. See live demo.

create-react-pwa - https://github

•    HTML

https://github.com/facebookincubator/create-react-app + Progressive Web App goodness

hoverboard - GDG DevFest website template

•    HTML

Project Hoverboard is the conference website template that helps you to set up mobile first conference website with blog, speakers and schedule management in a few minutes. The template is created based on 7 years of GDG Lviv team experience of running conferences and feedback from more than 500 event organizers from all around the world who were using previous Hoverboard versions.

UpUp - ✈️ Easily create sites that work offline as well as online

•    Javascript

UpUp is a tiny JavaScript library that makes sure your users can always access your site's content, even when they're on a plane, in an elevator, or 20,000 leagues under the sea. Mobile-First has become the de-facto standard for building modern sites. But in a world where everyone is mobile, an always-on connection isn't something we can rely on. It's time to start thinking Offline First.

Workbox: JavaScript libraries for Progressive Web Apps

•    Javascript

Workbox is a collection of JavaScript libraries for Progressive Web Apps. Workbox is available on npm. We have installation instructions available depending on your build tool or bundler of choice, including webpack. Even on an unreliable connection, your web app can still work using the right runtime caching strategies.

vue-wordpress-pwa - An offline-first SPA using Vue

•    Javascript

This is the code for the FullStackWeekly website. You can use it as a starter pack for your WordPress site as well. Since WordPress can expose a REST API, this project uses Vue.js, Vue-router, Vuex, Vue-resource & Progressive Web App techniques to create an offline-first web client.

preact-pwa - Super fast progressive web app with small footprint & minimal dependancies

•    Javascript

A Super fast progressive web app with a small footprint & minimal dependencies. Features universal rendering, redux, state-driven routing, preact, & service workers. Crunched & optimized with rollup, buble, optimize-js, & purify-css.

StreamSaver.js - StreamSaver writes stream to the filesystem directly asynchronous

•    HTML

StreamSaver.js is the solution to saving streams on the client-side. It is perfect for webapps that need to save really large amounts of data created on the client-side, where the RAM is really limited, like on mobile devices.There is not any magical saveAs() function that saves a stream, file or blob. The way we mostly save Blobs/Files today is with the help of a[download] attribute FileSaver.js takes advantage of this and create a convenient saveAs(blob, filename) function, very fantastic, but you can't create a objectUrl from a stream and attach it to a link...

next-offline - make your Next.js application work offline using service workers via Google's workbox

•    Javascript

Use Workbox with Next.js and easily enable offline functionality in your application. Then create a server.js, because we'll need to serve out service worker.

serviceworker-rails - Use Service Worker with the Rails asset pipeline

•    Ruby

The Rails asset pipeline makes a number of assumptions about what's best for deploying JavaScript, including asset digest fingerprints and long-lived cache headers - mostly to increase "cacheability". Rails also assumes a single parent directory, /public/assets, to make it easier to look up the file path for a given asset. Service workers may only be active from within the scope from which they are served. So if you try to register a service worker from a Rails asset pipeline path, like /assets/serviceworker-abcd1234.js, it will only be able to interact with requests and responses within /assets/**. This is not what we want.