v2.0

[tafelnl]

This plugin is already quite good. But IMHO it still misses a few things to be a full fletched alternative to cordova-plugin-googlemaps in production.

I like to propose the following issues to be added to a possible milestone for v2.0 of this package. I considered a major release tag since some of the changes below are braking to 'old' API.

1. The API should be unified to be completely the same on Android and iOS. At the moment event listeners and API calls have different names on both platforms. They should be the same.
2. (Refactor: Split the Plugin class into smaller classes #8) Plugin classes should be split up in multiple classes
3. Multiple map instances should be possible at once. The point above simplifies this. I already have a working proof-of-concept for Android.
4. (Custom icon marker in SVG #15 & Marker icon not changing #44) Custom marker icons should be refactored to be fully supported and support vectors (and when possible svg's, but I do not think that is a hard requirement).
5. (feat(map): cover map with HTMLElements #84) It should be possible for HTMLElements to overlap the map.
6. Ideally, support for custom info windows is added. It would be even more interesting to support html content as an info window.
7. Documentation should be updated. It should also be more clear. (Add docs using capacitor/docgen #17 & Reverse Geocoding Docs #4) have a WIP on these but slow progress.
8. (Drawings on the map: Ground overlays #2 & Drawings on the map: Tiles #3) Finish drawing methods. Working local prototypes, need to cleanup and push. Could be a part of v2.

When above issues are addressed it is pretty much on par with the cordova maps, I think. Also, point 1, 2 and 3 I am already working on.

What do you think about this? Do you have any other important issues in mind that should be addressed?

__

On a side note: when releasing v2.0, it might be a good idea to change the name to capacitor-community/google-maps. This change addresses possible confusing about "capacitor" being two times in the name. Above all, the omitting of the word "native" opens up possibilities to also support web in the future.

[hemangsk]

Sounds like a plan! I agree with all the points. Thanks a lot for chalking everything out in details.

Documentation should be updated. It should also be more clear.
(#17 & #4) have a WIP on these but slow progress.

Do you have any other important issues in mind that should be addressed?
(#2 and #3) have got working prototypes locally, need to cleanup and push. Could be a part of v2.

👍 big thumbs up on the sidenote, we'll sync with Capacitor maintainers and get the renaming process done. I'm not sure how the npm rename mechanism will be like.

[hemangsk]

@tafelnl , pls feel free to ping me I can assist with anything. Really looking forward to this

[hemangsk]

https://github.com/tiaanduplessis/pkg-rename 😄

[tafelnl]

Progress can be seen here: https://github.com/DutchConcepts/capacitor-google-maps/tree/next

New API proposal: https://github.com/DutchConcepts/capacitor-google-maps/blob/next/API_REFERENCE.md

[J-Gonzalez]

@tafelnl - WIP is looking great! The CustomMapView file with the listeners is 👍 . Just need the setOnCameraIdleListener also added there and I think we're almost golden from my initial look through

[hemangsk]

I tried the vue3 app in examples, looks perfect. @tafelnl can you please create a PR?

Also @tafelnl , could you please consider becoming a maintainer for this plugin? :) We could really use your expertise over here to move this project in a proper direction 🖖

[tafelnl]

Thanks for testing them out @hemangsk ! I'd love to help out with maintaining this plugin. Can you add me as a collaborator?

[selected-pixel-jameson]

Thank you for your work. I would stress that without #5 IMHO this library can't be considered as a production ready solution. #5 should be prioritized above #4 and #3. I have multiple production apps that need #5 implemented before we would be able to use this solution. I would be willing to donate / pay someone to work on getting #5 implemented ASAP.

[DwieDima]

Thank you for your work. I would stress that without #5 IMHO this library can't be considered as a production ready solution. #5 should be prioritized above #4 and #3. I have multiple production apps that need #5 implemented before we would be able to use this solution. I would be willing to donate / pay someone to work on getting #5 implemented ASAP.

@tafelnl i think @selected-pixel-jameson meant the issue #84 which is number five in your top comment list.

[tafelnl]

Ah my bad. In that case I can fully agree. I would be able to finish it. It's just that I am really busy with work. But I will see what I can do.

[ChiKaLiO]

@tafelnl if you can point me in the right direction, i want to help, specially on the svg pointer since i really need it