-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace bubbles that send no ID #71
Labels
Comments
I'm leaning toward replacement being opt-out. We don't want to encourage apps to spam with a lot of notifications, so we could just show the latest notification (assuming no ID), or let developers send an ID to get the privilege of more than one notification. Basically, reward proper usage. 😄 |
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if this is a great idea or a terrible idea. Should replacing be opt-in or opt-out?
What I mean is, if you're an app developer and your app sends a notification: should you have to opt-out of replacing previous notifications by supplying a unique ID or should notifications only be replaced if you opt-in by supplying the same ID?
Currently, we create a random ID based on notification spawn time if the ID is null, but we could instead use the app ID as a fallback
The text was updated successfully, but these errors were encountered: