twocentstudios

> There are just so many considerations to navigation when you're not in a car, mixing modes, and know the city and system pretty well already.

Yes! This is exactly the niche I'm trying to solve.

You mentioned 4 or 5 different routing considerations I'd never have been able to predict. And I'm sure anyone you ask could add another couple to the list.

I'm hoping that Eki Bright hits that sweet spot between too much and too little creative freedom in helping the user solve the problem of getting from A to B in the way that works best for them.

> Maybe one suggestion I could think of, would be a risk score.

I like this idea a lot. If I were to do a full-featured routing app concept using an API to get route proposals, I think it'd be possible to supplement each proposal with a risk score the way you describe.

> The main thing I get from Google Map's estimates is an indication that something has changed.

Great point here.