When something goes wrong, most apps try to recover without interrupting what you’re doing. I looked at Slack, Uber, and Wells Fargo to see how they respond to common failures.
In Slack, I turned off WiFi and tried to send a message. Nothing happened right away. The text stayed in the input field, and there was no error. After a moment, a short line appeared under the box: “Slack is trying to connect.” It didn’t clear the message or open a modal. I also tried mentioning someone who wasn’t in a private channel. Slackbot posted a message in the chat explaining the issue and gave me two options: add them or do nothing. Both cases stayed within the flow of conversation. The interface handled it quietly and gave me a way to fix it.
On Uber, I left a ride request screen open and came back to it later. The pricing and map updated without needing to refresh. I also tried using a debit card with a $1 spending limit to book a ride. The app told me the card didn’t work and kept me in the selection screen. A button for switching payment methods was already built in, so the next step was clear. The ride request flow stayed intact, and the app treated the failed payment like a minor adjustment, not a full reset.
In the Wells Fargo app, I turned off internet access while viewing my account. Nothing loaded, not even the last known balance. The app wouldn’t show anything until I reconnected. I also tried logging in with the wrong password. The response was a single sentence saying the combination didn’t match, with links to reset or recover the login. The app didn’t explain more than it needed to, and when it wasn’t sure if it had the right information, it didn’t try to guess.
