Case study
Why people give up writing in your app's chat
When a chat in your app feels awkward or unreliable, people stop using it. Here’s what we learned fixing these problems in our own apps, and what you can check yourself.
Key takeaways
- Unreliable chat features quietly drive people away from your app.
- The chat box should clear instantly when you tap Send, not after the server replies.
- Failed messages must stay visible with clear options to retry, edit, or remove.
- A chat should always open on the newest message first.
- You can check these issues yourself before asking a developer to help.
When a chat in your app feels unreliable—messages stick in the box, replies vanish, or the latest message is hidden—people quietly stop using it. These issues don’t show up as errors, but they can make your business seem unresponsive and cause people to write less over time.
What a chat that half-works does to a business
A chat that does not behave as people expect makes them give up before they ever see an error. If the text box does not clear after tapping Send, people may send the same message twice or wonder if their words ever left. When a chat thread opens in the middle of an old conversation, the person can miss new replies and feel ignored. If a failed reply quietly disappears, it looks as if nobody is listening. None of these issues trigger alerts or error reports—they simply lead people to stop writing, often without saying why.
The complaints our own apps kept getting
We saw these problems in our own mobile apps, which have chat features for clients and staff. People found that after tapping Send, their words often stayed in the box, so they sent the message again. Some chats would open on an old message, forcing the person to scroll down every time. Sending a second message was not possible until the first one finished. If a reply failed, it quietly came back into the box, with no sign of what went wrong. Leaving the chat while a message was still sending could lose it entirely. On iPhones with the latest system, the app sometimes froze mid-reply and closed itself twice in a row.
How the freeze led to the everyday failures
We started by tracing the freeze on iPhones, since the phone’s own reports showed the app stopped responding while its screen kept trying to recalculate its layout. The chat’s text box shared the cursor’s position with the rest of the app, but on the newest iPhone system, the box could report positions that did not exist, causing a loop where both kept trying to fix each other. Solving that revealed the deeper pattern: every chat screen waited for the server before showing any change. The box only emptied after the server replied, and the entire chat thread was redrawn after each check for new messages, which threw the reader to the top. If someone left the chat mid-send, the message was dropped. A second message could not go out until the first finished, and sending the same short word twice (like “ok”) meant a failed second message was ignored. Reading older messages could also bump the person back to the top of the chat.
The rule we rebuilt every chat around
We rebuilt every chat in our apps with one rule: show the person’s action right away, and let the network catch up behind the scenes. Now, tapping Send empties the box instantly and adds the message to the thread straight away. Messages go out in order, each with its own label, so retrying cannot send the same one twice. If a message is not delivered, it stays in the thread in red with options like Try again, Edit, or Remove—never quietly disappearing or jumping back into the box. Messages keep sending even if the person leaves the chat or switches tabs, and an unsent message is saved on the device. Each chat thread opens on its newest message, and if someone has scrolled up, they stay where they are, with a button showing new messages. On iPhones, we built a custom text box that only tracks its own words and keeps its own size, so it cannot freeze the app again.
Where these changes stand
Every chat screen in both our iPhone and Android apps has been rebuilt following these rules. These changes are in the next versions of the apps: they will reach everyone once the new iPhone version is approved for the App Store, and the new Android version is live on Google Play. On our test phones, the chat box clears the instant you tap Send, every chat opens on its newest message, failed replies wait in red with options, and even the reply that once froze the app now types smoothly.
What you can check yourself
- Send a message on a slow connection and see if the box clears right away.
- Open a chat with a long history and check if it opens on the newest message.
- Turn on airplane mode, send a reply, and look for a clear sign that the message was not sent, with a way to try again.
- Send a message, leave the chat immediately, then come back and check if the message arrived.
- Type a long reply, making corrections and adding an emoji, on a phone with the latest system to see if the app keeps up smoothly.
What to do next
If your app’s chat feels slow, loses replies, or opens in the wrong place, these are not just minor annoyances—they cost you trust. Try the checks above. If you see any of these failures, ask your app’s developer to review how chat messages are handled and whether actions are shown instantly, not just after the server replies. This kind of work—finding and fixing invisible failures in chat or comment features—is something Tech Concierge engineers handle for clients’ apps and sites.
Questions people ask
Why does my app's chat box stay full after I tap Send?
If the chat box stays full after you tap Send, users see their words sitting there and may send the message again. This usually means the app is not updating the box until it hears back from the server, which feels slow and confusing.
Why does the chat open on old messages instead of the latest one?
If your chat opens somewhere in the past, it may be redrawing the whole conversation or not remembering where you last were. This forces users to scroll and can cause them to miss new replies.
What should happen when a message fails to send in an app?
A failed message should stay visible in the chat thread, marked clearly (such as in red), with options to try again, edit, or remove it. It should not disappear or quietly return to the text box.
Why does my app freeze when I type a long reply on a new iPhone?
Some apps have text boxes that do not work smoothly with the latest iPhone systems, especially if they share cursor or layout information in ways that are no longer supported. This can cause endless recalculations and make the app freeze.
Can a message be sent twice if the first one was slow?
If the app does not handle retries properly, sending a message again while the first is still pending can result in duplicate messages or failed messages that go unnoticed. Messages should be labelled so they can be retried safely without duplication.