What we're building and what's coming next
1,420 protected lane segments from OpenStreetMap, with tap-to-view details and toggle visibility.
Status: Complete, deployed in iOS app v1.0
GraphHopper-based routing with basic cycling profiles and turn-by-turn navigation.
Status: Core routing functional, profiles being refined
Collect stamps for riding protected infrastructure, basic leaderboards and progress tracking.
Status: V1 complete, iterating based on user feedback
Sophisticated two-layer route rendering: wide semi-transparent background (14pt @ 50%) plus thin precise foreground line (2.5pt solid / 1pt dashed). Solid lines indicate better protection, dashed lines show minimal infrastructure.
Status: Deployed October 2025 in iOS app
Routes dynamically change colors based on infrastructure transitions - green for protected paths, cyan for bike lanes (solid=buffered, dashed=basic), orange for residential, red for high-traffic. Each segment colored based on actual infrastructure present.
Status: Deployed October 2025 with GraphHopper bike_infra integration
GraphHopper routing with tuned multipliers: protected lanes (3.0×), separated paths (2.5×), buffered lanes (2.0×), shared paths (1.5×), basic lanes (1.3×). Routes prioritize safety while maintaining practical travel times.
Status: Production deployment with bike_conservative profile
Visual heatmaps showing cycling activity density, popular routes, and infrastructure gaps. Designed for BUG groups and local councils to identify improvement priorities and make evidence-based advocacy.
Target: Q2 2026
Partner dashboards for BUG groups showing aggregated cycling patterns, hazard hotspots, and infrastructure usage in their area. Export reports to PDF/CSV for advocacy and planning meetings.
Target: Q3 2026
Anonymized, aggregated data feeds for local councils showing cycling trends, high-traffic corridors, and infrastructure effectiveness. Helps councils make data-driven planning and investment decisions.
Target: Q4 2026
User-reported hazards with photo uploads (construction, debris, flooding, road conditions). Community comments, verification votes, and map display with tap-to-view details.
Status: Complete with photo support and community feedback
Automatically route around reported hazards based on severity and recency. Requires careful balancing to avoid over-routing and ensure route practicality.
Target: TBD - researching implementation approach
Integration with Emergency Victoria and VicRoads for real-time road closures and incidents. Requires API partnerships and continuous data processing infrastructure.
Target: TBD pending government partnerships
Native Android version with feature parity to iOS. Evaluating development approach and resource requirements. Depends on iOS app maturity and user demand.
Target: 2027+ (pending iOS adoption metrics)
Expanding beyond Victoria to other Australian states. Each region requires custom OSM data processing, local BUG partnerships, and infrastructure verification. Victoria-first approach to prove model.
Target: TBD - pending successful Victoria deployment
Partnerships with councils to integrate official infrastructure plans, construction schedules, and maintenance data. Requires data sharing agreements.
Target: TBD
This roadmap is a living document. We prioritize features based on community needs and feedback from BUG groups. Have ideas? Want to see something specific?
Join the discussion and let us know what matters most to you. We're building this transparently with the cycling community.