Lines with multiple destinations get totally whacked

[remulasce]

Some lines, like the 720 or Blue Line, have multiple eventual destinations, but serve most of the corridor together.

In-app, they're shown as totally different trips, even though most people don't care which they take.

I don't have a good way to fix this. The official Go Metro, and other, apps don't do any better a job either.

Possible Solutions:

• Some specific functionality to combine destinations, eg. long-click allows you to combine trip items into one.
• Option to add stop by line instead of by destination. Eg. checkbox lets you condense all destinations of a single line into one.
• "Begin + End" trip item, which goes and finds every line that goes from one specified stop to the destination, and displays it in one place.

  Short-term Mitigation:

• For the "When's the next bus coming" use case, we could bring back the priority-based-on-arrival-time ordering of trips. It used to be confusing when first introduced, but having just the tiniest bit of priority could at least put the first bus on top.

[nighelles]

This seems like an issue where the core problem is what information you're actually looking for, and if theres a good way to get that info quickly. If you wanted to do smarter logic, you basically need where they intend to go, which slows down your whole high speed low drag bus app thing.