Service request list isn't properly explained

[remulasce]

https://www.reddit.com/r/LosAngeles/comments/2x1wws/my_app_metros_mobile_app_is_too_slow_mine_is_fast/cp3g634

User didn't realize that the request list was holding currently tracked stops. He thought it was a history / quick suggest thing, which is actually a good idea.

The current tutorial text- "Add stops in the field above"- explains how the input box works, but it is located in the stops list. In contrast, the "Predicted arrivals show up here" tutorial, located in the trip list, explains what the trip list will do.

So we should change the request list tutorial to actually describe what is happening in that element. Then, use the hint text on the input bar to describe what that does.

Example text: Input hint: "Type a stop name" Request list tutorial: "Stops that are being tracked show up here" Trip list tutorial: "Realtime arrivals to the stops above are displayed here"

Contributing factors:

• Request list isn't visually differentiated in any way.
• All tutorials end once a stop is added and predicted. So there's nothing explicitly showing how to add additional stops, which would show the use of that list.
• It's not obvious that each Trip has a different stop heading. Especially since some destinations read like stop locations, you can't really tell that the top line is supposed to be a location.

[remulasce]

Additional tutorial tuning.

"Add a Stop" "Currently tracked stops are listed here" "Realtime arrivals to the stops above are shown here"