WhatsApp Web and iOS

Discussion in 'iOS 8' started by GreyOS, Jan 22, 2015.

  1. GreyOS macrumors 68030

    GreyOS

    Joined:
    Apr 12, 2012
    #1
    WhatsApp Web has been released and works with most mobile OSes except iOS.

    WhatsApp said “Apple has no background multi-tasking and no proper push technology. So it is a bad user experience on iOS.”

    I'm surprised as I thought Windows Phone was very similar in that it's locked down with no 'true' multitasking and only allows certain background tasks. Yet it's possible on Windows Phone but not iOS.

    Is anyone able to offer some technical insight into what the problem might be for iOS?

    From what I understand (please correct me if wrong), on other platforms, the messages are routed via phones. e.g. Person A is sending a message to Person B using the web client. The message actually gets sent to Person A's phone. Person A's phone sends the message to Person B's phone. Person B's phone forwards it to the web server so Person B can see it on the web client.

    Now, this is easier on Android, where WhatsApp can run a background service so it's constantly connected to the WhatsApp servers. It can receive and forward messages at any time. But on iOS, WhatsApp can't run in the background. This is probably the initial problem, but again, I thought it would be the same problem on Windows Phone?

    I was also under the impression that background tasks could be initiated by notifications, and also that notifications can be silent. So there wouldn't be any problem for iOS to receive a WhatsApp notification and then this wake up WhatsApp so it can forward it onto the web servers. Then messages sent using the web client could use silent notifications to trigger WhatsApp on the phone to forward it on. So it seems possible on iOS, but I'm not an iOS developer so might be missing some obvious limitations.

    If anyone understands the whole situation better, I'd love to hear your thoughts.
     
  2. LordQ macrumors 68040

    LordQ

    Joined:
    Sep 22, 2012
  3. nightstalkerz macrumors 6502

    Joined:
    May 9, 2013
    #3
    iOS does support push notifications but you have to use the Apple servers and from iOS8, background notifications can download content.

    It seems like WhatsApp just wants to bypass Apple and control all notification related things and also kill your battery.
     
  4. GreyOS thread starter macrumors 68030

    GreyOS

    Joined:
    Apr 12, 2012
    #4
    Doesn't Windows Phone use Microsoft servers for notifications though? I didn't think apps could run in background to handle their own push/pull?
     
  5. bbrks macrumors 65816

    bbrks

    Joined:
    Dec 17, 2013
    #6
    I only wish, WhatsApp would do the same as Viber, so that I can also use it on my lap top.
     
  6. GreyOS thread starter macrumors 68030

    GreyOS

    Joined:
    Apr 12, 2012
  7. xero9 macrumors 6502a

    Joined:
    Nov 7, 2006
    #8
    Initially, I wondered how Apple's limitations in iOS could have any bearing on their web chat not working, but looking at it closer, it seems the web is more of a portal to your chats that are actually taking place on the phone. It could probably work for iOS if one were to leave the screen on and stay within WhatsApp. They likely just didn't bother, because who's going to actually do that.

    It's the same with the sync feature in Plex. On Android you can manage synced content within the Plex service itself, and have it sync content to your Android device where as on iOS you need to leave the app open and running while it completes it. It's quite annoying.
     
  8. Stuke00 macrumors 68000

    Joined:
    Oct 11, 2011
    Location:
    Collinsville,IL
    #9
    Just look at google hangouts. Massive battery drain there.
     
  9. zorinlynx macrumors 601

    zorinlynx

    Joined:
    May 31, 2007
    Location:
    Florida, USA
    #10
    It completely blows my mind what crap WhatsApp is. People should migrate over to Telegram. It just does the job so much better.

    - Clients for pretty much every platform
    - Conversations synced on every client you use
    - Open source client API (anyone can make a client)
    - Private peer to peer off the record conversations

    WhatsApp is such a horrible kludge, having to use the phone as a proxy for the web client to work. It boggles my mind people keep using this; word needs to get out about how superior Telegram is.
     
  10. GreyOS thread starter macrumors 68030

    GreyOS

    Joined:
    Apr 12, 2012
    #11
    .

    Thanks but a central thread through my posts is regarding how it is possible on Windows Phone but not iOS. I know Android can do this, as I stated in my first post:

    "Now, this is easier on Android, where WhatsApp can run a background service so it's constantly connected to the WhatsApp servers. It can receive and forward messages at any time. But on iOS, WhatsApp can't run in the background. This is probably the initial problem, but again, I thought it would be the same problem on Windows Phone?"
     
  11. pacorob macrumors 68000

    pacorob

    Joined:
    Apr 8, 2010
    Location:
    the Netherlands
    #12
    I agree but in e.g. the Netherlands the majority of users stays with WhatsApp because they know it and everyone uses it. I would also like to use to Telegram but the majority of my friends/family keep using WhatsApp.
     
  12. peter08po macrumors member

    Joined:
    Nov 13, 2013
    #13
    I don't think it's due to platform restriction.

    Look at WeChat, another popular app which functions similar with Whatsapp.

    https://web.wechat.com/

    Its web edition provides the same thing as the new Whatsapp web: scan the QR code in app and you are logged-in from desktop's browser. More importantly, it supports iOS!!

    And if WeChat could do it, why couldn't Whatsapp?

    Why an update of Whatsapp in iOS always take a decade to go?

    It's simple - they never take care of iOS users.:mad:
     
  13. Sirious macrumors 65816

    Sirious

    Joined:
    Jan 2, 2013
    Location:
    United Kingdom
    #14
    You know, I often think that's in the works. It seems natural for Apple to do that using Apple ID and whatnot.

    But then again, who is not carrying their iPhone, iPad or MacBook with them, and not natively iMessaging from one of those devices instead?
     

Share This Page