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

Similar to your open question…

> Do we allow a notification payload whose only member is `"app_badge"`, skipping the notification but allowing efficient updating of the application badge?

…should this allow notification payloads with just `"data"`? The use case would be apps that keep settings like, say, the chosen app language purely on the client. For example, for an airline travel app, this would allow the server to send a notification with a `"data"` object like…

```json
{
  "data": {
    "type": "gate_change",
    "details": {
      "old": 12,
      "new": 25
    }
  }
}
```

…that the app could then dynamically expand to a notification like _"There's a gate change for your flight, the old gate was 12, the new gate is now 25"_ when the app language is set to English, and translations thereof for other languages. This of course requires allowing script execution, so may be out of scope slightly.

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

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