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.
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.