Ripple's future

Product roadmap

Ripple today handles custom intervals beautifully. Here's where we're headed — starting with smarter medication reminders (v2) and shared coordination for families and teams (v3). Nothing here is a promise or ship date; it's our direction, shaped by users like you.

v2 · Multi-Time Alarms v2 · Retry Until Dismissed v3 · Shared Alarms

Version 2

Medication seriousness

Multi-time alarms and retry-until-dismissed — built for the audience that depends on Ripple most.

9:41

💊

Blood pressure medication

↻ Every 1 day

✓

8:00 AM

Morning

✓

12:30 PM

Lunch

7:00 PM

Dinner

+ Add another timePro

One alarm · three ring times

💊

v2 candidatev2

Multi-Time Alarms

One task, multiple ring times

Blood pressure medication

8:00 AM · 12:30 PM · 7:00 PM

↻ Every 1 day

Stop creating three separate alarms for morning, lunch, and dinner. One label, one interval — multiple ring times.

Example

"Blood pressure medication" — every 1 day — rings at 8:00 AM, 12:30 PM, and 7:00 PM. One alarm slot, not three.

Pause once — all times pause together
Skip next ring or skip all of today's rings
Each ring logged individually in History
Full-screen takeover & snooze unchanged

Pro (proposed)

Multiple times per alarm is planned as a Pro feature. Free users keep one ring time per alarm; a multi-time alarm still counts as one alarm toward the free limit.

The problem today

Right now, one alarm means one ring time. Medication three times a day means three separate alarms — burning free slots and tripling pause, skip, and edit work.

Uses all 3 free alarm slots on a single prescription
Pause, skip, and edit must be done three times
"My blood pressure meds" is one thing — not three alarms

What we're building

An alarm can hold multiple ring times under a single label, category, and interval. Create/Edit screens get a “+ add another time” flow; widgets and next-ring countdown pick the soonest of all times.

Why it matters

Medication is our #1 use case — and the insight matches what users and competitors like Repeatly are asking for: one smart alarm instead of many.

9:41

Morning medication

Re-rings in 10:00 if not dismissed

7:00 AM — rang

7:10 AM — rang

7:20 AM — ringing now

Retry until dismissed

🔁

v2 candidatev2

Retry Until Dismissed

Optional re-ring every N minutes

Morning medication

Re-rings every 10 min

↻ Until dismissed

Optional re-ring every 10 minutes until you dismiss — so a missed tap doesn't mean a missed dose.

Configurable retry interval (e.g. every 10 minutes)
Pairs with Multi-Time Alarms for medication seriousness
Converts “set and forget” into “won't let you forget”

The idea

Instead of auto-missing after 5 minutes, an alarm can optionally re-ring on a schedule until you explicitly dismiss it — built for medication and shift-wake use cases where missing once isn't acceptable.

Why it's in v2

Together with Multi-Time Alarms, retry-until-dismissed forms a “medication seriousness” bundle — the features that make Ripple's strongest promise legitimately usable for people who depend on reminders.

Version 3

Shared coordination

Ripple Groups — remind the people you care about, with their explicit consent every step of the way.

9:41

Alarm request

👩

From Mom

Family group

Take your medication

↻ Every day · 8:00 PM

💬 “Please take this after dinner.”

Nothing is scheduled until you accept

Shared alarm request

👥

Future visionv3

Shared Alarms

Ripple Groups — remind together, stay in control

Take medication · from Mom

8:00 PM daily

↻ Shared request

Send alarm requests to family, caregivers, or teammates — they accept before anything is scheduled on their phone.

Example

A mother sends her son: "Take your medication at 8:00 PM every day" with a note — "Please take this after dinner." He accepts, and it behaves like a normal Ripple alarm on his device.

Private groups: Family, Caregiving, Work Team, Household
Email invites — accept membership before joining
Every shared alarm requires accept or decline
Optional “I've taken it” separate from dismiss

The vision

Ripple becomes a trusted coordination tool — not just a personal interval alarm. People can remind and support one another while recipients stay fully in control.

Privacy first

An alarm is never added silently. Recipients always see who sent it, the title, schedule, and an optional message — then choose Accept or Decline.

Approve or decline every shared alarm
Allow automatic alarms only from trusted members
Mute a member, leave a group, or remove a shared alarm
Control whether completion status is shared

Status you can trust

For medication, dismissing doesn't automatically mean the medicine was taken. A separate “Mark as completed” action makes status meaningful — invitation pending, accepted, declined, scheduled, acknowledged, completed.

Planned MVP

The first version focuses on essentials before admin roles, dashboards, or team subscriptions.

Group creation and email invitations
Accept or decline membership
Send an alarm to one or more members
Accept or decline each alarm request
Schedule accepted alarms locally on the recipient's device
Optional description or personal message
Basic accepted, declined, and completed statuses

Have ideas for what Ripple should build next? We'd love to hear from you — especially if you use Ripple for medication, caregiving, or team coordination.

Get in touch