OpenFoodFacts proxy via OHD SaaS
So the app doesn't hit world.openfoodfacts.org directly on every search. Same response shape; rate-limited + cached.
Vote / discuss →Roadmap
What we're building.
OHD is built in the open. Below is what's shipped this beta cycle, what's actively being implemented, and what's planned next. To vote on what we should build next, react with 👍 on a GitHub issue. To ask for something new, open one.
Updated weekly Items move between columns as PRs land. Vote counts mirror GitHub reactions.
Done
Shipped this beta cycle.
Live in the current APK download. Bug reports for any of these are welcome — open a GitHub issue with the "bug" label.
- Pencil-aligned Connect Android UX Home (KADlx) · Medication v2 · Food v3 + search · Symptom log · Measurement log · Urine strip · Pain score · Form builder · Recent events · Settings hub + 8 sub-screens · Personal CORD chat skeleton.
- Inline barcode camera + OpenFoodFacts lookup CameraX preview embedded in the food screen, ML Kit barcode detection, OFF lookup for both barcode + free-text product search.
- Android Health Connect sync Read-only sync of Steps / Heart rate / Blood pressure / Glucose / Weight / Body temperature / Sleep / SpO2. WorkManager 15-min periodic backgrounded; 30 s foreground polling. 5-year initial backfill on first install.
- Local notifications + reminders engine In-app inbox at the bell icon, system notifications via the WorkManager reminders worker, medication-due alerts, optional daily summary.
- Operator screens accessible via Settings → Profile & Access Grants, Pending approvals, Cases, Audit log, Emergency, Export — full operator flow reachable from a consumer-first home.
-
Honest deploy story
Single Hetzner ARM box runs storage + relay + Caddy. Beta APK served from
/downloads/. Specification + source dual-licensed Apache-2.0 OR MIT.
Building
Right now.
Open pull requests + the work landing in the next 1–2 weeks of betas. Watch a PR to get pinged when it merges.
- Cross-runtime metrics registry Single canonical TOML for the supported measurement types. The Android app, the Rust storage core, and the server all load from the same source. Custom-measurement management surfaces in Settings → Forms.
- CORD chat — provider API keys Bring your own Anthropic / OpenAI / Gemini key, or sign up for the OHD managed model (Gemini + MCP access to your data, your grant rules).
- OHD Cloud / Self-hosted / Provider-hosted storage First-run storage chooser already shows the four options; only on-device is wired today. Cloud + self-hosted + provider-hosted backends are next.
- Devices screen + paired sources The "1 device" tile on Home will list every connected source (Health Connect, future paired wearables, browser sessions, clinic-issued tokens).
- Food consumption-in-progress Some foods get consumed gradually (a Red Bull open 4 hours, a coffee sipped). Start now → finish later flow, with the "in progress" list on the food screen.
- Extended nutrition panel Show-more affordance on the food screen to reveal fibre, sodium, cholesterol, saturated fat, vitamins — every nutriment OpenFoodFacts has.
Planned
Next.
Scoped + on the agenda, not yet implementation-started. Vote with 👍 on the matching issue to bump priority.
iOS Connect app
The Rust core already cross-compiles for iOS via uniffi. The SwiftUI scaffolding needs to catch up to the Android UI parity we have today.
Vote / discuss →Health Connect Changes API
Migrate from time-range reads to OFF's getChangesToken + getChanges for proper deltas including deletions, and cheaper polling.
Wearables: Wear OS companion
A small watch face complication + quick-log tile for medication / mood / pain — writes directly to OHD via Health Connect on the phone.
Vote / discuss →EU eIDAS / smart-ID clinician auth
Existing Grants flow assumes a custom OIDC. Wire the common European national-ID issuers so clinicians can authenticate without bespoke per-clinic setup.
Vote / discuss →Calendar export for medication reminders
Push the prescribed-medication schedule into Google / iCloud calendars so reminders fire on watches without OHD running.
Vote / discuss →How to help
Help us pick what to build.
Vote on existing requests
Browse open feature-requests sorted by 👍 reactions. The top of that list is what we look at next when scoping a beta cycle.
Open the issue list →Request a new feature
One short paragraph: what does the feature do for you, and what existing flow would it replace or augment. We read every one.
Open a feature request →File a bug
Anything in the shipped APK that crashes, persists wrong, or silently fails — open a bug with the "bug" label + a logcat snippet if you can grab one.
Open a bug report →