-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WatchOS Support? #12
Comments
The original Mapbox SDK from which MapLibre SDK si forked did not have support for WatchOS. We will not implement it now. |
This PR is updating the version of this image's parent (`bionicbase`) to keep this image (`maplibreglnativeprivate`) up-to-date. It will be merged if all tests pass via `/merge-skip-owners`; if tests do not pass, it will require manual intervention. For more details please see the [docs about Automatic Updates](https://docs.lyft.net/eng/provisioningdocs/learning/automatic_updates.html). [Here is what's changed in `bionicbase`](lyft/containers@3681888...0c41080). REVIEWS WERE BYPASSED
* Fix performance when adding many individual markers to map * Thread-safe `postUpdateSource` * Replace lambda with explicit anon class We still seem to be on java language level 7
Any updates on watchOS support? Thanks! |
@robertgreso MapLibre Native focusses on real-time rendering of vector based maps. I think the existing apps for the WatchOS use raster maps with some simple vectors graphics on top. You could render with MapLibre Native on the phone and stream that to the watch, but it is out of scope for this project. If Apple were to support Metal on watchOS, that would change things. But since Apple Watches already struggle with battery life, I doubt that will happen any time soon. |
Hi, have you considered to add the support for WatchOS? I think it would open a gigantic market of outdoors the possibility to use vector maps on the Watch.
The text was updated successfully, but these errors were encountered: