Re: [w3c/push-api] Declarative Web Push (Issue #360)

Turbocat6413 left a comment (w3c/push-api#360)

This all does sound interesting, however I am concerned about the following problems that may come with the new standard:

1. What if all localization (including push notifications) is stored on the client? (e.g. IndexedDB)
2. What to do if, say, we have a messenger application in which the user has the ability to delete a message for two interlocutors (hence, as on native applications, the notification must be deleted from the notification item)
3. How do you envision actions? Their original idea was that they are just buttons that seamlessly call js-functions in the background (e.g. “mark as read” action in messenger). In this case, however, we only have a url. This would be great to use if the url doesn't have to open as a page, but is an endpoint for the HTTP REST API of the sender
4. Again, as with the messenger app example, are you considering extending the standard in the future to include message notifications with an interactive display of the sender contact (avatar and name) as in native apps?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/360#issuecomment-2764397452
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/push-api/issues/360/2764397452@github.com>