The Route Plan
A motorcycle route-planning and group-ride system that connects route design, readiness, live coordination, and ride recaps.
What it is
The Route Plan is an early-access motorcycle route-planning and group-ride coordination product. It is designed to connect route design, crew organization, rider readiness, live ride coordination, route-aware stops, and post-ride recaps in one workflow. The current public artifact is a landing page and interactive concept demo; the full rider application is not yet publicly available.
Problem being solved
Planning a motorcycle ride commonly spans disconnected map links, group-chat messages, attendance polls, readiness reminders, stop planning, and temporary location-sharing tools. That fragmentation creates ambiguous plans before departure and weak shared awareness once a group is moving.
How it solves the problem
- Center the ride lifecycle on one shared plan with scenic, balanced, and direct routing plus GPX, KML, and GeoJSON imports.
- Coordinate invitations, attendance, ride notes, regroup points, captain and sweep roles, and rider-readiness checks.
- Provide opt-in, ride-scoped pack visibility and route-aware fuel, charging, food, mechanic, viewpoint, and accommodation stops.
- Carry multi-day ride legs through to a post-ride route, crew, and memory recap. These capabilities remain proposed until the production rider application launches.
Technology used
React
Powers the public landing experience and interactive concept demo.
Static ES modules and CSS
The public frontends ship as static bundles; the build tool is not publicly documented.
Separate application API
The landing page submits early-access requests to an API on api.therouteplan.com.
Cloudflare, AWS, and Caddy
Documented edge, hosting, infrastructure, and API gateway layers.
Google Analytics 4
Page and product-event instrumentation; production results are not yet published.
Brevo and Clerk
Email delivery and authentication-enabled services identified by the public policies.
Implementation details still TBD
Database, mapping provider, realtime protocol, and eventual client platform are not publicly verifiable.
Analytics placeholder
Product signals
Awaiting early-access data
Replace these placeholders with a dated reporting window after early access begins. Demonstration figures are simulated and must not be presented as production usage.
- Signup conversion
- Pending baseline
- Ride publish rate
- Pending baseline
- Readiness completion
- Pending baseline
- Repeat ride planning
- Pending baseline
Illustrative — not implementation-verified
Basic system architecture
This is a deliberately provisional model for the proposed product. Database, mapping, realtime, and mobile technology choices remain unspecified until the implementation is confirmed.
01
Rider client
Proposed web or mobile surface for plans, readiness, live coordination, and recaps.
02
Cloudflare edge
Public traffic and static assets enter through the documented edge layer.
03
Application API
A working boundary for route, ride, rider, readiness, live-pack, and recap operations.
04
Domain data and integrations
Placeholder stores and providers for transactions, routes, ephemeral location, identity, notifications, and media.