One route. Every leg.
Tap the trip bar to open the timeline. Select a leg to focus it.
Demo route, no live verification behind it. Ride the Terminal Link train, then continue to the depot.
Verified routing. In development for iOS.
Trip plans that connect the shuttles, terminal walks, and missing links. With the evidence to back them up.
The airport name is only the beginning. The terminal and arrival details help define the first walking leg.
Walk, ride, then take the shuttle. Each connection needs evidence before it can be treated as confirmed.
If a shuttle pickup cannot be checked, that connection stays unverified. Check the operator before relying on it.
The depot is off airport. Its shuttle and terminal walk exist in no route graph.
Maps return a 2 h 4 min perimeter walk, or a drive to a car you cannot reach.
Each leg shows its status. Unsupported connections stay visible and clearly unverified.
01 / The missing connections
Maps route what their graphs contain. Private shuttles, terminal interiors, and informal connectors are often missing.
Laneway is tested against that gap: Pearson Terminal 1 to an off-airport rental depot.
02 / Inside the app
Three parts of one sample plan, visible together. Open the route, inspect a source, and tap the connection we could not confirm.
Tap the trip bar to open the timeline. Select a leg to focus it.
Demo route, no live verification behind it. Ride the Terminal Link train, then continue to the depot.
Tap the evidence row to open the claim, quote, source, and fetch time.
Terminal 1 Link station → Viscount station
10:12 AM to 10:20 AM (estimated)
Board the Terminal Link toward Viscount. Runs around the clock.
Board the Terminal Link toward Viscount. Runs around the clock.
"The wheelchair-accessible train runs 24 hours a day, seven days a week and is completely free-of-charge to ride."en.wikipedia.org - sample fetch: Oct 9, 2026 at 10:00 AM
Tap the shuttle to focus it, then open the claim the app could not support.
Terminal 1 Link station → Viscount station
The operator shuttle leaves from the unmarked post by the station exit; call ahead if it is not there.
No source reachable: the operator site blocked the crawler. This claim is not confirmed.
Interactive recreation of the current iOS route and evidence views using the app's canned offline sample. No live route was requested. The schematic map, timing, and sample source timestamp are illustrative, not travel directions.
03 / Evidence, not estimates
Plausible is not proof. Laneway checks every claim and can return supported, contradicted, or unsupported.
Unsourced facts cannot be constructed. Every source stores its URL and fetch time.
04 / Connections concept
Imagine opening a friend's profile to find the route they saved, photos, and the memories around it. This is a fictional concept. Today's app has a local profile and saved-trip verification, but no connected friends or photo sharing. Osaka is outside current Canada-only route coverage.
Try it yourself: click or tap Connections, then Maya to preview her profile and Osaka trip.
Click or tap Maya to preview her profile and Osaka trip.
This profile and person are fictional. Connections are not available in the app today.
Routes, photos, and the people in between.
Illustrative friend profile
"We followed the lights along the canal after dinner and kept walking just to see what was around the next corner."
"One more skewer turned into a whole extra hour at the table."
The Verified badge is a fictional example of a route whose every leg has source evidence. It does not verify a visit, these photos, or these memories.
Illustrative concept only. Maya, Ren, the Osaka trip, its Verified state, the photos, and the memories are fictional. The photographs were generated for this preview. Laneway currently plans in Canada; Connections, shared photos, and friend memories have not shipped.
05 / In motion
Simulated route feedVaried timing. No route repeats within one hour in this browser.
06 / Building in the open
The next leg starts here.
Verified planning is the foundation. Navigation is the product. Follow the engineering log until release.
Read the dev log