For me the missing capabilities are :
- listener for pin/marker tap (exists now but is unstable/unreliable)
- separate listener for a bubble on top of marker tap
- method to show/hide bubble
- ability to insert icon and/or button inside bubble.
- So the bubble listener should respond to overall taps in the bubble while a separate listener should respond to the icon/button inside the bubble.
- More consistent map tap behavior across IOS & Android. Currently Android bubbles don’t disappear unless you tap X on them while IOS markers disappear when you tap on another marker or an empty spot on the map etc. If I had wishlist #3 I could make Android markers disappear when I get a listener call for a new marker.
I’m sure you could put in a lot more bells & whistles using direct access to native map api but for my current app the items listed above are causing me the most grief. I would of course prefer CL to fix the mapView implementation but I don’t hold my hopes high on that.
@nmichaud, how about you? I bet most of the above will apply to your project as well. Anything else you identified as a need?