It causes to have inconsistency of behavior between platforms, but also the flyTo is jankier than the easeTo, leading to degraded performances (that I did observe on mid-end Android devices). Since the zoom level changes back and forth during the animation, the map has to be redrawn if it crosses the threshold between plane and globe projections, or if it crosses the zoom level where different tiles resolutions are used.
Since both methods are exposed on native libs, could we expose them as well on the Flutter side instead of forcing the use of flyTo exclusively, and leave to the user the possibility to select the type of animation they prefer ?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
As of now, on Web and Android,
animateCamera
relies on the nativeflyTo
implementation, whereaseaseTo
is still used on iOS, base on the following issue : https://github.com/flutter-mapbox-gl/maps/issues/1097It causes to have inconsistency of behavior between platforms, but also the
flyTo
is jankier than theeaseTo
, leading to degraded performances (that I did observe on mid-end Android devices). Since the zoom level changes back and forth during the animation, the map has to be redrawn if it crosses the threshold between plane and globe projections, or if it crosses the zoom level where different tiles resolutions are used.Since both methods are exposed on native libs, could we expose them as well on the Flutter side instead of forcing the use of
flyTo
exclusively, and leave to the user the possibility to select the type of animation they prefer ?