Decision-Point E-Ink Bike Navigation
Before a long ride, turn a route into low-refresh navigation pages that reveal directions, hazards, or resupply details only when a decision is needed.
Before a long ride, cyclists import a GPX route and the device splits the continuous map into a stack of e-ink event pages. During the ride, the screen persistently shows speed, remaining distance, and the next key point, remaining legible in sunlight without frequent charging over several hours.
Only shortly before GPS reaches a complex intersection does the screen refresh to an enlarged turn diagram and a single action prompt. Near a resupply stop, the page shows water availability, opening hours, or a supply checklist. Route authors can also embed alerts for roadworks, hazardous descents, and other conditions at the relevant locations.
If a rider leaves the route, the device does not present a dense, hard-to-read map. It shows only the direction and distance needed to return to the route. Once the route is rejoined, navigation automatically returns to the next event page; the full flow still works without network access.
The first hardware release can focus on single-day and multi-day riding, with GPX import, offline positioning, and a small number of route annotations. Social rankings, training analytics, and live emergency tracking can wait for later versions, keeping attention on the moments when riders genuinely need to look up and decide.
Why now
When observed on September 5, the open-source e-ink bike-computer project ranked sixth on Hacker News, with 221 points and 76 comments. S1 That brought the concrete trade-offs of offline, sunlight-readable, low-power navigation into developer discussion.
Target user
People riding solo on single-day endurance rides or multi-day bike tours. They typically already have a GPX file from a club, event organizer, or Komoot, and are willing to check resupply and risk points before departure. The real need arises when they are tired, in bright sun, or without signal: reading a complex map is slow, and pulling out a phone breaks riding rhythm.
Minimal entry point
Start with OpenTrailPaper’s open firmware. Its existing hardware already includes an ESP32-S3, GPS, an e-ink display, and an SD card. S2 A phone app first parses the GPX file and creates an ordered event list. The first version recognizes only clear turns, user-set markers, and off-route states. Authors can manually correct complex intersections rather than relying on unreliable automated judgment. The device stores the route polyline, event coordinates, and a simplified basemap. While riding, it matches the current location to the next event and refreshes only the relevant part of the page. Initial offline recovery should use the nearest route segment and direction of travel, not full road-network recalculation.
Punching above its weight
Acquire the first users through the DIY bike-computer community. OpenTrailPaper has already attracted people willing to flash firmware and assemble hardware. S2 Publish compatible route packs and an event-page compiler so existing devices can test the experience immediately. Then invite long-distance route authors to create demonstration routes with public resupply and hazard markers. Real route files are more likely than broad promotion to generate downloads, reproducible tests, and improvement feedback.
Competitors & gaps
- OpenTrailPaperGoogle
- OpenTrailPaper already imports GPX files and displays offline maps on the device. It also provides turn prompts, ride recording, and Bluetooth sensor connectivity. Once routes and maps are loaded, it needs neither a phone nor a network during a ride. S2 It shares this product’s e-ink, offline-navigation, and open-hardware approach. Its interface still centers on a dashboard and follow-along map rather than compiling an entire route into a limited set of event pages. Resupply stops, roadworks, and hazardous descents are not core route objects either. If a rider goes off route and must rely on the map, they still need to interpret the surrounding roads. The opening is stricter information restraint: each refresh answers just one immediate decision question, while route authors decide exactly where an interruption is worthwhile.
- Beeline Velo 2Google
- Beeline Velo 2 already offers simple turn-by-turn navigation. It supports GPX import, off-route rerouting, and ride-data display, including climbs, remaining distance, and estimated arrival time. S4 Its compact display, designed for quick glances, has validated the minimal-navigation form factor. Route planning and the main navigation computations still run in the phone app, and its specifications state that a Bluetooth connection is required. S4 For multi-day riders, phone battery and pairing status remain part of the reliability chain. It is not an e-ink device, and route content is controlled by the navigation system. Users cannot easily embed a water-stop checklist or road-condition warning at a specific location. The opening here is to complete all compilation before departure, then run the device solely on local positioning and event pages during the ride.
- Garmin Edge Explore 2Google
- Garmin Edge Explore 2 already covers mature cycling navigation, with high-contrast maps, turn-by-turn prompts, and off-route handling. Routes can be synced from Garmin Connect, Strava, or Komoot. S3 It also integrates climbs, safety tracking, and an external-device ecosystem. It is more comprehensive for riders who need full maps and training features, but that breadth brings more feature layers and a screen that continuously carries both maps and data. Route authors also cannot easily turn a resupply checklist into the primary page triggered by a location. Multi-day routes still require managing device battery and companion services. A new product should not try to match all of Garmin’s capabilities. It can retain a narrower task boundary focused on infrequent decisions: replacing map reading with a prearranged sequence of events.
How it makes money
Charge once for the hardware and include the route compiler for free. Keep basic offline navigation subscription-free. Later, offer an annual plan for route cloud backup, syncing author annotations, and firmware hosting.
The case against
A wrong turn directly causes detours and can mean missing resupply in remote areas. GPX files often contain only track points, so automatically inferring an action at an intersection can create false prompts. Roadworks, opening hours, and water availability also go stale, requiring clear maintenance ownership. E-ink refreshes slowly, so continuous speed display and local map updates may compete for power. Outdoor hardware must also handle waterproofing, vibration, low temperatures, and mount reliability. If off-route recovery is not stable enough, riders will quickly return to their phones. Before proceeding, validate turn-prompt accuracy and all-day battery life on real long-distance routes.