Look at your run, hike or ride the way a trader looks at a ticker. The user drops a GPX file on the page and gets a trading-terminal view of it: speed as price, distance as the x-axis, candlesticks, moving averages, a volume panel driven by elevation, and a route map linked to the chart. It is a toy in premise and a proper charting tool in execution.
Requirements
OV-01The application MUST be entirely client-side: static files, no backend, no accounts, no data leaving the browser.
OV-02The application MUST handle exactly one GPX track per session. Loading a new file replaces the current one.
OV-03On first load the application MUST automatically load a bundled demo GPX so visitors see a live, fully-featured chart before uploading anything, with a clear call to action to load their own file.
OV-04The product MUST be polished and public-facing. Visual quality is a requirement, not a nice-to-have; the implementation MUST use the frontend-design skill.
OV-05Desktop is the primary target. Mobile MUST be functional but MAY be simplified.
OV-06All units are metric: kilometres, metres, km/h, min/km. No imperial units anywhere.
OV-10The product name is RunCandles, deployed at runcandles.com, with the tagline “GPX for Traders”. Branding MUST use this name in the site title, header, README and page metadata. “gpxfortraders” survives only as the historical working title of this spec.
Non-goals (explicit)
OV-07Multi-track loading / comparison (watchlists, overlays of several runs) is OUT of scope.
OV-08Sharing and export features (share links, image export) are OUT of scope.
OV-09Serious training analytics (heart-rate zones, training load, comparisons over time) are OUT of scope. This is not a coaching tool.