Summary
When a user indexes a large photo library, PictoPy can detect a significant number of unique face clusters. While the detection itself is working correctly, the current layout displays every face collection in a single expanding section.
As the number of detected face clusters increases, the Face Collection component continues to grow vertically, pushing the tagged image grid further down the page. In large libraries, this can become a usability issue where users may initially believe that only face collections are being displayed and that no tagged images are available.
Current Behavior
- Every detected face cluster is rendered in the Face Collection section.
- The component expands indefinitely as more clusters are detected.
- The tagged image grid is pushed far below the visible area.
- Users with large libraries need to scroll significantly before reaching the images.
Expected Behavior
The Face Collection component should occupy a fixed amount of vertical space regardless of how many face clusters exist.
One possible implementation is:
- Display only 2–3 rows of face clusters at a time.
- Paginate the remaining clusters within the component.
- Provide Previous / Next arrow controls (or similar navigation) to switch between pages of face clusters.
- Keep the tagged image grid visible without requiring excessive scrolling.
Benefits
- Prevents the Face Collection section from dominating the page.
- Keeps tagged images immediately visible.
- Improves the experience for users with large photo libraries.
- Maintains access to all detected face clusters without overwhelming the layout.
Notes
The exact UI implementation is flexible. Pagination, horizontal sliding, or another compact navigation pattern would all achieve the same goal, provided the Face Collection component maintains a reasonable and consistent height.
Summary
When a user indexes a large photo library, PictoPy can detect a significant number of unique face clusters. While the detection itself is working correctly, the current layout displays every face collection in a single expanding section.
As the number of detected face clusters increases, the Face Collection component continues to grow vertically, pushing the tagged image grid further down the page. In large libraries, this can become a usability issue where users may initially believe that only face collections are being displayed and that no tagged images are available.
Current Behavior
Expected Behavior
The Face Collection component should occupy a fixed amount of vertical space regardless of how many face clusters exist.
One possible implementation is:
Benefits
Notes
The exact UI implementation is flexible. Pagination, horizontal sliding, or another compact navigation pattern would all achieve the same goal, provided the Face Collection component maintains a reasonable and consistent height.