eldermate

Remote Care for Your Parents. Simple as a Slide.

Visit Website
April 21, 2026 Building a Zen-style Elderly Care Hub with Supabase & Realtime: How I'm Solving the 'Notification Fatigue' Problem

Hi Indie Hackers,

I’m Roc, an independent developer currently building ElderMate — a family coordination hub designed for aging parents.

Most elderly care apps on the market share a common flaw: They are noisy. Every time a vitals sensor pings or a step goal is reached, the caregiver's phone screams. Eventually, the family develops "notification fatigue," and the truly critical alerts get ignored.

For ElderMate, I decided to take a different path: Premium Zen. Here’s how I’m using Supabase and a custom T1/T2 Logic to build a system of "Silent Trust."

1. The Philosophy: Design as a Record of Decisions

In elderly care, a notification doesn't equal a solution. We’ve all swiped away a "Medicine Reminder" while in a meeting, only to forget it 5 minutes later. That's why we built the Task-Closure Engine:

  • T1 (The Trigger): A calm, local notification for the senior (via Apple Watch).

  • T2 (The Closure): A confirmation from the senior or a family member that the task is actually done.

2. The Tech Stack: Why Supabase & Realtime?

I needed a backend that could handle high-priority SOS events with zero latency while keeping daily "maintenance" tasks silent.

  • Realtime WebSocket Sync: We use Supabase Realtime to power the "Family Hub." When a senior taps "I've taken my meds" on their Zen-style interface, the status updates in the background. The family's dashboard turns "Green" instantly without a single intrusive buzz.

  • Edge Functions for SOS: For T1 emergency alerts (like heart rate anomalies), we use Supabase Edge Functions to trigger a MAX Importance push notification that bypasses silent modes.

  • Decoupled Architecture: Our logic is hardware-agnostic. By building the coordination layer in the cloud, we ensure that as sensors evolve (from Apple Watch to future wearables), the family's coordination logic remains intact.

3. Stripping Away the Noise

To achieve "Premium Zen," I had to make some hard choices:

  • No AI "Predictions": Only real-time truth.

  • No Endless Menus: Just two interfaces — one hyper-minimalist for seniors, one powerful for caregivers.

  • Silent Success: We deliberately chose not to send push notifications for routine task completions. The psychological satisfaction comes from opening the app and seeing a "Clean Dashboard," not from 50 daily vibrations.

4. What's Next?

I’m currently in the pre-launch phase on Indiegogo with 26 early followers. It’s a slow build, but I believe the "Zen" approach to caregiving is the future.

I’d love to hear from other devs: How do you handle "notification fatigue" in your products? Is "Silent Trust" a viable UX path, or do users always demand more pings?

Check out our progress here: [你的 Indiegogo 链接]

Happy to answer any questions about the Supabase setup or the Zen UI logic!

Best, Roc

1 Comment

  1. 1

    The T1/T2 split (calm trigger vs. confirmed closure) is basically the same principle I built FounderFlow around (an AI chief of staff for founders, disclosing since it's directly relevant), just applied to running a business instead of caring for a parent: don't tell me something happened, tell me only when it actually needs a decision, otherwise stay quiet. "Silent Success" is the gutsy part, most founders panic and add more notifications when users complain about missing something, when the real fix is usually fewer, better filtered ones. Have you gotten pushback yet from caregivers who want more reassurance pings even though logically they don't need them?

About

Building a Zen-style Elderly Care Hub with Supabase & Realtime: How I'm Solving the 'Notification Fatigue' Problem