The first version of a mobile app usually gets the happy path right. Open it. See something clear. Tap through. The drop-off we keep finding is less dramatic. It happens the second time someone tries to get back in.
They booked a room, applied for a shift, or started an assessment for their child. Then the app asks them to sign in again. The code goes to an email they do not check on that phone. Or the password rules are stricter than their bank. Or the session died while they were on a call. They do not file a bug report. They finish on a website, or they phone someone.
We treat that second visit as the real product. The first one is a tour.
The person is usually standing up
Booking apps, workforce apps, and care apps share a setting. The person is often in a hurry, with one hand free, on a connection that is only mostly there. Every extra field is a reason to stop. So is every message that sounds like it was written for a developer.
What tends to help is plain:
- Stay signed in on a personal phone, and say so. People forgive a logout on a shared tablet. They do not forgive it on the device in their pocket.
- Send the code by SMS or WhatsApp when email is the slow path. Use the channel they already use with you.
- Let them finish the job they came for before you ask for a photo, a company name, and three preferences.
- If something fails, say what to do next in one sentence. “Try the code again” is kinder than an error number.
How we check it
We delete the app, install it again, and try to complete yesterday’s task on a mid-range Android phone. If we can, we do it somewhere the signal is patchy. If we get stuck, a guest will too.
Polish still has a place. Type, spacing, the way a card moves. None of it brings back a person who could not reach their own booking. Get them back in first. Then make it feel considered.