Andrei Lukoits
All work
  • Product design
  • B2C SaaS
  • Web dashboard
  • Mobile app

CareBridge

Product design for a service that alerts family when an elderly parent's phone goes quiet. Split it into a caregiver web dashboard and a parent Android app, and designed both, plus onboarding, billing, the landing and the rules for an AI-written blog.

Platforms
Web, Android
Status
Live since June 2026
Role
Product design: web dashboard, Android app, landing, blog rules

Web for the family, app for the parent

The final user path: automated blog, landing, sign in, onboarding, Stripe, then the device card waiting for the app. Cancelling Stripe makes the card inactive and leads back to payment; deleting the card leaves an empty dashboard that leads back to adding a device; the card shows the code for the parent's phone, and the trial starts once that phone is active. Settings hold billing, time format, account deletion, privacy and support

Analysed competitors' reviews on Google Play and the App Store. The common problem: similar services live entirely on the elderly person's phone, so the family adds payment on that device and afterwards cannot see whether monitoring works at all.

Split the product in two. The relative who decided the service is needed gets a web dashboard with the subscription, the settings and the alerts. The parent gets a free Android app with one task: type a code once. The split set everything after it: questions go to the caregiver, payment stays on the web, the trial waits for the parent's phone.

Mapped the whole path in FigJam, from the ad to a working dashboard, with every branch: app not installed, not paid, device inactive, account deleted. Added a silent ping for when the phone stops checking in: the family is alerted only if it does not answer within 10 minutes, so an app that merely went quiet does not set off a false alarm.

Landing: three steps, no surveillance

The landing: the top of the page with the “Are you sure your mom is OK?” hero photo, how it works, three steps and what the app does; and its end with the FAQ, the final call to action and the footer

Started from an AI-generated draft and reworked it in Figma over 4 full-width directions. Removed the stats bar, the comparison, the feature cards and the pricing table. The page now shows how little it takes: sign up in about a minute, install on the parent's phone in about five, and that's it.

In competitors' reviews, parents often refused monitoring apps because they felt watched. So the landing has a separate block on what the app reads and what it never touches: location, camera, microphone, messages. The hero says “Android only”, so iPhone users don't sign up by mistake.

Questions to the caregiver, not the parent

Three onboarding steps the caregiver answers: about your loved one, quiet hours with the alert threshold slider, and optional questions about phone use and concerns

Put every question to the caregiver, who knows the answers and wants to give them, never to the parent. Designed three steps between Google sign-in and the saved card: relationship, sleep hours and alert threshold, optional routine questions.

Replaced the sleep-time text fields with hourly dropdowns. The alert threshold is a slider with a recommendation: 6–8 hours. The caregiver's own email becomes trusted contact 1 of 4, marked “(you)”. Onboarding resumes where it was left.

The trial waits for the parent

The dashboard waiting for activation: two steps, activation code 9412, Emma's device marked not connected, and notes that the 7-day free trial begins once the device is activated. Next to it, the parent's phone with the same code entered and a Connect button

Moved the card into the last onboarding step, saved without a charge, and started the 7-day trial at the parent's first connection instead of at sign-up, so nobody pays for days spent installing. The dashboard says it in one line: the trial begins once the device connects.

Kept monitoring on while a payment is past due: a safety product should not go silent over billing. Cancelling the subscription and deleting the account both sit in Settings, each behind a single confirmation.

Set up in one step

Five parent app screens: the intro with Start and the terms, entering activation code 9412, the permissions warning, monitoring active, and the stop monitoring dialog with Keep monitoring as the main button

Put an “I agree” after the 4-digit code and started monitoring only on that tap, so nothing runs on the phone before the parent consents. The only system prompt, for notifications, appears after that tap; from then on the app is one status screen, active or paused.

Made stopping monitoring ask for confirmation and say what the family loses: activity updates and alerts.

The dashboard

Put the answer in the device card at the top: online status, sleep schedule, inactivity limit. Moved the explanation into the activity log below it. Cut the “disconnected” status, which overlapped with “offline”, and merged repeated events of the same type within 2 minutes into one.

Hid sleep events from the log at first, then brought them back as markers such as “Night mode started”. Designed every empty and in-between state: no device yet, waiting for activation with the code and two numbered steps, device inactive.

Rules for an AI-written blog

Blog self-check output on the latest article: 35 checks, 0 failing, 5 needing a line in the pull request

An AI agent writes two articles a week. The first 13 came out as copies of one template: 281 em dashes and 2 outbound links across 19,331 words. Rewrote the rules it writes against as 34 countable checks that a script runs on every draft: sourcing, repetition, links, length. Review takes about two minutes per article.

Google Search Console, August to November 2026: daily impressions climb from zero to about 400; 12.6K impressions and 102 clicks in total

Daily search impressions grew from zero in August to about 400 in November, and the traffic started bringing in the first paying customers.

Launched in June 2026

Published on Google Play and opened to the public at carebridge.family in June 2026. Search traffic from the blog started bringing in the first paying customers.

Next project

Capable