organicmaps
organicmaps copied to clipboard
organicmaps
Basic POI info pane (place page) takes too much space
Here it takes two lines. It used to be just one line before the addition of the share and close buttons.
E.g. in this case I select the POI just to know the approx distance towards it. Its important to see as much map as possible still.
Any ideas how to reclaim this "wasted" space?
Caused by #6776 and improved by #7145 Can you share coordinates of guest house?
@Jean-BaptisteC almost any nameless POI will do, e.g. 41.860873, 2.664371
I like the proposition of @Misalf-git
Move the blue arrow is not a good idea, some users touch the middle of place page to close it. I'm afraid user touch arrow when he want close place page. But I will see to reduce again margin of buttons. And on little device, title can be take more height if blue arrow is moved at the middle.
Move the blue arrow is not a good idea, some users touch the middle of place page to close it. I'm afraid user touch arrow when he want close place page.
Good point! But the "share" and "close" buttons should create a similar mis-tap issue? But looks like they don't. I think users will quickly recognise that tapping on the blue arrow does something else and they'll re-learn to tap on the POI title instead.
Also currently tapping on the title/middle of the place page first expands it, then the second tap closes it.. I don't know if this behavior is as intended, but I find it a bit confusing...
Indeed, I only had screen estate in mind.
After playing with the place page to see where I might imaginarily mis-tap, I don't really see a problem, though. Expanding/Closing the pp is possible by swiping up/down (incl. over buttons) and by tapping the (possibly partially unused) title area.
In theory, I agree that "more map" is better than "large button size" if the latter claims space that's otherwise usable for infirmation.
- Moving the same controls dynamically depending on a title length is a bad idea for muscle memory.
- Share and close buttons are now also used by Google, not only by Apple. So it's a familiar pattern for many, and it doesn't make sense to change it.
Some other ideas are needed...
- Moving the same controls dynamically depending on a title length is a bad idea for muscle memory.
Well e.g. we change positions of bottom bar buttons depending on their number... Doesn't seem to be an issue there, although these buttons are used frequently and their position is fixed vertically (so some users might to "blind" tap them indeed). Whereas the top line of the PP (which is sensitive to closing/expanding taps) could appear at different vertical positions (depending on PP contents) and hence a user will have to look at the screen anyway to make a tap.
Your case is not a main case. In your case you have just the type of POI not a name. In the most of case, we have his name, his type, his address -> In this case by default we have 3 lines used to show information
One line is a common case for selections via a long tap
- related to https://github.com/organicmaps/organicmaps/issues/7691
And two lines (title + subtitle) is a very common case and it doesn't look good still
The gap between the share/close buttons and distance / direction arrow is too big
Upd: screens are from the current master as of March 25.