Case Study: Comparing Two Lanes or Route Sections Objectively

Public beta

App Store availability will be defined soon.

Drivers often know that one lane, one street, or one route section feels worse than another.

The problem is proving it clearly and repeatably.

This is where Road Survey becomes useful.

The practical question

You want to know:

which lane is smoother?
did resurfacing or patching actually improve the road?
is one route section rough enough to justify avoiding it or documenting it?

These are exactly the kinds of questions that subjective memory handles badly.

Why this matters

A rough section can affect:

comfort
equipment vibration
recording quality
repeatability of route testing

If you compare by memory only, the result is weak. Traffic, speed, and expectation all distort the judgment.

Best tool

Use Road Survey .

It is the right engineering mode when the real question is not mount quality, but surface quality.

Road Survey is built to compare:

lane A vs lane B
before repair vs after repair
one route section vs another
one repeated run date vs another

Example comparison

A simple first test:

Run 1: right lane on a known rough section
Run 2: left lane on the same section

Keep these stable:

same vehicle
same mount and phone position
similar speed
similar traffic conditions if possible

Only the lane should change.

What Road Survey tells you

Road Survey helps you compare the complete result of each run.

The most useful first reading order is:

Overall score
Impact score
Stability score

Practical reading model:

worse Impact score usually means harsher bumps or stronger defects
worse Stability score usually means more persistent roughness through the run
if both get worse, the section is likely meaningfully rougher in real use

Example decisions this enables

This kind of test helps you decide:

which lane gives the smoother ride
whether a resurfacing job actually improved the section
which route is better for sensitive cargo or recording
whether a road-quality complaint has measurable support

Why this is persuasive for users

This use case is easy to understand immediately.

It shows that the app is not only for hobby experimentation. It can be used to document road conditions, route quality, and repeatable before-and-after comparisons with a phone users already have.

Good result patterns

What you see	What it usually means
Better overall score and lower impact severity	The compared lane or section is meaningfully smoother
Similar impact but worse stability	The section may be broadly rougher, even without a few standout hits
Better scores after resurfacing	The repair likely improved the real ride quality
No clear difference	The sections may be closer in quality than expected, or the test conditions varied too much

Recommended workflow

Use Road Survey on one reference section.
Repeat the run on the second lane or section.
Save both sessions with clear labels.
Compare the scores and report.
Re-run if traffic or speed conditions were too different to trust the first result.

Who this is for

users comparing daily routes
municipal or maintenance users checking repairs
drivers documenting rough sections
testers who need repeatable route-quality evidence