Find a tappable, tap, watch the animation, and get the message "Uh-Oh" the network is unavailable. When this happens, it looks like the rewards are lost. But the game knows we clicked on an object, it's doing the animation, and it should know what whatever was in there was already earned.
Please ensure that in this condition that rewards are not lost.
We shouldn't see "Uh-Oh" unless something really critical prevents the app from continuing. If that's the case, don't dump us back on the map as if everything is fine. Don't let us walk into failure. If the connection is lost, tell us, not with a modal button but with a small icon. Then we'll know the connection is down and actions will be ignored.
Or, depending on the context, don't show anything. There's nothing in the map that really requires a network connection when it comes to random tappables. That will change with more live interactions. Why aren't those operations done on the client side and then communicated back to the server?
I'm confused about why intermittent network errors are even visible in the UI of a modern mobile app. The app should be resilient to handle that kind of instability behind the scenes. But when MCE seems stalled, I can easily jump to other network apps and I get data, so something in MCE is more sensitive than in other apps.
In summary, this is a request to simply (Ha!) handle this "Uh-Oh" condition better.
Thanks.
Please sign in to leave a comment.
4 Comments