Skip to content

Use case — native mobile app

Build a reminder app that notifies the way you need it to

Reminders are the one thing a web app structurally cannot do: a notification has to arrive on a locked phone, and a browser tab cannot deliver that. So every "every third day at 8pm, and again in twenty minutes if I do not confirm" rule ends up as a calendar entry that does not work like that. A native app can, and Vibely builds native — expo-notifications, real local scheduling, on a React Native app on your own phone.

  • Real React Native and Expo — native navigation and native components, not a web view
  • Local push scheduling through expo-notifications
  • Fires offline — no server, no subscription
  • History kept on the device
  • Scan a QR code and run it on your own phone through Expo Go while you build
  • Cloud builds through EAS reach TestFlight and Play internal testing

Start with this prompt

Paste it in and edit the details to match your own. Being specific about the screens and the data is what separates a working app from a mockup.

Build a native mobile app for medication reminders.

Home: today’s doses in time order, each with the medication name, the dose, the time, and a Taken button. Anything overdue is highlighted.

Add a medication: name, dose, and a schedule — daily, specific weekdays, or every N days — with one or more times a day.

Notifications: schedule a local notification for each dose. Tapping it opens the app on today. If a dose is not confirmed within thirty minutes, notify once more.

History: a calendar view of confirmed and missed doses for the last month.

Store everything on the device so it works offline, and keep the reminders scheduled after a restart.

Seed two medications with a week of history.

What to build next

  • Add a weekly adherence summary I can screenshot for an appointment.
  • Add a refill reminder when the remaining count gets low.
  • Connect Supabase so a carer can see the log on their own phone.

Native mobile app

What the build actually consists of

For anyone whose reminder rule is slightly unusual — medication with a confirm, plant watering by species, recurring admin, a supplement schedule. This is also the clearest demonstration of why native matters, which makes it a good first build.

01

Rules more flexible than a calendar

Daily, every N days, specific weekdays, several times a day, with a window and a snooze. The rule is data, so changing it is a sentence rather than deleting and re-creating an event.

02

Real notifications

expo-notifications schedules on the device, so reminders fire on a locked phone without a server, without a subscription, and without an internet connection.

03

A log, so it counts

Confirming a reminder writes a record to device storage, giving you a history — which is what turns "I think I took it" into something you can actually check.

What you get

  • Reminders with recurring rules that fit how you actually think
  • Notifications on the lock screen, with confirm and snooze
  • A log of what was confirmed and when
  • Editing and pausing without losing the history
  • An app you can run on your own phone the same session

Describe it. Watch it build.

Paste the prompt above and scan the QR code when the build lands — the app runs on your own phone while you are still changing it. The free plan needs no card.

Start building

FAQ

Questions, answered.

Do the notifications work if the phone is offline?+

Yes. These are local notifications scheduled on the device by expo-notifications, so they fire without a network connection and without any server of ours being up.

Why can a website not do this?+

Web push is limited, inconsistent across browsers, and on iOS requires the site to have been added to the home screen with permissions granted — it is not something to build a medication schedule on. A native app schedules on the operating system, which is the difference between a reminder and a hope.

Is this suitable for something medically important?+

Treat it as a personal tool, not a medical device. It schedules and logs reliably, but we make no clinical claims about it and you should not present one to anyone else as though we do.