5 ms·

Chrome has perfectly acceptable push notification support. I am an occasional user of Facebook Messenger, and using the mobile website was perfect: I don't car

by codeka 10y ago

Chrome has perfectly acceptable push notification support. I am an occasional user of Facebook Messenger, and using the mobile website was perfect: I don't care if notifications are delayed or even lost (I'll see the messages eventually anyway). But there's no way I'm going to install a separate app for something I use maybe once a week, tops. If it stops working from the mobile website, then I just wait until I'm back at my computer to read fb messenges.

galistoca 10y ago
I'll assume, by Chrome you mean desktop Chrome. This is irrelevant to my comment. I was specifically talking about realtime push notifications via mobile devices. Also remember that your preference is just your preference, many people would want to be able to make sure their messages get seen in realtime. And Facebook probably wants that for their users too. Again, I'm not saying this is a good thing. I'm just saying it's not an illogical decision. You are free to complain but it would be stupid for Facebook to keep going this way just so they can support the legacy technology.
- lelandbatey 10y ago
  Chrome on Android does support real-time push notifications. I know because I was notified of a friend's Facebook post I was mentioned in within 5 seconds of my friend posting it. I don't have Facebook installed on my phone, and he posted it from his phone while my phone was face up on the table between us and we both where surprised at how fast I was notified.
  - Ronsenshi 10y ago
    Con confirm. Worked with real time push notifications via Service Workers in Chrome myself.
  - galistoca 10y ago
    Please read my other comments on this thread. Basically just because Android supports it doesn't mean it's all good since iOS doesn't. Also the "open web" you think you have on Chrome is not really that open as you think if you think about the entire mobile ecosystem landscape.
- colordrops 10y ago
  Android Chrome supports push notifications, even when the browser is not loaded.
  - galistoca 10y ago
    I keep saying this in every comment I made on this thread, but I'm talking about the entire mobile ecosystem. Who cares if Android Chrome supports it, iOS doesn't. Which means it's not a 100% coverage. Just by letting this happen you are providing a low quality service to not just the iOS users but also the Android users, since there will be an assumption that the recipient doesn't always get the message in realtime. If you want to send that kind of messages, there is always email. Messaging apps are built on assumptions that people know the other person receives push immediately.
    - suppressingfire 10y ago
      I call shenanigans for two reasons: 1) you can never assume a recipient ever has their phone on, with them and in a non-silent mode 2) users can disable push notifications for individual apps anyway
      - galistoca 10y ago
        For some reason I feel like I have become some sort of FB defender, but I am not. Just to be clear, I am not a fan of FB. I even completely got rid of my FB account a year ago because I got sick of fake interactions on the site and have never looked back. I am happy with communicating with close people just via text and other special purpose communication apps. That said, the reasons you mention are pretty edge cases. Instead of just hating on it, just stop and think about it for a moment without prejudice. When you email someone you don't expect them to read it immediately, but when you send a text you at least expect them to know they received something, no? (If you say no to this, I really have nothing else to say anymore, you would be just denying the reality) That's what Facebook wants to be. They're competing with SMS, not email.
        10y ago
personjerry 10y ago
Safari doesn't though :/
wodenokoto 10y ago
> I don't care if notifications are delayed or even lost But I hope you can imagine why a chat team does care if a technology doesn't allow them to send timely and reliable notifications. It is often better to have no feature than a bad feature. I've never used the mobile web messenger, but if it is unreliable, only works in a few browsers, it makes sense to remove the product.
- yason 10y ago
  The mobile Facebook website worked fine with messages. You could see whether there were new messages and you could read them and reply to them. You could even chat a bit albeit not as conveniently as on a laptop or a messaging app such as Hangouts or Whatsapp. But it was just enough to keep you connected when needed.
- codeka 10y ago
  > But I hope you can imagine why a chat team does care if a technology doesn't allow them to send timely and reliable notifications. Sure, that's why they have the app. But it's not a reason to completely turn off messaging from the website. Heck, they could even turn off chrome notifications completely and the website would still be completely functional.
- lucb1e 10y ago
  More likely the chat team couldn't read your contacts through your web browser and decided to do something about it.

by codeka 10y ago

galistoca 10y ago

I'll assume, by Chrome you mean desktop Chrome. This is irrelevant to my comment. I was specifically talking about realtime push notifications via mobile devices. Also remember that your preference is just your preference, many people would want to be able to make sure their messages get seen in realtime. And Facebook probably wants that for their users too. Again, I'm not saying this is a good thing. I'm just saying it's not an illogical decision. You are free to complain but it would be stupid for Facebook to keep going this way just so they can support the legacy technology.

lelandbatey 10y ago
Chrome on Android does support real-time push notifications. I know because I was notified of a friend's Facebook post I was mentioned in within 5 seconds of my friend posting it. I don't have Facebook installed on my phone, and he posted it from his phone while my phone was face up on the table between us and we both where surprised at how fast I was notified.
- Ronsenshi 10y ago
  Con confirm. Worked with real time push notifications via Service Workers in Chrome myself.
- galistoca 10y ago
  Please read my other comments on this thread. Basically just because Android supports it doesn't mean it's all good since iOS doesn't. Also the "open web" you think you have on Chrome is not really that open as you think if you think about the entire mobile ecosystem landscape.
colordrops 10y ago
Android Chrome supports push notifications, even when the browser is not loaded.
- galistoca 10y ago
  I keep saying this in every comment I made on this thread, but I'm talking about the entire mobile ecosystem. Who cares if Android Chrome supports it, iOS doesn't. Which means it's not a 100% coverage. Just by letting this happen you are providing a low quality service to not just the iOS users but also the Android users, since there will be an assumption that the recipient doesn't always get the message in realtime. If you want to send that kind of messages, there is always email. Messaging apps are built on assumptions that people know the other person receives push immediately.
  - suppressingfire 10y ago
    I call shenanigans for two reasons: 1) you can never assume a recipient ever has their phone on, with them and in a non-silent mode 2) users can disable push notifications for individual apps anyway
    - galistoca 10y ago
      For some reason I feel like I have become some sort of FB defender, but I am not. Just to be clear, I am not a fan of FB. I even completely got rid of my FB account a year ago because I got sick of fake interactions on the site and have never looked back. I am happy with communicating with close people just via text and other special purpose communication apps. That said, the reasons you mention are pretty edge cases. Instead of just hating on it, just stop and think about it for a moment without prejudice. When you email someone you don't expect them to read it immediately, but when you send a text you at least expect them to know they received something, no? (If you say no to this, I really have nothing else to say anymore, you would be just denying the reality) That's what Facebook wants to be. They're competing with SMS, not email.
      - 10y ago

personjerry 10y ago

Safari doesn't though :/

wodenokoto 10y ago

> I don't care if notifications are delayed or even lost But I hope you can imagine why a chat team does care if a technology doesn't allow them to send timely and reliable notifications. It is often better to have no feature than a bad feature. I've never used the mobile web messenger, but if it is unreliable, only works in a few browsers, it makes sense to remove the product.

yason 10y ago
The mobile Facebook website worked fine with messages. You could see whether there were new messages and you could read them and reply to them. You could even chat a bit albeit not as conveniently as on a laptop or a messaging app such as Hangouts or Whatsapp. But it was just enough to keep you connected when needed.
codeka 10y ago
> But I hope you can imagine why a chat team does care if a technology doesn't allow them to send timely and reliable notifications. Sure, that's why they have the app. But it's not a reason to completely turn off messaging from the website. Heck, they could even turn off chrome notifications completely and the website would still be completely functional.
lucb1e 10y ago
More likely the chat team couldn't read your contacts through your web browser and decided to do something about it.