From 38ccc6f03d189ded1f51338538cf51132892004b Mon Sep 17 00:00:00 2001 From: Paul Ailincai Date: Tue, 2 Jun 2020 15:45:46 +0400 Subject: [PATCH] Recommend a PWA implementation path --- DEVELOPMENT_PATH_WEB.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/DEVELOPMENT_PATH_WEB.md b/DEVELOPMENT_PATH_WEB.md index bf5df3d..504fe5a 100644 --- a/DEVELOPMENT_PATH_WEB.md +++ b/DEVELOPMENT_PATH_WEB.md @@ -17,5 +17,8 @@ meteor add activitree:push Copy the worker file here: https://github.com/activitree/meteor-push/blob/master/example/app/public/firebase-messaging-sw.js to your public folder. This needs to be available at https://www.your_address.com/firebase-messaging-sw.js. This worker is responsible for handling backgroud messages. Your 'action' key in the notification object contains the URL that will be open when the notification on screen is being clicked on. +** If you are looking for a more complex implementation of a Meteor PWA with Notifications, Offline Caching and Offline experience, please visit this repo: https://github.com/activitree/Meteor-PWA-Explained + + ***Note:*** With Firebase, some of the public credentials are exposed and visible on the client. Read this for an understanding of how to restrict public API keys in Firebase: https://medium.com/@impaachu/how-to-secure-your-firebase-project-even-when-your-api-key-is-publicly-available-a462a2a58843