Feedback

This page lists feedback received on the Grivel Photo Archive App.

• I typed in “T-Shirt” as the keyword, and the search results returned 53 results. However, the results were rendered in a way that it’s showing 3 pictures in a row on my phone. The last row ended up with only 2 photos and a blank spot. In my mind, because of that blank spot, I thought that this is the end of the search results but instead, there’s a next page. Then I realized that it’s because you’re returning the first 50 (even though you did mention it in the search results page), and that’s why you’re not filling in the last spot.
  Eric: Makes sense, never thought of that. Long-term, the list should probably be an infinite scroll rather than visually paginated. Short-term, putting a button/link "Next Page" after the last result would probably help in the thumbnail view. In fact, the first thumbnail could be a "Previous Page" button if that would be appropriate.
  Added previous and next buttons in release 0.91.0.
• Search: On my phone, I’m more used to typing in a keyword and then when I hit enter, it will perform the search. Any additional filtering will be done on a filter page. So when I typed in the keyword and there’s no search results, I realized that this is a multi-field search and I have to hit the “search” button on the screen in order to execute the search.
  Eric: I will investigate how that would work.
  Supporting the “Enter” function on the Search page in release 0.91.0.
• If you browse the photos, the photos are listed one by one from top to bottom. (Try 2024). Then I clicked the top one from the list. Then my mind was thinking that since this is the first one, there would be next. However, when I clicked the “next” button, I was told that this is last. So then I realized that it’s because the initial list was sorted in descending order so I needed to click Previous to get to the previous pictures, not next.
  Eric: I understand the problem, but I'm not sure what to do about it. For those who come to see the most recent photos, sorting in descending order makes sense, but maybe it shouldn't be?
  Not addressing this feedback at this time.
• The cache label is really taunting me. I have no idea how the number goes up, and my natural inclination is to clear the cache. There’s no explanation to what that is.
  Eric: that's really for debugging and I should probably remove it, or at least put it under a preference, off by default.
  Added a preference in release 0.91.0.
• Eric: Observed: when a person doesn’t match any existing names, the search returns everything, without a warning that there is no match. That’s not really nice…
  Eric: it's a bug. Searching with a person name and no other criteria should say something about the person not being found. Searching with a person name AND other criteria should say that the person wasn't found, and the results without the person are shown.
  Actually, I changed the requirements. The “explain” on the Search page now explicitly states that searching for a non-existent person will return all photos in the archive. So the bug now becomes a feature. There is definitely a need to make the person search more useful, by being able to select a person from a list.
  Updated documentation in release 0.91.0.