Lesson 1: Most "senior-friendly" apps aren't.
When I started researching health apps for my grandmother, I downloaded 15 of them. Almost all had the same problem: tiny text, complex navigation, and notifications that disappeared after 3 seconds.
My grandmother has arthritis and isn't interested in learning a new interface every month. The first thing I built for Zellia was a UI with buttons large enough that she could tap them without reading glasses — not as an afterthought, but as the foundation.
If you're building for older adults, test on an actual older adult, not on yourself. What feels "big enough" to you is probably too small.
Lesson 2: Medication adherence isn't a UI problem — it's a social one.
I initially thought the hard part was getting the reminder timing right. It wasn't. The hard part was that my mom (primary caregiver) lives 30 minutes away, my aunt checks in on weekends, and neither knew whether my grandmother had actually taken her morning meds.
What ended up mattering most was the family collaboration feature — not because it's technically impressive, but because it solved a trust problem. Now my mom gets a notification when my grandmother logs her meds. No phone calls needed.
The best health feature is often the one that reduces family anxiety.
Lesson 3: Doctors don't want more data — they want a summary.
I spent weeks building beautiful charts. When my grandmother finally visited her doctor, I proudly handed over the iPad showing months of blood pressure trends. The doctor glanced at it for 3 seconds and said, "Can you print me one page with the weekly averages?"
That's when I built the PDF report feature. A single page. Medication adherence, BP trends, glucose readings. Designed to be read in under 10 seconds. The doctor loved it.
The lesson: more data is noise. Better context is signal.
Lesson 4: Compliance is harder than code.
Building a health app means navigating medical device regulations, even when you're just a tracking tool. I spent almost as much time on Play Store compliance documentation as I did on the actual app.
The key distinction that took me weeks to fully understand: a lifestyle tracking tool that helps you log readings and set reminders is fine. A tool that claims to "manage" or "improve" your health crosses into medical device territory.
Stay on the right side of that line. My simple rule: describe what the app does (reminds, logs, summarizes), not what it achieves (improves, prevents, treats).
Lesson 5: Start with one pain point, not a platform.
My original plan was ambitious: medication + vitals + appointments + insurance + telehealth + AI predictions. I'm glad I didn't build any of that.
I shipped with just medication reminders and BP logging. That was enough to be useful. Everything else (glucose logging, PDF reports, caregiver collaboration) came from actual user requests — not from my assumptions.
The most valuable feedback I've gotten so far: "Can you make the font even bigger?"
I wrote about this while building Zellia, an Android app for family health and care. It's a lifestyle tracking tool for medication reminders, vitals logging, and caregiver coordination — not a medical device.
Back to blog