Case study
Why some of your app's notifications never reach anyone
A morning summary that never arrived, and a customer who heard nothing at all. Two gaps in our own app, both caused by a message with nowhere to land, and what we changed.
Topic
Apps for customers and staff, from the first release to every update.
Case study
A morning summary that never arrived, and a customer who heard nothing at all. Two gaps in our own app, both caused by a message with nowhere to land, and what we changed.
Case study
Our team app's waiting list filled with red rows for conversations that needed nothing. We added a way to close a chat without writing in it, and made the wait restart from the customer's next message.
Case study
Our own team app opened on charts, not on the customers waiting for a reply. We rebuilt the first screen around who is waiting and for how long; reaching a customer's chat is a tap or two in the reworked version, against four or five moves before.
Case study
Our own iPhone app was turned down over two App Store rules on personal data. The consent question was too general: it named no AI provider, covered one feature out of three, and came later than the reviewer looked.
Case study
Our own Android app is updated almost every day, and the people using it said it lagged. The cause was not one heavy screen but repeated work, a phone relearning the app after each release, and a demo that crashed only on real phones.
Case study
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.
From Tech Concierge
Your own engineer builds and runs the website, the app, the CRM and the AI assistant that answers your customers.
The first 7 days are free.
We count visits to this blog with our own analytics, never Google's, and share what you read with nobody. May we remember this browser with a cookie? See the privacy policy.