← SharkDreams Labs · home
A product story · 2015 → 2020

It started at the bedside:
make medication adherence measurable.

The research, the device, the sensor, the app, and the platform — how a smart pillbox lid grew into a connected health-tech system. The founding engineering years.

SharkDreams and LIVIT brand marks
SharkDreams & LIVIT — the original brand marks.

Every chapter below is a real thing that got researched, designed, and built between 2015 and 2020. One idea runs through all of it: most avoidable health cost comes from people not taking their medication — so make adherence visible, and put the right person in the loop the moment it slips. The innovation was the delivery of information, not the medicine.

Chapter 1 · The idea

2015 – 2016

The smart pillbox lid

SharkDreams' founding invention
Smart pillbox lid linking to phone, family, caregiver
The founding concept — a smart lid that links the patient to phone, family, and caregiver.

It began with a simple, stubborn problem at the bedside: did the patient actually take the dose, on time? The answer was a sensor-equipped pillbox lid that could tell — and quietly notify a family member, pharmacist, or clinician when something was off.

  • Notifies patient, family, and clinician about medication habits.
  • Counts pills and can auto-reorder; flags missed or mistimed doses.
  • Senses heat/cold exposure and tampering; fingerprint-locked.
  • Measures basic body factors (heart rate, temperature).

Chapter 2 · Prototype & the printed sensor

2015 – 2017

From sketch to working sensor · patents & design files

Real engineering: prototypes, a provisional patent, NDAs, and a design build

The idea was carried into hardware — a printed-sensor architecture (SDX) small and cheap enough to sit on any medication container, with a ~40-day battery, unique device ID, and weight-change sensing to count pills. The work was documented the right way: a provisional patent filing, signed NDAs with development partners, and a contracted UI/design engagement.

  • Printed sensor for universal medication containers.
  • Weight-change sensing → pill count to phone + base station.
  • Device activation, unique ID, critical-battery and sensor-error alerts.
SDX printed-sensor feature set
SDX — the printed-sensor concept and its feature set.
Smart pillbox lid capabilities and technical detail
The device spec — what it does, the sensor stack, and manufacturing flexibility.

Chapter 3 · LIVIT, the companion

2016 – 2017

LIVIT — the app the device talked to

The patient/family-facing interface

Hardware needs a face. LIVIT was the companion app — the layer that turned sensor data into something a patient, a family member, or a pharmacist could actually see and act on. It carried the product idea from planning through prototype, client demos, and into production design across 2016–2017.

LIVIT development timeline 2016-2017
LIVIT's development arc — planning, patents, prototype, client demos, production design.

Chapter 4 · The data loop

2017

Sensor → storage → the right person

The notification engine that made it useful
Workflow: lid open, sensor activated, pill taken check, data storage, transmitter, notifications to patient, pharmacist, caregiver
The core loop: detect the event, store it, route an alert to patient, pharmacist, or caregiver.

The value wasn't the sensor alone — it was the loop. Was the lid opened? Was the dose taken? If not, the event flows to storage, through the transmitter, and out as a notification to the person who can act: the patient, the pharmacist, or the caregiver. This closed loop is the reusable heart of the whole system.

Chapter 5 · From a device to a platform

2017 – 2020

Adherence → engagement → monitoring

One device became a stack

Each capability revealed the next one it needed, and the product grew into a platform:

Chapter 6 · The proof

2017 – 2021

Real customers, real deployment

B2B, into the specialty-pharmacy supply chain

This wasn't a slide deck — two specialty pharmacies put LIVIT in front of real patients:

A second pharmacy coming online in 2018 is exactly why that year's work was Software Version 1 plus servers, HIPAA, and healthcare security. The deployments serve a largely Medicare-eligible population — the group where adherence matters most — and are the evidence behind every concept above.

Chapter 7 · The PerformRx collaboration

2017 – 2019

A real pharmacy partner — teams, process, and a business model to build against

PerformRx / PerformSpecialty · specialty pharmacy

PerformRx didn't just sign a pilot — they opened the door to work alongside their teams, their processes, and their business model. That access turned a good idea into an engineered product: it grounded the work in how compliance and adherence actually fail in a pharmacy, drove a hardware design built to prove the mechanics, and then expanded into software that surfaces what the hardware sees in a meaningful way — so a pharmacist can reach the exact patient who has an adherence problem, at the moment it matters.

The arc: understand compliance & adherence → design hardware to prove the mechanics → build software that turns hardware signals into pharmacist-ready actions.

The build roadmap · 2017 Q1 → 2019 Q3

2017 · From problem to working device
Q1
Define the problem & the possible hardware design.
Q2
Design the prototype.
Q3
Hardware + basic software.
Q4
Software design.
2018 · From device to platform
Q1 – Q2
Software Version 1.
Q3 – Q4
Servers, HIPAA, healthcare security & infrastructure.
2019 · From platform to the floor
Q1 – Q3
Multiple refinements, mini-trials, and pharmacy-staff training.
→ toward deployment
Proven mechanics, secured platform, trained staff.

Where it points

The same idea, ready for senior care

Everything built between 2015 and 2020 — the adherence sensor, the companion app, the notification loop, the monitoring stack — points naturally at one place: keeping older adults safe and connected to their families and caregivers. That is the thread carried forward today into U.S. senior care, where the device-and-data idea becomes a consumer-facing service rather than a B2B component.

For completeness: SharkDreams, Inc. later became the subject of an SEC matter, with a final judgment entered in March 2025 (E.D.N.C., Case 5:23-cv-00503). The current operating ventures are separate entities. Full record at sec.gov.