IssueTracker

# WARNING: DO NOT INCLUDE YOUR API KEY OR CLIENT ID CREDENTIALS
# It is OK to share your API Project ID, but _not_ API keys.  

Feature Request
-----------------------
What would you like to see us add to this API?

I have spent the last 8 to 9 months developing an app for android and ios that relies on google maps and it's ability to draw shapes. One thing I have noticed is the lack of consistency between the android and the ios sdk. It is super important that user experience is consistent no matter which platform is being used. I would like the code to be more consistent as it helps when viewing code on one platform and converting it to the other. For example: There is no GMSMutablePath() object for android but there is for ios. The android equivalent would be HashMap<LatLng>. This creates an inconsistency in the code which makes it difficult when there is just one person working on both platforms. Code is the least of my worries right now as it's function is possible to be consistent. One thing that is not possible to be consistent though, is the visual aspect. In the documentation it says that when adding holes to polygons, if the hole is not encapsulated by the polygon, then the polygon is rendered without any fill.
https://developers.google.com/maps/documentation/android-sdk/shapes#create_a_hollow_polygon

On the ios version, this will not happen which is the behavior im looking for.  On my ios app, I am creating polygons with a semi transparent green color, and when adding holes, I am filling in those holes with a semi transparent red color and there are no underlying lines from the green polygon showing through under the red polygon. On the android version, I am forced to just overlap the polygons which mixes the two transparent colors together and reveals the lines underneath. I feel as if there are two different teams working on each platform and there is little to no communication when it comes to small details like this. You encourage consistency between platforms in your material design guide, yet there is no work-around for this inconsistent behavior with google maps. I would like to see more consistency in future updates ^_^

Explain your use case for that feature:

I would like my user to be able to outline their whole yard to be mowed and then outline parts of their yard they don't want mowed (houses, sheds, walkways, etc) so the back end can give them an accurate price based on the amount of actual yard to be serviced. On Android,  If I add holes and the hole is not encapsulated within the polygon, then the polygon becomes unfilled and ruins the visual aspect, so I have no choice but to forget about adding holes and just overlap polygons.