Why your parent's screen in Marlow has no buttons that matter

Every caregiving app has to decide what the person being cared for sees. Many decide they are a user like any other, hand them a login, and trust a large font to make it manageable. Marlow decided the opposite: the parent’s side is one screen, it shows the day, and nothing on it can change the schedule.

This post is the reasoning, because it’s the decision people ask about most and it rules out a lot.

The parent is not the user. The family is.

Marlow exists because coordinating rides among siblings is hard, not because a parent can’t read a calendar. The people doing the work, adding appointments and claiming rides and changing plans, are the adult children. The parent’s job is to be ready at the right time and know who’s coming.

Once you say that plainly, most of the “senior UX” problem disappears. You don’t need a simpler version of the family app. You need a different thing: a display, not a tool.

That’s a statement about the job, not about your parent. Plenty of people in their seventies and eighties are entirely at home on a phone, and some of them will find a screen they can’t touch a little insulting. If that’s your mother, she doesn’t need the senior side, and nothing stops you inviting her into the circle like anyone else. The senior side is for the parent who shouldn’t have to operate anything, and for the family that would rather she didn’t have to.

What the screen shows

The senior side shows today and what’s next: the appointment, the time to be ready, and the name of who’s driving. The type is large by default, the surface is warm and quiet, and it’s the same information whether it’s on the phone’s screen, its lock screen, or the home screen widget.

That’s the whole interface. It doesn’t scroll into settings, it doesn’t have a menu, and it never asks a question about the schedule.

What it deliberately can’t do

• No account. There’s no email address, no password, no sign in on the parent’s phone. A family member pairs it to the circle once, by showing a code, and after that it just shows the day.
• No editing. A parent can’t move, cancel or add an appointment. If something’s wrong, or she isn’t going, she tells whoever is coming, the way she always has. The phone is still the phone.
• No decisions to make. Nothing arrives asking her to confirm a ride or answer a question. The one thing her phone does ask is whether a medicine has been taken, and a tap says yes. That’s a record for the family, not a decision about the schedule, and nothing about the schedule depends on it.
• No view of the negotiation. If nobody has claimed a ride yet, the parent’s screen says the ride is being arranged. That’s true, it is, and it’s the family’s problem to solve, not hers to worry about. Some parents would rather know, so they can make their own arrangements. If yours would, her screen won’t tell her, and you should.

Each of those is a feature we could build and have chosen not to. The rule inside Marlow is simple: if the schedule would only work when the parent does something, we don’t build it that way.

“Read only” is enforced below the app, not just hidden

Hiding buttons is not the same as removing the ability. A parent’s account is granted read access at the database, so the server refuses a change from it even if the app has a bug. Big targets and no mistakes goes through why that matters more than the size of any button.

Language is chosen per person

A parent who reads Spanish gets the screen in Spanish while her son organizes in English. Marlow speaks English, Spanish, Chinese, Hindi and French, chosen per person rather than per app. Names, addresses and anything a family member typed pass through untranslated, because those are hers.

What this rules out for us

The cost is real. This design means Marlow is not a communication channel with your parent. There’s no chat, no “on my way” button for her to press, no confirmation that she saw it. Some families want that, and there are apps that do it. We think that asking a parent to confirm she has read her own schedule is asking her to do a job so her children feel reassured, and that the reassurance should come from the ride actually happening.

It also means that a parent without a smartphone isn’t served yet. We’ve designed a text message and phone call version of the senior side. It isn’t built, and we say so on the FAQ rather than implying it. If you want to see what both halves look like, the senior side page shows them next to each other.