IdeaWell

Project ideas from Hacker News discussions.

Show HN: Open-Source eInk Bike Computer

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

Three prevalent themes in the discussion

  1. Enthusiasm for e‑ink as a bike‑computer display
    Many commenters praised e‑ink for its sunlight readability, low power draw, and clean look.
  2. “eInk is the right display tech. I think this will do really well.” — mholt
  3. “But man, that eInk looks so clean and nice. Definitely the superior display!” — mholt
  4. “Within 10 seconds I was convinced I needed to try this.” — neoCrimeLabs

  5. “I love my eInk displays, I love my bike head unit.” — wiether

  6. Concerns about e‑ink’s practical limitations
    Several users pointed out drawbacks such as slow refresh rates, fragility, UV degradation, poor visibility in low light, and lack of colour.

  7. “Does this work well in direct sunlight? I know a lot of e‑paper panels struggle to refresh in strong sunlight.” — dinan
  8. “For all their readability benefits under direct sunlight, prolonged exposure also damages or kills them. You need at least a UV blocker for outdoor use, but the heat cannot be avoided.” — orbital‑decay
  9. “I've found e-ink displays super fragile for this use case. They break from a little fall, or even from the constant shaking.” — zsoltkacsandi

  10. “The cons of eInk: refresh rate … visibility in the dark … lack of color.” — wiether (quoted from their pros/cons list)

  11. Excitement over hacking ANT+ via BLE (often aided by LLMs/logic analyzers)
    The technical feat of getting ANT+ working on BLE hardware sparked interest, with remarks about protocol similarity, AI‑assisted reverse engineering, and the ANT+ ecosystem’s fate.

  12. “Wow. You managed to receive ANT via BLE hardware?! I didn't know these two protocols were so similar.” — kccqzy
  13. “yes. they luckily the same phy, 1 Mbit/s GFSK modulation.” — stingrae
  14. “AI does make it really easy to figure out these protocols now… I just flipped my bike upside down and hooked up a logic analyzer and it took LLM no time to figure it out… it is really impressive.” — tuchsen
  15. “EDIT: Woah, you got ANT+ support using BLE radio? … that must have been a clever LLM.” — mholt (edit)

🚀 Project Ideas

Generating project ideas…

OpenSource BikeComputer Hardware Kit

Summary

  • A DIY, waterproof bike computer built around an ESP32, UV-protected e‑ink display, and optional physical buttons, supporting ANT+ (via BLE‑to‑ANT bridge) and BLE sensors.
  • Core value: low‑cost, open‑source hardware that survives rain, snow, and sunlight while delivering customizable data fields, voice feedback, and local ride logging.

Details

Key Value
Target Audience Cyclists wanting a cheap, durable, hackable bike computer (e.g., pilina, Lucioasato, tuchsen)
Core Feature ESP32‑based controller with e‑ink display, UV filter, waterproof enclosure, BLE‑to‑ANT bridge for legacy sensors, onboard TTS for voice alerts, and local FIT/GPX logging
Tech Stack ESP32‑S2/S3, 2.7” e‑ink panel with UV coating, silicone/waterproof case, Micropython or Arduino‑IDE, TinyBLE library for ANT+, eSpeak NG for TTS, optional companion Android/iOS app for maps
Difficulty Medium
Monetization Revenue-ready: Kit sales ($45‑$60 per unit)

Notes

  • HN users lamented the lack of a cheap waterproof alternative (“I am searching for alternative, which needs to be waterproof and cheap” – pilina) and praised open‑source hackability (“The mess of different implementations makes it really hard to hack on and share this kinda stuff.” – tuchsen).
  • Provides a tangible platform for experimenting with ANT+ via BLE (kccqzy) and addresses UV/fragility concerns (orbital‑decay, zsoltkacsandi) by incorporating a UV filter and rugged enclosure.
  • Enables community‑driven firmware upgrades (voice modes, thermal management) that align with mholt’s desire for phone‑like features on a dedicated device.

PhoneBike: All‑in‑One Bike Computer App

Summary

  • A cross‑platform (iOS/Android) bike‑computer app that offers multiple UI modes (high‑contrast wireframe, rich map, voice‑only) and automatic thermal/throttle management to save battery.
  • Core value: turns a rider’s phone into a powerful, adaptable bike computer without extra hardware, while still supporting ANT+ sensors via a low‑cost BLE dongle.

Details

Key Value
Target Audience Riders who prefer using their phone but want better visibility, voice control, and sensor integration (e.g., mholt, robot_jesus, jeffbee)
Core Feature Switchable ride modes (wireframe map for low‑power, voice‑only for eyes‑free, rich map for navigation), BLE central for ANT+ sensors (using a cheap BLE‑to‑ANT dongle), voice TTS updates, radar overlay, automatic GPU/CPU throttling to control temperature, local ride logging with export to personal fitness DB
Tech Stack React Native or Flutter, Mapbox GL/MapKit for maps, AVFoundation/AVSpeechSynthesizer for iOS, TextToSpeech for Android, Bluetooth Low Energy (BlueZ/CoreBLE), optional BLE‑to‑ANT bridge firmware (ESP32), secure local storage (SQLite/Realm)
Difficulty Medium
Monetization Hobby (open‑source) – optional donations or “tip jar”

Notes

  • mholt expressed a preference for phone‑based solutions (“I really prefer to just plop my phone on my handlebars… I’m building a bike computer app for iPhone”) and highlighted the need for voice‑only mode, thermal management, and radar integration.
  • jeffbee suggested using the phone as a GPS peripheral and wanted a way to offload GPS to the phone – this app makes the phone the central hub.
  • Users worried about e‑ink refresh rate and darkness; PhoneBike’s high‑contrast wireframe mode works at 1 Hz and is readable in low light, while voice‑only mode removes display dependency entirely.
  • Open‑source nature invites the community to contribute new modes (e.g., HR‑zone power control) and improves upon fragmented proprietary apps.

FitVault: Personal Fitness Data Hub

Summary

  • A self‑hostable web service that ingests ride files (FIT, TCX, GPX, CSV) from any bike computer or phone app, provides rich analytics (HR zones, power curves, route heatmaps), and can issue control commands to smart trainers to keep the rider in a target HR zone.
  • Core value: gives cyclists full ownership of their data and enables closed‑loop training without relying on proprietary cloud platforms.

Details

Key Value
Target Audience Data‑savvy cyclists and triathletes who want to avoid vendor lock‑in and use their own data for training (e.g., neoCrimeLabs, mharrison)
Core Feature Upload API/web UI for activity files, visualization dashboard (HR vs. time, power, elevation), HR‑zone alerting, MQTT/REST bridge to adjust smart‑trainer resistance, export to personal databases (InfluxDB, Postgres) or downstream services (Strava, TrainingPeaks)
Tech Stack Backend: Node.js (NestJS) or Python (FastAPI); DB: TimescaleDB or PostgreSQL with PostGIS; Frontend: Svelte or React with Chart.js/WebGL maps; MQTT broker (EMQX) for trainer control; Docker‑compose for easy deployment
Difficulty High
Monetization Hobby (open‑source) – optional paid support or hosted instance

Notes

  • neoCrimeLabs wanted to “load [sensor] data into my own fitness tracking database that I own, control, and isn’t tied to someone else’s profits.” FitVault directly satisfies that by letting users store data on their own server.
  • mharrison wished to “set an HR zone and then connect it to my e‑MTB and have it change power to keep me in a zone.” The hub’s MQRT‑to‑trainer bridge can automate resistance based on real‑time HR.
  • The discussion highlighted the death of ANT+ due to EU regulation and a desire to move toward open, interoperable data formats – FitVault accepts the ubiquitous FIT/TCX/GPX/CSV files, making it future‑proof.
  • Self‑hosted approach appeals to privacy‑conscious HN readers and encourages community contributions (plug‑ins for new sensor types, novel visualizations).

Read Later