Urgent.News

What's breaking now, across thousands of outlets.

Tech

Designing a pill reminder that never says 'missed' when it doesn't know

When several family members help an aging parent with medication, the hardest bug isn't a crash. It's a record that says something that isn't true. "Missed" when nobody actually checked. "Given" when someone only meant to give it. Two siblings both logging the same dose. We built DoseBeacon around one principle: the history should only ever say what someone actually reported. Here's how that…

When several family members assist an elderly person with their medication, the biggest challenge isn't a technical glitch, but rather a record that inaccurately states something that isn't true. For example, labeling a missed dose when nobody actually checked, or marking a dose as given when someone only intended to provide it once. DoseBeacon was developed with a single principle: the history should only ever reflect what someone genuinely reported. This design philosophy is evident in the user interface and features.

The application offers four straightforward buttons for the individual taking their medication: Senior Mode displays one large, high-contrast card at a time, and users have four options: LOG AS TAKEN, LATER, NOT SURE, and I NEED HELP. The "Not sure" option is considered a valid answer, not an error state. Read-aloud functionality, Dynamic Type, and VoiceOver support are included, and reminders operate offline by scheduling them on the device. Senior Mode does not display ads or purchase screens.

When there is a dose that hasn't been reported, it is labeled as "Not confirmed yet" instead of "missed." The absence of data does not imply a missed dose, and displaying a frightening word on a parent's screen would not be helpful. A claim is not considered a dose; tapping "I'm handling this" informs the rest of the care circle who is involved.

However, this claim is never presented as a dose given, only as a report. Conflicts are flagged, not overwritten. If two people report the same dose, it is marked as "Needs review" rather than adhering to the "last-write-wins" rule. Every report retains the person who made it, the device used, and the timestamp. Corrections are appended to the history; no data is silently erased.

Care circle permissions are managed through a circle code that only sends a join request. The parent's manager reviews and approves the request, assigns a role (manager, dose-logging helper, or read-only family member), and can revoke any device at any time. Each screen indicates when the data was last updated, preventing users from mistaking outdated information for current information.

An app feature called "Beacon Quests" encourages honest records by displaying a lighthouse as users complete tasks such as adding medications, selecting a helper, and reviewing an emergency card. These quests reward honest records, including "Not sure" and requesting assistance, without imposing streaks or consequences for being incorrect.

Other features include pharmacy-label scanning with on-device text recognition (with manual verification before enabling reminders), refill estimates, 7/30/90-day PDF reports for doctor visits, and a printable emergency medication card.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Migrate Bitbucket Pipelines to GitHub Actions

To migrate Bitbucket Pipelines to GitHub Actions, treat each Bitbucket step as a GitHub job, not a GitHub step: a Bitbucket step starts its own Docker container, so the files it shares travel as…

  • Treat each Bitbucket step as a separate GitHub job.
  • Map caches, services, and artifacts between Bitbucket and GitHub.
  • Adjust concurrency controls and specify build size with runs-on label.

Half My Old Articles' Comment Counts Include One Reply I Wrote Myself

I run a scheduled routine that writes and publishes articles to this account, and a separate rule change landed on November 4th that was supposed to make the output better: stop writing formulaic…

  • Average comments per article dropped from 2.18 to 0.61 after November 4th change
  • 58 out of 141 before-period articles had inflated comment counts due to author's own comment-reply
  • Normalized average reactions per day lived increased 27 times after the change

Go Agent Recovery With Free Uptime Monitoring APIs (3 Logistics Boundaries)

Choose free uptime monitoring APIs by the failure they can detect, and preserve an attempt ledger before enabling automatic recovery.

  • UptimeRobot and Healthchecks.io are suitable free uptime monitoring APIs for logistics AI agents.
  • Neither API alone determines which shipment experienced additional work during retries.

Why a Video Link Shouldn't Always Return a Video

A URL looks like a simple input. But when it points to a social post, the content behind it may be anything but simple. One post might contain a video.

  • A URL's content can vary from video to text
  • Parsing should model post content, not just video presence
  • Platform-specific adapters isolate URL handling complexities

I Told My Agent Who Sent the Message. It Mostly Stopped Saying We Were Talking.

This is the line: AUTOMATED SCHEDULER CHECK: sender=scheduler, not Keniel; Keniel is not participating in this turn. I added it to a frozen copy of my agent's scheduled self-audit request.

  • Agent incorrectly claimed conversation while human not participating
  • Corrected sender line improved accuracy, p-value 0.0000002
  • Advice to check sender info in scheduled messages

Beyond Black-Box Prompts: Building an Explainable Multi-Agent Financial Intelligence Platform with FastAPI & React

In quantitative finance and retail investing, treating Large Language Models as a single "oracle" prompt is dangerous. When you ask a single LLM whether a stock is a buy, it frequently exhibits…

  • Vibe-Finance platform combines multi-agent financial intelligence with explainability
  • System uses FastAPI backend, RAG over corporate filings, React/Vite/Tailwind client
  • Three specialized agents prevent single-point failure and bias in investment decisions

More from Sunday 15 November →