# Rich Notifications support for DiscourseHub

**URL:** https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981
**Category:** Feature
**Tags:** discourse-hub
**Created:** [December 27, 2022, 8:17pm UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981 "2022-12-27T20:17:36Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [December 27, 2022, 8:17pm UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/1 "2022-12-27T20:17:37Z")

</div>

Hello,

On iOS, There’s something called Rich Notifications. It’s where you can interact with them on your Apple Watch, or pull down to interact with them without opening the app.  
Example (Twitter):

 ![image](https://global.discourse-cdn.com/meta/original/4X/0/5/4/054bf66ce3f116d227d12212f18ace13903fc13c.jpeg)  
I think that Discourse could benefit from a direct reply option, and a like button. This could also open a viewport instead, so we can use markdown instead of plain text. Discourse Chat could use the plain input box.  
This would be helpful when I’m not by my computer and am doing something like playing a game which cannot be out on idle and I have to reply to something.

Another issue I have with the app is delayed and inconclusive notifications when your site is not hosted by Discourse.  
I dont see why this happens, as other 3rd party apps like Fig have done it fine. I could be wrong, but it’s slightly annoying to have to download another app just to get push notifications which aren’t 20 minutes late and just say `@User posted in Topic`, when on Discourse forums such as Meta they’re instant and say`"@User posted in Topic: "Content"`

Again, I could be wrong about any of this, but it’s possible.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [December 27, 2022, 11:26pm UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/2 "2022-12-27T23:26:22Z")

</div>

CDCK provides notifications for Meta and the sites they’re paid to host.

Fig provides notifications because the app itself is $20 a year, covering the cost of the notification service.

I’m sure this has been discussed and they will correct me if I’m wrong, but I don’t think it’s remotely practical to ask CDCK to pick up the tab for the notification infrastructure to route hundreds of millions of messages. After all, it’s a selling point of their hosting.

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [December 28, 2022, 1:17am UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/3 "2022-12-28T01:17:29Z")

</div>

> [@darkpixlz](#):
>
> I think that Discourse could benefit from a direct reply option

Discourse Chat notifications on compatible browsers already support this

> [@Quick replies for Discourse Chat notifications](https://meta.discourse.org/t/quick-replies-for-discourse-chat-notifications/245358):
>
> Starting today, the Discourse Chat notification allows users to reply inline in the notification itself tada The UI for this is different on every OS, as it integrates into the native notification system. Smartwatch Android Wear OS Android Windows All going well, possible next steps for around …

> [@darkpixlz](#):
>
> It’s where you can interact with them on your Apple Watch

I’m using my WearOS watch to reply to chat mentions all the time, it’s awesome. And since it’s based on the web standard, it works on Windows, Android and ChromeOS.

Apple made a promise to support the WebPush standard in 2023, so let’s hope they do it properly with support to inline replies built in.

---

<div class="post-metadata">

### Author: ![hiddenseal](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hiddenseal/32/284273_2.png) [@hiddenseal](https://meta.discourse.org/u/hiddenseal)
#### Post date: [December 28, 2022, 2:20am UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/5 "2022-12-28T02:20:13Z")

</div>

> [@darkpixlz](#):
>
> Another issue I have with the app is delayed and inconclusive notifications when your site is not hosted by Discourse.

Didn’t you ask this question before?

> [@Hub app does not give notifications until you open it](https://meta.discourse.org/t/hub-app-does-not-give-notifications-until-you-open-it/236452/2):
>
> Push notifications for iOS users are only “real-time” if your community is hosted by CDCK (the paid plan of Discourse). If you are self-hosted, push notifications come with a certain delay.

> [@darkpixlz](#):
>
> I dont see why this happens

See:

> [@Push Notifications on iOS](https://meta.discourse.org/t/push-notifications-on-ios/138868/10):
>
> I can provide this. Fundamentally cause this is Apple’s job not our job. They are the ones who suck here, Android have supported this for years. Why should thousands of self hosted Discourse instances send us private user information? If this thing is opt in what could we charge for this? At best pittance. This introduces a legal liability for both Discourse on various self hosted instances out there. This is not going to be happening, some third party can create a service for you. The APIs a…

---

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [December 28, 2022, 2:25am UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/6 "2022-12-28T02:25:03Z")

</div>

Yes I did, I said that it could be a fix but I was told why it probably won’t happen:

> [@Rich Notifications support for DiscourseHub](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/2):
>
> CDCK provides notifications for Meta and the sites they’re paid to host. Fig provides notifications because the app itself is $20 a year, covering the cost of the notification service. I’m sure this has been discussed and they will correct me if I’m wrong, but I don’t think it’s remotely practical to ask CDCK to pick up the tab for the notification infrastructure to route hundreds of millions of messages. After all, it’s a selling point of their hosting.

---

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [December 28, 2022, 1:48pm UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/7 "2022-12-28T13:48:52Z")

</div>

To avoid this you can also use the [Whitelisted app codebase](https://meta.discourse.org/t/whitelisted-discourse-app-with-push-notifications-via-onesignal/58247) and deploy to the stores. Or wait for Apple to fix their shameless anti-competitive monopolistic behaviour in this space (or the EU or Congress to force them to)

---

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [February 17, 2023, 11:19pm UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/15 "2023-02-17T23:19:34Z")

</div>

In 16.4, Apple is finally adding support for push notifications in Safari.  
[For anybody interested, here’s the blog post.](https://webkit.org/blog/13878/web-push-for-web-apps-on-ios-and-ipados/)

Checking on my phone, seems like Discourse is confused

 ![IMG_4809](https://global.discourse-cdn.com/meta/original/4X/a/f/1/af192538aa963b991f17a9a91c63f507193e5c7f.jpeg)

---

<div class="post-metadata">

### Author: ![dfabulich](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dfabulich/32/108716_2.png) [@dfabulich](https://meta.discourse.org/u/dfabulich)
#### Post date: [February 18, 2023, 2:07am UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/16 "2023-02-18T02:07:42Z")

</div>

This is only a partial screenshot. Did you add the forum to your Home Screen first? (That’s the secret rule of iOS 16.4 push notifications. Regular web sites can’t request push permissions; it only works when you A2HS.)

---

<div class="post-metadata">

### Author: ![darkpixlz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/darkpixlz/32/549896_2.png) [@darkpixlz](https://meta.discourse.org/u/darkpixlz)
#### Post date: [February 18, 2023, 2:16am UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/17 "2023-02-18T02:16:06Z")

</div>

> [@dfabulich](#):
>
> That’s the secret rule of iOS 16.4 push notifications.

Nope. This is on Meta, I’ll probably just remove DiscourseHub and use all of my communities as web apps to utilize this from now on

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [February 18, 2023, 2:23am UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/18 "2023-02-18T02:23:52Z")

</div>

Already discussed on [iOS 16 web push notifications in 2023](https://meta.discourse.org/t/ios-16-web-push-notifications-in-2023/229240)

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [February 18, 2023, 2:23am UTC](https://meta.discourse.org/t/rich-notifications-support-for-discoursehub/249981/19 "2023-02-18T02:23:55Z")

</div>


