Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Boogie3335yWhy wouldn't you use push notifications for critical feature?! They are great, here, I will show you. The app's name is Duolingo...
-
mostly agree they are not reliable for critical functionalities.
But what else would you propose? -
On a business decision cost is a factor mostly. SMS is expensive and sometimes just as unreliable in cases.
Love the last line of your rant!! Haha. 👌🏼 -
Yes other options like sms are expensive but how expensive is it to have your service not working and a team of devs doing nothing but repeatedly debugging it because management won’t accept it.
In our particular case we need web sockets. We are sending a large number of push notifications to keep refreshing screens and keeping users up to date with status changes.
Backend have said it will take too long to change everything to websockets ... so we aren’t -
jeeper59665y@badcopnodonuts if the user isn’t gonna pay attention either way it doesn’t matter what notif you pick
-
@practiseSafeHex lol wow.. nothing like building solid solutions
And can they just build a websocket layer only for notifications? -
@badcopnodonuts there are a few places we still need to use notifications. But yes there are many uses cases where a straight swap to websockets would fix it. But I don’t think the backend is architected in a way to make that easy
Related Rants
-
BM32180My dumb CEO just hired an even dumber CTO. The new CTO asked me the following questions... 1. What is GitHub...
-
nikmanG16CS Professor: “What M word is the black hole to all productivity?” Student: “Management” CS Professo...
-
wilziack47Jesus, Apple are fucking amazing at design! A keyboard I need to prop up with a book and a mouse I can't use w...
So I've been screaming for months that push notifications are not reliable enough to build critical functionality on top of. Management won't listen and keep pushing ahead with making teams use it because its cheap and easy.
Been debugging an issue on/off for several weeks. Turns out someone in management asked the backend team to cut the expiration time of items down to 5 minutes to increase throughput (without telling mobile). Notifications are regularly taking +4 mins to get to the phones, leaving our users with barely any time to react. They are now complaining.
I swear if there is a single IQ point available between the whole team i've yet to see any evidence of it
rant
push notifications
management
idiots
timing