Hello !
On Android devices, native mapview seems to be lagging when starting to move/zoom the map.
On IOS this issue doesn’t appear.
Does anyone has encountered this bug and have some solutions ?
Thx,
Hello !
On Android devices, native mapview seems to be lagging when starting to move/zoom the map.
On IOS this issue doesn’t appear.
Does anyone has encountered this bug and have some solutions ?
Thx,
It is like that on Android. If you use it on more powerful Android devices, then the problem is less prevalent. Try not to load many pointers on the map as it will make the ‘lag’ worse.
It could be also due to some third party maps installed on the Android OS that utilizes Google Maps (like some older models of Samsung).
You can try out the Google Maps using webView
In an other webview in our app, without google map but with a simple page with text, buttons … it seems to be lagging too
If my memory serves me correctly on Android native.newMapView is implemented as a webView already. There is a good reason for this. Amazon made devices do not include Google Play. The Google Maps SDK requires Google Play be installed on devices. Back in the day when Nook’s were popular and the both went the way of a customer Android without Google Play, the only way we could implement maps in a Cross-platform manner was through a webView. Today, this is still an issue with Amazon’s devices.
While mapViews are on our roadmap for the next three quarters, I don’t know how feasible making it work native on non-Kindle devices and do webViews on Kindles.
Rob
It is like that on Android. If you use it on more powerful Android devices, then the problem is less prevalent. Try not to load many pointers on the map as it will make the ‘lag’ worse.
It could be also due to some third party maps installed on the Android OS that utilizes Google Maps (like some older models of Samsung).
You can try out the Google Maps using webView
In an other webview in our app, without google map but with a simple page with text, buttons … it seems to be lagging too
If my memory serves me correctly on Android native.newMapView is implemented as a webView already. There is a good reason for this. Amazon made devices do not include Google Play. The Google Maps SDK requires Google Play be installed on devices. Back in the day when Nook’s were popular and the both went the way of a customer Android without Google Play, the only way we could implement maps in a Cross-platform manner was through a webView. Today, this is still an issue with Amazon’s devices.
While mapViews are on our roadmap for the next three quarters, I don’t know how feasible making it work native on non-Kindle devices and do webViews on Kindles.
Rob