AirPods Pro owners who've switched to Android want the hearing-enhancement features Apple ships on iOS: apply an audiogram and get real-time amplification. LibrePods is the only open-source bridge, but its hearing-aid implementation has recurring bugs across multiple release cycles... audiogram saves don't persist, amplification doesn't apply to music, settings reset on reconnect. The opportunity is a stable, maintained Android layer for AirPods hearing features, or a first-party equivalent that doesn't require users to root their phones for something that still half-works.
builder note The initial scope is narrower than it sounds... AirPods Pro + audiogram persistence + reliable amplification is already a real product with paying users. Nail that before expanding to other earbuds. Watch the FDA OTC hearing-aid claim line in your copy.
landscape (3 existing solutions)
iOS proved the 'AirPods as OTC hearing aids' model works, but on Android the only path (LibrePods) is fragile and actively broken for hearing-specific use cases. The multi-year bug backlog on a single open-source project shows demand with no real commercial alternative for AirPods users who've left Apple's ecosystem.
LibrePods Open-source bridge that brings AirPods hearing-aid customizations to Android and lets you SET an audiogram, but it can't run a hearing test to generate one and has recurring bugs saving/applying results (see the cited issues). sources (3)
accessibilityhearing-aidandroidaudiootc-hearing
People who run their own private or self-hosted food and fitness tracker want their logged calories, water, weight, and sleep pushed back out into the phone's health hub (Apple Health / Android Health Connect) so the OS, their rings/watches, Home Assistant, and clinician apps all see one complete picture. Today these trackers are read-only sinks or standalone, so privacy-minded self-loggers keep a parallel MyFitnessPal account just to feed Apple Health. The opening is a privacy-first tracker that is a first-class WRITER to both platforms.
builder note The moat isn't the food diary, it's being a reliable WRITER to HealthKit and Health Connect... HealthKit has no backend API, so you must ship a small native companion on each platform that syncs and writes on-device. Nail bidirectional sync and you become the private hub everything else points at.
landscape (3 existing solutions)
HealthKit has no server API (data lives on-device), so any self-hosted tracker needs a thin native iOS/Android companion that holds the permissions and writes to the health store. That platform plumbing, not the food diary, is why FOSS trackers stay read-only and users keep a second MyFitnessPal copy alive.
SparkyFitness Actively developed self-hosted nutrition/fitness tracker, but writing your logged data back to Apple Health and Health Connect is unbuilt (these are the open requests). It is effectively a data sink, not a writer. Open Wearables Self-hosted platform that syncs HealthKit/wearable data INTO your backend (read-in). Solves the opposite direction; does not push your own logged nutrition back OUT to the OS health store. MyFitnessPal / Cronometer Proprietary apps that DO write nutrition to Apple Health and Health Connect, but they are cloud-bound, ad-supported, and not self-hostable... which is exactly what these users are trying to leave. sources (2)
self-hostedhealth-dataapple-healthhealth-connectprivacy