Improve ways to discover the trip planner inputs

[devinbraun]

There doesn't seem to be a way to discover the trip planner and its origin/destination inputs without searching for an address first or long-clicking on the map, which isn't obvious. Other methods could be added after searching for a stop ID, for example, or clicking on a stop on the map and begin with "Directions to here/from here".

[aaronbrethorst]

@devinbraun I totally agree! Question for you, though: did you see a tip appear when you first launched the app that pointed at the search box and told you to tap on it to plan a trip?

[devinbraun]

@aaronbrethorst Honestly, I didn't remember, but I just reinstalled and did get the message.

[flash1729]

@aaronbrethorst a tip does appear at the first launch of the app as expected.
currently annotated pins are dropped on 2 scenarios -

1. whenever a user clicks on any already present Map Feature(such as clicking on any park, school etc), after details view related to that is dismissed then a new pin is dropped there.

This is kind of unnecessary as that place is already marked in the maps so no need for a user to drop new pin there and in case if someone wants to plan a trip from that Item then that is already covered in MapItemView overlay(which includes Plan A Trip button). In my fork I edited it so that when use clicks on any MapFeature then no new pin will be dropped.
(Do let me know if some other functionality is expected)

2. after long press is detected at any point then also a pin is dropped and the thing about that is at one time we are only tracking a single pin in private var userAnnotation: MKPointAnnotation? so when user long presses again then that previous pin is not stored anymore to use.

I am thinking of storing all the dropped pins in an array along with storing an MKMapItem related to them so that on each click it does not need to reverse geocode to get details related to that point/pin(which is happening rn).
We can integrate this newly created pins array in Trip Planner as in when user is selecting 2 locations(start and end) to plan trip amongst then along with favourites we can also include the list of currently dropped pins which would make sense in making multiple pins.