It doesn't, but.. nothing does.
Pokey doesn't seem to have a predominant use-case just yet. In theory it sounds good- then the possibility of native notifications seem to collapse the idea.
I think pokey can serve as a really good platform for apps who can't figure out push notifications as quickly as they can develop a mobile client.
For instance- once I form communities, I will be dependent on only the apps which can cater to them. At this time, Flotilla is the only app that truly does this. If I am more of an operator than a client dev- I'm SOL.
The addition of nip-29 support in pokey would allow communities who use flotilla to furthermore add notification support for their own custom clients down the line. As they progress into sovereign ecosystems, pokey can probably get left behind for that subset of users, at least in regards to that specific ecosystem's notifications.
I think pokey might need some work to feel more reliable and feature-rich.. but it seems like a really good option for some developers who aren't sure how to go full native.
All of this aside- I think flotilla alone will require some granual notification support that we haven't seen yet in any client. Once communities do scale, our notifications will easily begin to overwhelm. I can already imagine channel-level controls for push notifs.
It's a lot to imagine doing, but it seems rather logical to me, in consideration to all of the people and developers who might use and bridge with both pokey and flotilla, and relaytools and so on.
I see pokey as the future Amber for notifications and I think most mainstream client devs will try to avoid it- but embracing it could be very powerful for the ecosystem.
