Future feature ideas & backlog

[merlin1de]

Collection of feature ideas for future consideration. No commitment on timeline or implementation.

---

Folder statistics

A small summary badge when browsing folders: "12× ★★★★★, 3 Picks, 2 Rejects" — useful for getting a quick sense of a folder without opening it.

Fullscreen mode (Chrome/Edge only)

Browser-native Fullscreen API for Grid + Loupe + Slideshow — escapes the Nextcloud chrome (header, sidebar) so the gallery fills the entire screen, ideal for client presentations on a big display.

Design (orthogonal axes):

• F toggles fullscreen on/off, regardless of current view (Grid, Loupe, or Slideshow).
• Esc always means "Loupe → Grid", regardless of fullscreen state.
• The two are independent: leaving fullscreen never closes the loupe; pressing Esc never toggles fullscreen.

Why Chrome/Edge only: the model requires the Keyboard Lock API (navigator.keyboard.lock(['Escape'])) so our Esc handler still fires inside fullscreen instead of the browser swallowing Esc to exit. Keyboard Lock is supported in Chrome and Edge (HTTPS). Firefox and Safari don't support it — there, Esc in fullscreen would exit the browser-level fullscreen first and then a second Esc would go to the grid (two-step). To keep the model truly clean and avoid double-paths in code, the feature is feature-gated: if navigator.keyboard?.lock is missing, the F shortcut and button are simply hidden. No fallback logic, no degraded UX leakage.

Implementation sketch:

• Call requestFullscreen() on the Gallery root so both Grid and Loupe benefit.
• Track state via document.fullscreenchange event.
• Add an F keyboard shortcut + a small button (icon-only) in both Grid and Loupe.
• On enter: navigator.keyboard.lock(['Escape']) + optional navigator.wakeLock.request('screen') for client-presentation no-sleep.
• On exit: release Keyboard Lock + WakeLock.
• iOS Safari: button hidden anyway because Keyboard Lock isn't there.

Bonus: wake-lock is most valuable here — long slideshow on a tablet at a client meeting won't have the screen sleep.

NC Files integration (sidebar)

Set ratings directly in the Nextcloud Files sidebar without opening StarRate. Would make StarRate feel more native to NC and reduce context switching.

Mobile selection via long-press

Long-press (~500ms) on thumbnails to enter multi-selection on touchscreens (no modifier keys available). Standard gesture from iOS/Google Photos.

Mobile-optimized batch bar is a separate question — current bar might be sufficient, but worth revisiting if mobile usage grows.

(Moved from #14)

---

Ideas that don't fit elsewhere can be added here as comments.

[merlin1de]

Comment indicator in grid view

When a photo has a comment, show a small 💬 icon in the top-right corner of the thumbnail (mirroring the pick indicator top-left). Requires a batch API endpoint to check comment status for multiple file IDs efficiently — deferred for now.

Reactive comment state (Pinia store)

Comments currently load when opening the Loupe and the state is lost when going back to the Grid. A central Pinia store would keep comment indicators in sync without a full reload — write a comment in Loupe, see the indicator in Grid immediately. No WebSocket needed, just a local reactive cache.

Makes most sense to introduce when a second store use case comes along (e.g. shared filter state), not just for comments alone.

Desktop: inline comments in Loupe

On desktop there's enough space to show comments directly alongside the image while swiping, without requiring an extra click. Mobile stays with the current button/sheet approach. Responsive split: desktop inline, mobile sheet.

[merlin1de]

Email when a guest finishes rating

Right now the photographer has to actively check the share log to see whether the client has been through the gallery. A small notification email after a guest session wraps up would close that loop.

Something like:

Anna has finished rating "Wedding Müller" — 24 picks, 8 rejects, 112 images reviewed.

Trigger (to be refined)

• Inactivity after a clear rating burst (e.g. 30 min since last rating in that share)
• Or explicit session close (tab closed, logout)
• Not instant — a short buffer avoids coffee-break false positives

Open questions

• Opt-in per share, or a global photographer preference?
• Rate limit: one mail per session max, not per rating
• What counts as "finished enough" to mail about — all images touched, or any meaningful activity?
• Mail language: follows the photographer's locale, not the guest's

Not urgent, not scoped yet. Parking the idea while it's fresh.

[merlin1de]

Metadata-driven filtering & sorting (EXIF)

Today, sorting is name | date | size (a global preference) and filtering is rating | color | pick. A broader direction: treat photo metadata — capture time, camera/lens, ISO, rating, and other EXIF — as first-class axes for both filtering and sorting.

The natural pairing matters here: you can't yet filter by capture time or use rating as a sort key, so adding just "sort by rating" in isolation would be a lone bolt-on that doesn't fit the current global-preference model. Better to think of filter + sort over the same metadata set as one theme.

Scope is deliberately open — this can stay small (add rating to the existing sort) or grow large (a real metadata query/sort UI, possibly an interactive control instead of a global default). No design yet; parking the theme.