When the user enters into the Offline mode , Whats app is automatically trying to reconnect and get back online.
It is showing information about it in the uper menu. It looks confusing because the user intentionally entered the Offline mode but still Whats app tries to reconnect him. But the user is not interested in reconnecting and going online.
Could this be somehow set up that way that Whats app will not try to reconnect the user ? (guess not ?) If not,
We could try to "hide" the confusing tab which is informing us about Whats app reconnecting.
We could cover this with an another image-icon for example some kind of Zen Mode icon which could cover the whole field where the message about Whats app trying to reconnect is located.
That way the user will not see the information about Whats app trying to reconnect and he will not be confused why this is happenning and why Whats app is trying to reconnect him when he intentionally choosed to enter the offline mode.
When the user enters into the Offline mode , Whats app is automatically trying to reconnect and get back online.
It is showing information about it in the uper menu. It looks confusing because the user intentionally entered the Offline mode but still Whats app tries to reconnect him. But the user is not interested in reconnecting and going online.
Could this be somehow set up that way that Whats app will not try to reconnect the user ? (guess not ?) If not,
We could try to "hide" the confusing tab which is informing us about Whats app reconnecting.
We could cover this with an another image-icon for example some kind of Zen Mode icon which could cover the whole field where the message about Whats app trying to reconnect is located.
That way the user will not see the information about Whats app trying to reconnect and he will not be confused why this is happenning and why Whats app is trying to reconnect him when he intentionally choosed to enter the offline mode.
BEFORE:![offlinemode](https://user-images.githubusercontent.com/105730382/169538957-43c785f2-0248-4f03-8f0e-03057df2df2a.JPG)
AFTER: