Skip to content

BACKLOG — Future features and deferred distribution #1518

Description

@timohueser

Future features and deferred distribution

This is the single backlog for future product work. Finish the current closeout issues before starting these features. An entry records interest, not authorization to implement it. Refine current code, data availability, product decisions and acceptance when a feature is selected.

Adventure and navigation

Feature Existing disposition Scope to preserve
Last open food/water stop before a gap Will add Evaluate availability at the rider’s ETA; unknown opening hours stay unknown. Cover food, water and repair/resupply categories. Keep complex source parsing off-device.
Emergency location screen Planned; consolidates #527 Readable coordinates, fix age/quality, nearest named place/road, and relevant emergency access-point references. Keep decimal degrees and degrees/minutes; assess other coordinate formats, emergency numbers and optional contact/medical details during refinement. Offline and quick to reach.
Named climbs and passes Planned with climb-view update Name climbs from route/map context; show useful distance, ascent and gradient facts. Include a day/trip high point where it helps.
Route to start, join a route, return to start/car Proposed; consolidates #505 New target pickers over the existing router, with a connector that hands off without mutating the selected route. Refine target selection, reachability, emergency wording and latency. Separate from current planner/detour parity in #1400.
Wikidata/Wikipedia sights Strongly considering Curated offline sights linked through OSM; control density, relevance, language size and attribution. Show upcoming sights in the companion and, sparingly, on-device.
Terrain horizon data Strongly considering Support terrain shade, sunset and viewpoint ideas only if the existing terrain mechanism is insufficient. Peak View already works without the proposed precomputed horizon grid. Measure format size and cost when a consumer is selected.
Terrain shade on the elevation profile Considering Show terrain shadow at ETA on the profile, without a popup. Do not claim that terrain predicts tree cover.
Terrain sunset time Considering Estimate when terrain hides the sun here or at a future route point. Combine with the existing daylight context.
Computed viewpoints Considering Identify useful open panoramas ahead rather than relying only on tagged viewpoints.
Hairpin countdown and sharp-turn warnings Considering; opt-in Route-following only. Use appropriate road geometry and conservative triggering; preserve the distinction between a turn warning and a guaranteed safe speed.
Lunch-stop / open-at-ETA filters Considering Reuse opening-hours and ETA logic for food, water, shelter, repair and other useful stops.
Sights and POIs on the climb profile Considering Place water, shelter and relevant sight markers on the climb view.
Panorama preview from a pass Considering; UI-limited Preview from a selected summit/pass using the existing Peak View where practical.
One-gesture waypoint marking Considering; uncertain Mark the current position, optionally categorize it and export it with the ride.
Tunnel, unlit-road and obstacle warnings Considering; marginal Relevant upcoming tunnels, lighting gaps and other obstacles; avoid a noisy warning system.
Personal loaded-pace ETA Considering Learn bikepacking pace versus gradient from recent rides. Use it for arrival, resupply and daylight decisions.
Trail blazes and route branding After launch Match an imported route to signposted route relations and show meaningful route names/blazes. Do not reserve format fields before implementation needs them.
Hiking support Low priority Hiking ETA and relevant difficulty/visibility warnings, with route branding where useful.

Power, connections and additional data

Feature Source Scope to preserve
Battery time-remaining estimate #528 Settings-only beta until real rides validate it. Requires a characterized battery and credible fuel-gauge input. Route-versus-battery estimates are a later extension.
Configurable charging current #953 Support constrained sources such as a dynamo. Refine actual power hardware, allowed settings and acceptance before implementation.
External ride-service sync #781 Opt-in Apple Health, intervals.icu and Strava integration; Komoot via an approved partner path or the existing GPX share flow. Preserve one-time setup, explicit consent, duplicate prevention and private credential storage. Recheck API access/auth terms when selected; the old research is not a current contract.

Deferred distribution

Feature Source Scope to preserve
Desktop installers, updater and signing #908 Explicitly deferred until launch work is wanted. Produce macOS/Windows/Linux packages, decide signing, verify an actual upgrade and write accurate install instructions. #993’s assigned USB PID is a prerequisite. The current app’s launch/USB acceptance remains in #994.

Existing firmware release activation, key management and delivery acceptance remain in #773. They are not future feature design. This backlog does not remove those obligations.

Rejected directions

Retain the previous decisions unless new evidence changes them: broad road-traffic datasets, live traffic, an OSM GPX popularity heatmap, accident overlays, cycle-node-network features, mobile-coverage/light-pollution/tree-cover layers, border/camp/end-of-day/moon features, and showing the blaze of a road without knowing which signposted route the rider follows.

Peak View is already delivered in PR #1595. Its old sketch and PoC status do not belong in the future queue.

The source issues #527, #528, #505, #781, #1201 and #908 are consolidated here. Their closed discussions retain detailed prior decisions. Configurable charging current comes from #953; its verification items have separate current owners.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions