Feature Set Request

[gauntface]

Client:

• Dedupe push with native app
• How to distinguish between dismiss and failed subscription attempt
  • This is in reference to a subscribe() call failing due to network error (for example).

Worker:

• Coalesce Notifications
• How to manage analytics
• Notification Icon recommendations
• How to handle two push events firing simultaneously
  • Can be handled by keeping a reference of the current wait until and ignoring the second push
• Re-use existing pages rather than opening a new tab on notification click
• Skip notifications when the page is visible
• Hide notifications when the page is focused

Server:

• Setting TTL

[addyosmani]

@owencm do you have any insight/personal preferences on prioritisation of the items in this list given your experience with Propel?

Personally would love to see notification coalescence in the worker and multiple push events firing simultaneously.

[owencm]

The top priority (and largely easy) are: Coalescing notifications, skipping notifications when the page is visible, hiding notifications when the page is focused, handling simultaneous push events and re-using existing pages rather than opening a new tab on notification click.

Getting them baked in would be 60-70% of the nasty edge cases taken care of.

[gauntface]

FYI I have some of these in a couple of branches, was waiting on a PR to
get in first which I think I'm still waiting on.... Although been a while
since I checked.

On Tue, 26 Apr 2016, 00:16 Owen Campbell-Moore, notifications@github.com
wrote:

The top priority (and largely easy) are: Coalescing notifications,
skipping notifications when the page is visible, hiding notifications when
the page is focused, handling simultaneous push events and re-using
existing pages rather than opening a new tab on notification click.

Getting them baked in would be 60-70% of the nasty edge cases taken care
of.

—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
#29 (comment)