I only had some (for me) unexpected behavior with Push Notifications and message time-outs:
Sending one message
When I sent ONE Lync message to a mobile user, the user received a push notification correctly. Lync client on the desktop states “waiting for a response”.
After some time, when the mobile user does not open Lync Mobile app on the phone, the “waiting for a response” goes away and I receive the following message:
Sending Multiple Messages
When I sent multiple subsequent message to the mobile user, Lync client on the desktop states “waiting for a
response” and shows a twirling circle next to the second and subsequent messages.
Just as with one message, after some time and the mobile user does not open Lync Mobile app on the phone, you receive the following message:
On the mobile client
– A push notification is only received for the first message when subsequent are sent
– When opening Lync Mobile, only the first message (received with the push notification) is shown in the history
After some research I verified that this is expected behavior, and wanted to create a blog posting since this behavior is not documented in the Mobility Guide.
I understand why Microsoft took this approach as mobile clients often have unreliable network reach/connections and it is very well possible that a message does not get delivered (on time). The message also states that it may not have been received.
I’m not so sure about the implementation though, as I would expect :
- the client to give no feedback at all when the push message is successfully sent to the end-user device, but the user does not open Lync on time on the phone.
- a warning/error message when the push message was indeed not delivered at all
With the current implementation, I wouldn’t use the regular error-message layout for these messages as it might confuse users. A better solution would be an informational message like “this user is mobile, successful and timed delivery is dependent on networking conditions and phone reception” on the information bar (example screenshot below) in the conversation history.
I cannot find any reference why this is implemented like this, it might very well be a limitation of the push notification services of either Apple or Microsoft (or both).
Considering all this, I think the error message on the desktop client may confuse some users and I thought it was worth sharing.