web push notifications whois
play

Web Push Notifications Whois They are for push Whois They are - PowerPoint PPT Presentation

Web Push Notifications Whois They are for push Whois They are for push Timely Whois They are for push Timely Relevant and Secure Whois They are for push Timely Relevant and Secure


  1. Web Push Notifications

  2. Whois ● They are for push

  3. Whois ● They are for push ● Timely

  4. Whois ● They are for push ● Timely ● Relevant and Secure

  5. Whois ● They are for push ● Timely ● Relevant and Secure ● "Cross-platform" and "Cross-browser"

  6. "Cross-platform" and "Cross-browser" ● Service Workers background ● Push API receive messages from the server ● Notification API display messages natively

  7. "Cross-platform" and "Cross-browser" Mobile (not iOS yet) Desktop + Chrome + Chrome + Firefox + Firefox + Opera + Opera + Safari

  8. Push API Notification API Service Workers

  9. How it works 4 Message Server Client 2 3 4 1 Your App

  10. Message Server Sends message to your customers ● Accepts requests from your application ● Application key and Client token must have ● Dispatch message to the destination device

  11. Message Server ● FCM: Google, free (former GCM) Register and create application key in developer console ● APNS: Apple, needs certified developer or 100$ annually ● MSP: Mozilla Push Service, free. No registration required, open standard

  12. How it works Message Server Client 1 Subscribe, ask for client token Your App

  13. How it works Message Server Client 2 Get client token from Message Server 1 Your App

  14. How it works Message Server Client 2 3 Return client token to the web app 1 Your App

  15. How it works 4 dispatch Enqueue message Message Server Client 2 3 Send notification to tokenized endpoint 4 1 Your App

  16. https://firebase.google.com/docs/cloud-messaging/http-server-ref

  17. https://firebase.google.com/docs/cloud-messaging/http-server-ref

  18. https://firebase.google.com/docs/cloud-messaging/http-server-ref

  19. messaging.onMessage event

  20. TTL (1 month by default)

  21. On time

  22. The Firebase JavaScript SDK way ● Only client token needed, no encrypting payloads ● Custom features ● Supports Android, iOS and web Easy to use ● The VAPID way ● No sender_id required ● Chrome, Firefox supported (more will join) No Account with GCM required ● ● Tends to replace proprietary API

  23. :( ● No guarantee of delivery (even if browser opened and sw works) ● Still no wide support ● Every device needs to be registered ● ...

  24. Why bother? https://www.urbanairship.com https://pushpad.xyz https://www1.vizury.com https://moengage.com etc.

  25. Demo to play https://killoff.github.io/serviceworker/ Q & A References https://developers.google.com/web/fundamentals/push-notifications/ https://developers.google.com/web/updates/2016/07/web-push-interop-wins https://firebase.google.com https://medium.com/@firt/progressive-web-apps-on-ios-are-here-d00430dee3a7 https://github.com/digitaldrk/push_notifications

Recommend


More recommend