2-minute setup — designing for the kid, not the parent

The most common failure mode for eldercare technology is expecting the elderly person to set it up themselves.

Every product in this space thinks about the parent as the user. The landing page talks to the parent. The sign-up flow is for the parent. The app asks the parent to create an account, choose a password, configure their preferences. The parent, who was skeptical to begin with, encounters this and gives up. The adult child, who wanted to help, feels guilty for suggesting it.

FamAI inverts this. The buyer and the user are different people, and we designed for that explicitly.

The buyer ≠ user insight

The person who discovers FamAI, evaluates it, and decides to set it up is almost always the adult child — a 30-45-year-old who lives far from their parents, worries about them, and wants to do something about it. They're comfortable with technology, they read this blog, they can handle a 5-minute setup process.

The person who uses FamAI every day is the parent — someone who may be 65, who finds new apps confusing, who doesn't want to deal with passwords, and who will stop using something the moment it feels complicated.

These are two completely different users with two completely different needs. We tried to satisfy both at the same time for a while. It didn't work. Eventually we committed: design the setup for the kid, design the daily experience for the parent.

Setup on the kid's device

The setup form — entering the parent's name, phone number, medicine schedule, language preference — is done by the adult child on their own device. They don't need to be on the same call as the parent. They don't need the parent's phone in hand. They sit down, fill in the information they already know, and it takes about two minutes.

Once that's done, the parent gets a contact to save in their phone. That's their only action: save the contact. Everything else FamAI does happens through that contact — on WhatsApp, which the parent already uses every day.

Onboarding as conversation

When the parent messages FamAI for the first time — "Hi" or "hello" or just a voice note — FamAI introduces itself in Hindi. Not a welcome screen. Not a tutorial. A conversation.

"Namaste! Main FamAI hoon — aapka WhatsApp pe assistant. Aap mujhse kuch bhi pooch sakte hain — dawai ka reminder, health tracking, koi bhi cheez check karni ho. Aapka naam kya hai?"

The parent responds with their name. FamAI remembers it. The conversation has started. There's no "settings" to configure, no "tutorial" to skip, no "get started" button to press. The onboarding is the first conversation — and the first conversation is useful.

Why we removed the login flow for parents

Early versions of FamAI asked parents to create an account with a phone number and OTP. This created an immediate problem: many parents don't receive OTPs reliably (SIM issues, forgetting to check SMS), don't understand what an OTP is for, or are scared to enter one because they've been warned about OTP scams.

We removed it. The parent authenticates simply by messaging from their registered WhatsApp number — the number the kid entered during setup. No OTP, no password, no account creation on their end. Their identity is their phone number, and the matching is done in the background.

This is less secure in some abstract sense. In practice, it's far more secure: no password to lose, no OTP to accidentally share with a scammer, no friction that makes the parent give up and call their kid for help setting up the safety tool.