People with migraines, IBS, chronic pain, and autoimmune conditions want to track daily patterns over time. Existing apps like Migraine Buddy demand 15+ fields per entry. Users abandon them within weeks because the logging burden exceeds the benefit. A builder on HN shipped dotsjournal: just tap a dot for your day and see patterns emerge. The demand is for pattern recognition with minimal input.
builder note The core insight is that adherence beats precision. A 1-5 severity dot tracked daily for 6 months is more clinically useful than a detailed 15-field log tracked for 2 weeks then abandoned. Ship with ONE condition (migraines), ONE input (severity tap), and ONE output (calendar heatmap). Add conditions and optional fields later. Medical PDF export for doctor visits is the feature that drives word-of-mouth.
landscape (4 existing solutions)
Health tracking apps optimize for data richness at the cost of adherence. Detailed logging yields better insights but users quit within weeks. The gap is a 5-second daily check-in (severity dot + optional tags) that accumulates into useful pattern visualizations over months. dotsjournal proved the concept on iOS. Android and multi-condition support are wide open.
Migraine Buddy 3.5M users but demands extensive data entry per episode: triggers, symptoms, medications, location, weather, duration. Users with frequent migraines burn out on logging. Requests invasive permissions including constant location access. Bearable General chronic condition tracker with good cross-condition support. But still requires detailed symptom logging per entry. The correlation insights need weeks of detailed data before becoming useful. Daylio Closest to the 'simple daily tap' model with mood+activity tracking. But not designed for health conditions. No medical export, no pattern analysis for symptom triggers, no condition-specific insights. dotsjournal Exactly the right philosophy: minimal daily input, visual pattern display. But iOS only, single developer, and focused specifically on migraines rather than general chronic conditions. sources (2)
healthchronic-illnessaccessibilityminimalpattern-tracking
USCIS, IRS, and other government agencies use Adobe XFA PDF forms that don't render correctly in most mobile PDF apps. Users trying to fill immigration paperwork, tax forms, or benefits applications on their phones hit broken fields, missing dropdowns, and failed submissions. A builder on HN shipped a free USCIS form filler validating this exact pain. The broader opportunity is any government PDF made mobile-friendly.
builder note Start with the highest-pain forms: USCIS (immigration), IRS (taxes), and FAFSA (student aid). These have the most emotional urgency and the worst mobile experiences. The privacy angle is critical: users filling immigration forms are especially sensitive about data. Run everything client-side, store nothing on servers. FillVisa's architecture (browser-based, local-only) is the right model.
landscape (3 existing solutions)
Government agencies standardized on Adobe XFA forms years ago and haven't modernized for mobile. Adobe's own mobile reader handles them but with terrible UX. FillVisa proved the model for immigration forms but the gap extends to all government paperwork. Nobody has built a mobile-native form filler that converts XFA government PDFs into touch-friendly, auto-saving, smart-fill experiences.
FillVisa Free USCIS-specific form filler that works in-browser with local-only data storage. But limited to immigration forms only. No IRS, SSA, or state government forms. Single developer project. Adobe Acrobat Reader Official PDF reader that handles XFA forms. But the mobile UX is terrible for complex government forms: tiny fields, no smart autofill, no progress saving across sessions, and premium features require subscription. DocHub Web-based PDF editor that works on mobile. But doesn't properly handle XFA form fields. Treats government PDFs as flat documents rather than interactive forms. sources (2)
governmentimmigrationPDFaccessibilityforms
Content consumers juggle separate apps for RSS articles, podcasts, YouTube, and newsletters. RSS reader adoption climbed 34% in 2026 as users flee algorithmic feeds, but no single Android app combines all content types into one prioritized timeline. Corefeed launched on iOS with smart bucketing across formats. Android has nothing equivalent.
builder note The technical challenge is audio playback (podcasts) alongside article rendering and YouTube embedding in one app. Don't try to build a full podcast player or a full RSS reader. Build a FEED that links out to dedicated players but provides a unified inbox. Think of it as an email client for content: you see everything in one place, but tapping opens the best handler. YouTube RSS feeds are free and well-documented.
landscape (4 existing solutions)
The Android content consumption ecosystem is fragmented by format: one app for articles, one for podcasts, one for YouTube. Web-based readers like FeedSpot unify formats but lack native mobile UX. Corefeed proves the iOS demand but Android is unserved. The opportunity is a native Android app that treats all content formats as first-class items in a single chronological or smart-bucketed feed.
Corefeed Does exactly this but iOS-only. No Android app. Builder is a single developer from the HN thread, so Android may be far off. Podcast Addict Best Android podcast app with RSS feed parsing. But focused on audio content. No YouTube integration, no article reading, no unified timeline across content types. FeedSpot Web-based unified reader supporting blogs, YouTube, podcasts, and newsletters. But the Android experience is a mobile web wrapper, not a native app. No offline reading or smart content bucketing. Feedly Strong RSS reader with YouTube feed support. But podcast playback requires external apps. No unified audio+text+video experience. AI features locked behind $8/month subscription. sources (2)
RSSpodcastscontentandroidinformation-diet
Built-in Android screen time tools are trivially disabled with a single tap on 'Ignore Limit.' Third-party apps like ScreenZen can be bypassed by changing the phone clock. Users serious about breaking phone addiction want software blocks that create real friction, not polite suggestions. The only effective solution right now is Brick, a $100+ physical NFC tag. The software gap is wide open.
builder note The technical key is Android's Device Admin API, which can genuinely prevent app access without the bypass loopholes. Stay Focused proved it works but the UX is terrible. Build the Brick experience in software: a 'lockdown mode' that requires a time-delayed cooldown (not just a tap) to disable. Partner with therapists or digital wellness programs for distribution. The audience that will pay is parents of teens and adults in therapy for phone addiction.
landscape (4 existing solutions)
The screen time app space has a fundamental tension: Android gives users ultimate control over their devices, making any software block bypassable in theory. The apps that work best either use physical hardware (Brick) or leverage Android's Device Admin API for strict enforcement (Stay Focused). The gap is a well-designed, affordable app that uses Device Admin for genuine enforcement with modern UX and smart scheduling.
ScreenZen Clever friction-based approach (delay screens before opening apps). But bypassable by changing system clock. No strict lockout mode. Stay Focused (Strict Mode) Has a genuine strict mode that prevents settings changes until timer expires. But the UX is clunky, the interface is dated, and setup is confusing for non-power-users. RepsForReels Innovative approach: do physical exercise reps to earn screen time. Foreground service is hard to kill. But niche appeal. Most users don't want to do pushups to check Instagram. Brick Most effective blocker because it uses a physical NFC tag you must scan to unblock. But costs $100+ for hardware. Not accessible to budget-conscious users or teens. sources (3)
digital-wellnessscreen-timephone-addictionandroidmental-health
Smart home owners juggle 5-10 brand-specific apps. Home Assistant can unify them but requires YAML editing and significant setup. Users want a visual floorplan where they tap a room to control lights, see sensor data, and get alerts. A builder on HN is validating this exact gap with a floorplan dashboard product that skips SVG and 3D modeling entirely.
builder note Don't compete with Home Assistant on integrations. Build a beautiful floorplan layer that sits ON TOP of Home Assistant as a frontend. The HA API is well-documented. Users who already have HA running want a prettier, tap-friendly interface for their wall tablet. Users who don't have HA want you to handle the setup invisibly. Pick one audience first.
landscape (3 existing solutions)
Home Assistant dominates the unified dashboard space but its complexity creates an accessibility floor that excludes most smart home owners. The specific gap is a floorplan-based visual interface that auto-discovers devices and lets users place them on a room map without technical knowledge. The HN project getsmarthomefloorplan.com is the first to target this exact niche.
Home Assistant Most powerful option but setup requires dedicated hardware, YAML configuration knowledge, and ongoing maintenance. The visual automation editor handles 80% of needs but the other 20% still requires code. Floorplan dashboards exist as add-ons but need SVG files created in external tools. SharpTools Clean dashboard builder that works with SmartThings, Hubitat, and Home Assistant. But no native floorplan view. Dashboards are grid-based widgets, not spatial room layouts. Gladys Assistant Self-hosted, no YAML, beautiful UI. Genuinely simpler than Home Assistant. But smaller device ecosystem, limited integrations compared to HA, and no floorplan-based interface. sources (3)
smart-homeIoTdashboardconsumerhome-assistant
YNAB's price climbed 118% over nine years to $109/year and automatically syncs all financial data to their servers. Users want genuine offline-first budgeting where data stays on-device by default, with optional encrypted sync they control. Most 'offline' budget apps reconnect and upload silently. The privacy-conscious and subscription-fatigued overlap heavily here.
builder note The technical insight: use Syncthing-style encrypted device-to-device sync instead of a cloud backend. Users get multi-device without trusting a server. The business insight: charge a one-time fee ($5-10). The subscription-fatigued audience will gladly pay once for something that respects their data. Don't try to compete with YNAB's methodology. Just be the budget app that never phones home.
landscape (4 existing solutions)
The budget app space has a clear gap between cloud-first subscription apps (YNAB, Mint successors) and truly local apps that sacrifice sync. Actual Budget bridges this with self-hosting but demands technical skill. Nobody has shipped an offline-first mobile budget app with optional encrypted peer-to-peer sync (no central server) for non-technical users.
YNAB Gold standard methodology but $109/year and cloud-only architecture. All data goes to YNAB servers. European bank connectivity frequently broken, forcing manual entry anyway. BudgetVault 100% free and local-only. But no cross-device sync at all. If you lose your phone, you lose your budget. Single-device limitation is a dealbreaker for multi-device users. 1Money One-time $3.49 purchase with no subscription. Solid basic budgeting. But no bank sync, no envelope budgeting methodology, and no zero-based budgeting like YNAB offers. Actual Budget Open source and self-hostable with optional sync. Closest to the ideal. But requires self-hosting setup (weekend project minimum), which excludes non-technical users entirely. sources (2)
financeprivacyoffline-firstsubscription-fatiguebudgeting
Plant ID apps have become a subscription dark pattern minefield. NatureID hides the cancel button, PlantSnap gates free IDs behind 12-hour delays, Plant Parent killed its free tier entirely. Users are getting charged $50 within days of 'free trials.' The free alternatives (PlantNet, iNaturalist) do identification well but lack personal garden management and care reminders.
builder note The ID model is solved (use a plant recognition API or fine-tuned model). The real product gap is accurate care data tied to a personal garden tracker. The trap: don't scrape care data from the web. Partner with a botanical garden or use verified horticultural databases. Plantora's inaccurate care guides show that bad data kills trust faster than missing features.
landscape (4 existing solutions)
The plant app space split into two camps: subscription-hungry commercial apps with care features and aggressive billing, vs. free scientific apps with great ID but no personal plant management. Nobody has combined free identification with accurate care guides and personal garden tracking without resorting to subscription dark patterns.
PlantNet Excellent free identification of 20,000+ species with no dark patterns. But zero personal garden features: no care reminders, no watering schedules, no 'my plants' collection tracking. iNaturalist Free, community-driven, great for nature observations. But designed for citizen science, not personal plant care. No watering reminders, no care guides, no garden management. Plantora Completely free with no subscription. But plant care data is inaccurate (e.g., basil listed as watering twice monthly). Trust issues with care recommendations undermine the core value. Flora Incognita Free, research-backed, excellent for European flora. But limited species coverage outside Europe and no personal garden/care features. sources (2)
gardeningplantssubscription-fatigueconsumerandroid
Cyclists want to input a destination and get routes that automatically avoid steep grades above a threshold. Every major cycling app requires manual route drawing and hill-checking. Forum threads show users sharing multi-app workarounds (OSMAnd + BRouter + elevation overlays) to achieve what should be a single feature. E-bike riders and older cyclists especially need this.
builder note Don't build a full cycling app. Build a route planner that does ONE thing: point A to point B with a max gradient slider. Export GPX files that users load into their existing tracking app (Strava, Garmin). BRouter's open-source routing engine already handles the hard math. The moat is UX simplicity and good mobile offline maps.
landscape (4 existing solutions)
The cycling app space has mature tracking and decent elevation visualization, but zero apps offer automatic gradient-constrained routing in an accessible interface. OSMAnd+BRouter proves it's technically feasible but the UX is developer-grade. The opportunity is wrapping BRouter-style gradient routing in a consumer-friendly mobile app.
Komoot Surface-aware routing and good elevation profiles, but no maximum gradient filter. Cannot auto-generate a route that avoids hills above X%. Also cannot plan routes offline. Strava Great for tracking and analysis but route PLANNING is weak. Mobile app cannot edit/splice routes. No gradient-based routing parameters at all. OSMAnd + BRouter Closest to the need with 'Less Hilly' presets and BRouter plugin for gradient-aware routing. But requires installing two apps, configuring routing profiles, and understanding OpenStreetMap data. Not accessible to casual cyclists. Ride with GPS Excellent elevation data and route building tools, but no automatic gradient avoidance. Users must manually check elevation charts and drag waypoints around hills. sources (2)
cyclingfitnessnavigationaccessibilityoutdoor
Medisafe moved to mandatory paid subscriptions on Jan 1 2026, capping free users at 2 medications. Over 22% of US adults aged 40-79 take 5+ prescriptions, making the cap useless for the people who need reminders most. Users are scrambling for free alternatives with unlimited med tracking, persistent alarms, and health logging.
builder note The Medisafe exodus is a time-limited acquisition window. Users are actively searching for alternatives RIGHT NOW. Ship fast and simple. The trap is trying to replicate Medisafe's full feature set. Instead, nail persistent alarms and unlimited meds, then add health tracking. MedTimer proves the open-source angle works but it needs a non-developer UX layer.
landscape (3 existing solutions)
Three viable free alternatives exist but each has a distinct gap. Pillo is young, MedTimer is privacy-first but bare-bones, MyTherapy is feature-rich but pharma-funded. Nobody has shipped a free, open-source medication app that combines persistent alarms, health tracking, caregiver alerts, AND cross-device sync without monetizing user health data.
Pillo Free and unlimited but relatively new with a small user base. No caregiver notification network like Medisafe's Medfriends feature. Limited health tracking integrations. MedTimer Open source and fully offline, which is great for privacy. But no health tracking (blood pressure, glucose), no caregiver alerts, and no cloud sync between devices. Developer-oriented UX. MyTherapy Closest full replacement with health journal and free unlimited meds. But monetizes through pharmaceutical partnerships and anonymized data aggregation, which privacy-conscious users distrust. sources (3)
healthmedicationaccessibilityprivacyandroid