New answers tagged

1

I would recommend the reverse of what you described. Instead of having a button that allows you to scroll, show a static map, as Brett East described, with a caption/button of something like "Press to Open". In order to control the map, the user can press (or long-press) on the static map, which links to a new view with full-screen zoomable/draggable map ...


1

The solution might be having pinch to zoom option(with two fingers) for maps. When one finger is used only page scroll should happen. Most mobile users I came across uses one finger to scroll and pinch(with two fingers) to zoom. This may also be a better solutin http://stackoverflow.com/questions/15327783/enable-scrollwheel-zooming-on-a-map-upon-click-using-...


0

I completely understand the problem that you have, it can me quite common on mobile devices. My recommendation would be to not add the padding down the right, and instead make the map not drag or zoom on scroll at certain widths or for touch devices. Here is a link to a good article on the matter https://coderwall.com/p/pgm8xa/disable-google-maps-scrolling-...


0

One key question I think of would be relevance. Why should it be relevant to a user to submit that information? What is the benefit for the user to do it? I would guess that identifying the user perspective on this would help you understand how to approach these two groups. What is the motivation to use the app? Another question: How do you tend to remind ...


0

This is what I generally do: User interacts with the map (mousedown) -> set zoomable Mouse rests on the map for over 1 second -> set zoomable Mouse goes out of the map -> set not zoomable This usually gets the work done. When the user is in the mindset of scrolling the page, the map follows. When the user wants to zoom in/out they need to interact ...



Top 50 recent answers are included