You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
With the upcoming mobile SDK releases, we're adding support for runtime styling. This adds capabilities as adding layers, sources and changing underlying properties dynamically. One thing that we haven't updated with these capabilities is our (point) annotations API.
Underneath the public API, our annotations API is using a SymbolLayer and a source with id com.mapbox.annotations. We should be able to leverage changing a couple of the symbol properties dynamically and expose some of them as an public API.
Exposing these properties will allow gl based annotations to be on par with view based annotations on terms of public API. For me, view annotations should be a lost resort solution when gl based markers don't fulfil the requirements. For every other case, users should use gl based markers instead.
Since the possibilities are allmost endless what to support as a basic API,
I would try to have parity with Google Maps and expose the following for Android:
Capturing from #1734 (comment) that this isn't a priority. Noting that this feature would allow us to support the same API as ViewMarkers ( we can advice to only use ViewMarkers for very limited cases) and it would allow us to have parity with Google Maps SDK. Closing for now.
With the upcoming mobile SDK releases, we're adding support for runtime styling. This adds capabilities as adding layers, sources and changing underlying properties dynamically. One thing that we haven't updated with these capabilities is our (point) annotations API.
Underneath the public API, our annotations API is using a SymbolLayer and a source with id
com.mapbox.annotations
. We should be able to leverage changing a couple of the symbol properties dynamically and expose some of them as an public API.Some examples:
Exposing these properties will allow gl based annotations to be on par with view based annotations on terms of public API. For me, view annotations should be a lost resort solution when gl based markers don't fulfil the requirements. For every other case, users should use gl based markers instead.
cc @jfirebaugh @mapbox/mobile
The text was updated successfully, but these errors were encountered: