A better first step onto the TMB.
Build a fast, approachable planning companion to Ultimate France’s cornerstone guide. Earn trust with clear effort estimates, transparent coverage and portable plans. The long-term ambition is a bookable itinerary with a verified route, rather than a list of places joined by an attractive line.
What was reviewed
Public product pages from The Hiking Club, its four feature pages, Traileasy’s TMB page and Traileasy’s homepage, alongside Ultimate France’s TMB guide. This is a published-feature and acquisition-journey review. No paid account was purchased, and the authenticated planners, alert reliability and offline navigation were not tested. UX weaknesses below are identified friction or hypotheses, not invented usability-test results.
Competitor strengths → Ultimate France response
| Area | Evidence & limitation | Response in this beta |
|---|---|---|
| Flexible planning | The Hiking Club advertises templates, custom stages, pace adjustments, route variants, transport and itinerary checks. These are valuable benchmarks; published access starts at €79 per season. The entry price may discourage readers who are still exploring. Planner source | Open immediately on an editable 11-day plan. Offer 9/10/11-day starting points, stage combining/splitting, rest days and visible daily effort. No sign-up or payment before exploring. Free access is a positioning choice, not a claim that competitors have no free features. |
| Accommodation | The Hiking Club connects properties to itinerary nights, provides supported-system availability and opening/cancellation alerts, and stores booking notes. Coverage is explicitly limited to supported systems and bookings happen with providers. This leaves a fragmented booking process. Accommodation source | Date-specific records and clear manual statuses. Changed dates retain old bookings separately. No simulated stock, no false alert subscriptions. A coverage-aware availability service remains a later integration. |
| Preparation | The Hiking Club describes human-verified local updates, itinerary-relevant emails, community photos and modelled snow layers. This is a substantial operational strength. Modelled snow still needs local interpretation; a competing product needs ongoing verification, not merely a weather widget. Preparation source | Link directly to official TMB and La Chamoniarde sources, label the absence of live status, and explain route-specific checks. We do not call a source link a live conditions feed. |
| Navigation | The Hiking Club advertises personalised GPX/KML including accommodation approaches, alternatives, transport and useful stops. Navigation depends on a compatible app/device with maps downloaded in advance. Export and map setup are additional steps that first-timers must understand. Navigation source | A portable trip pack and explicit offline checklist. Only waypoints can be exported until a licensed, checked walking track exists. Native turn-by-turn guidance is deferred. |
| Quick-start alternatives | Traileasy’s TMB page exposes 9-, 10- and 11-day examples, camping options, a route map and personalised GPX export. Its broader site promotes web/mobile continuity. These are real strengths: Ultimate France should not assume it will win merely by offering templates. Labels like “relaxed” do not establish suitability for a specific hiker. TMB source · Platform source | Show time and climb beside each day, let users set a comfortable daily time, and flag compressed stages. The templates here are original illustrative partitions, not copied competitor itineraries or GPX files. |
| Official sources | Autour du Mont-Blanc provides route information, conditions and an accommodation directory. La Chamoniarde supplies local mountain information. They are essential verification sources, but are separate from a saved personalised plan. Official TMB · La Chamoniarde | Keep these sources within the planning journey and trip pack, while making the user’s next action explicit. |
The content issue to resolve first
The Ultimate France guide combines lift-assisted and scenic-variant stages with a headline “classic” circuit. In particular, the first stage describes using Bellevue, the Champex–Trient statistics describe Fenêtre d’Arpette, and the Aiguilles Rouges section discusses Lac Blanc. A planner must choose precise trail segments before it can promise consistent totals.
The beta selects a walking-only circuit via Les Chapieux and Alp Bovine, without Tricot, Fenêtre d’Arpette or Lac Blanc. Its approximate totals therefore differ from the article and should not be treated as verified track measurements. The article’s Croix du Bonhomme closure note also makes an automatically preselected overnight there inappropriate without direct confirmation. A local expert should review the route and the guide together before release.
What works now
- 9-, 10- and 11-day full-circuit partitions; stage splits and combinations; optional rest days.
- Dates recalculate throughout the journey. A reservation stays attached to its original location/date.
- Walking-time preference, pace adjustments, long-day flags and a clickable effort chart.
- Overnight booking names, statuses and notes saved locally on the current device.
- Offline HTML trip pack, browser print-to-PDF, editable JSON backup/import and approximate GPX waypoint export.
- Official conditions and accommodation links, route-specific guidance and saved preparation checklist.
- Responsive desktop/mobile layouts; native keyboard-operable controls. No advertising or email wall in the planning flow.
What this beta does not do
It does not optimise against real bed availability, process bookings, send cancellation alerts, synchronise across devices, compute exact accommodation approach paths, fetch live snow or closures, provide surveyed trail geometry, support alternate directions/start points, or perform GPS navigation. GR5, GR54 and GR58 are labelled as future additions. The downloadable pack opens offline; the planner itself is not a fully offline navigation app.
Next release: prioritise data before features
| Priority | Deliverable | Acceptance requirement |
|---|---|---|
| 1 · Route foundation | Obtain owned or licensed TMB geometry, geolocate lodging and approach paths, and commission local route review. | Every segment has provenance, licence, review date, ascent/descent and continuity checks. Exported tracks match selected stages. Confirm refuge openings independently. |
| 2 · Stronger planner | Add overnight alternatives, direction/start options and variants using a route graph. Offer a feasible shorter-stage option when a day exceeds the time preference. | Changing a stop recomputes both adjoining stages. Technical variants are opt-in. Feasibility includes descent, exposure and group limits, not only distance. |
| 3 · Small availability pilot | Partner with a booking system or properties. Start with a clearly named coverage subset and email alerts. | Show party size, room type, provider and last-checked time. Separate unavailable from unknown. Deduplicate notifications; unsubscribe works. Never imply an alert holds a bed. |
| 4 · Conditions service | Define source permissions, an editorial owner, timestamped observations and route/date relevance. | Reports have published/observed/checked timestamps and expiry. Stale or absent reports show “unknown”; closures remain separate from forecast data. |
| 5 · Navigation handoff | Export checked tracks by day and provide a tested offline import guide. Consider native navigation only after route accuracy and offline support are established. | Test actual files in supported apps/devices, including flight mode and missing map data. Never generate straight-line tracks between huts. |
Expand across France
Route content is separated into a route-pack registry in the source, with stable stop IDs, segment metrics, templates and review status. The date, booking and export logic can be reused. Before GR5, extend the engine to handle point-to-point routes and variable segment counts; GR54 and GR58 need their own validated datasets, source links and local guidance. No route should become selectable just because a title has been added.
A durable backend should separate routes/segments, properties/provider mappings, trips/days, reservations, availability observations, alert subscriptions and condition reports. A trip must store the route-data version it used. This avoids silently changing someone’s downloaded plan when editorial data is updated.
Integrate with the cornerstone guide
Begin with a prominent “Plan your TMB” link after the guide’s route summary. Keep the editorial guide indexable. Once the route data is checked and the app is released publicly, host it on an Ultimate France subdomain or embed it below the route overview with a full-screen option for mobile. The current review site is private and cannot serve anonymous blog readers.
Suggested launch model: free planning and saving, with an optional approximately €20 enhanced route pack once there is verified navigation data and meaningful extra value. Keep paid offers out of critical route or closure information. Add disclosed accommodation/gear recommendations where they help a real planning decision; do not optimise overnight routing for commissions.
Measure whether the UX is better
Test with five first-time independent TMB hikers: create a dated plan, identify the hardest day, add a Courmayeur rest day, record a reservation, change the start date, recover that reservation and download the final pack. Track task completion, incorrect assumptions about availability/navigation, time to first usable plan and return-to-plan rate. “Best route planner” is an ambition to validate, not a claim supported by this beta.