|
|
|
|
|
by GranPC
1664 days ago
|
|
I tried using the web notification API for a project recently - a project which is putting users' needs and wants above anything else. Our users wanted to receive push notifications whenever we go live, so the initial prototype used SMS notifications since that's what we were already using. Over time, the cost of these (completely optional and opt-IN) notifications grew enough that I figured it was time to seek an alternative. I fully implemented WebPush notifications and evaluated them with my users. I found that most Android devices wouldn't vibrate nor make a sound when a notification is received, and iOS straight up doesn't support these APIs. With these findings, I scrapped the entire implementation. It was useless to our users and only led to more confusion. If I had to guess, I would say that is the exact reason 99% of WebPush usage is spammy. Spammers don't really care about quality of service, they just want to cast a wide net. I'm willing to bet the API would see a massive uptick in legitimate adoption if it wasn't so utterly useless in the real world. |
|