While I love the photo tagging feature in Gramps Web, I think the photos should be represented as they are by default, without any additional overlays.
Here’s how the person outlines should work in my view:
-When media file is opened, person outlines should be hidden.
-When hovered over with a cursor, person outlines for a single person is shown
-When toggle switch turned on, all person outlines are visible.
-Similar function for photo display view with black background.
I see your point, but I disagree in almost all regards, sorry
I don’t think outlines should be hidden by default. This makes them almost useless IMO as many users will not be aware of the small button to unhide them.
Hover-only features are absent on mobile. I agreed to add this in the lightbox view after the user intentionally clicked the hide outlines button. But this cannot be the default.
When you click on the image, it opens full screen with the option to hide the outlines and to download it. I don’t see the point of duplicating this functionality.
How about “being shown” be default but 2 sets of 3 radio button for showing outlines and labels:
Outlines: show all, show Active Person, show none
Labels: show captions (below), show № (inside), show none
I understand your points, but let me offer counter arguments
First, as a subjective point, when I open a photo, I want to see the actual photo before any overlays, however helpful they might be. I want to see my ancestors without any digital metadata tagged onto them. There is a reason why for example Google Photos doesn’t open photos with rectangles drawn on top of faces. It would be bad design, frankly.
With all respect, I think that’s backwards thinking. The issue with discoverability of a feature shouldn’t be solved by enabling it by default, especially when it drastically changes how the primary content is presented. The problem could be solved by having descriptive icons, buttons with text (like for text recognition), tooltips, onboarding tutorial, subtle visual cue on the corner of the photo etc. You could also have a list of all people under the photo, with a button to highlight them.
I understand that, but it is still possible to turn them on with a single click, or be revealed by tapping the faces. Having to figure out how to disable them is the bigger issue here, not how to enable it. This problem is even worse when viewed from small screens, so it would make even more sense to have them hidden.
IMO having to click twice makes it even harder to disable them. Having to do this just to see the photo without them is frustrating, why not show the photo as it is the first time user opens it? The point would be the ease of use no matter if the photo is opened full screen or not.
You made your opinion clear and I am open to it. But if you start labelling other people’s views or preferences as “bad”, I am less motivated to listen, honestly.
I think it’s quite obvious that this is a question of personal preference, and I am happy to collect other user’s views in this thread.
The problem could be solved by having descriptive icons, buttons with text (like for text recognition), tooltips, onboarding tutorial, subtle visual cue on the corner of the photo etc. You could also have a list of all people under the photo, with a button to highlight them.
I’m open to having a feature request with some mockups (but the solution most be design, not documentation - I know my relatives are not reading it anyway ).
I suppose everything in design comes down to preference in the end, but I’m just pointing out if this was done by Apple or Google, it would be taken back real soon. It’s not a personal attack, but I apologize it came out that way.
I can put up some mockups if I find the time. Thank you for considering this.
I can imagine it’s a bit frustrating when the original intended audience doesn’t engage as hoped.
Do you have any upcoming family gatherings/reunions? Perhaps you could take a portable Gramps Web running on that Raspberry Pi with a WiFi local net hotspot? So family could have hands on exposure to sharing with it? And give you feedback (from personalties you know) about what grabbed their interest or pushed them away.
Perhaps print a QR code to help get to the login with their smart phones?
Perhaps they do, but the reason for hiding the tags by default would be the same from UX perspective. I feel they are an intrusive element, but I agree with you that I probably made my point clear already. I should also make clear that I love the general design of the Gramps Web, I’m not trying to prove otherwise.
).
I should also make clear that I love the general design of the Gramps Web, I’m not trying to prove otherwise.