Running an event All guides ▾
Open / on the display, share /snap with guests, and keep /control on the host’s phone or laptop. The display keeps its own connection; closing Control does not stop it.
The TV remote
| Button | What it does |
|---|---|
| OK | Opens the full-screen spotlight |
| OK, held | Starts a photo call; hold it again or press Back to end it early |
| Left / right | Steps through approved photos |
| Back | Closes the spotlight; press twice on the wall to exit |
| Play/Pause, or Alexa | Pauses or resumes the slideshow (“Alexa, pause”, “Alexa, play”) |
| Next / Previous, or Alexa | Steps to the next or previous photo (“Alexa, next”) |
| Menu (demo mode only) | Shows the next theme |
A photo call fills the screen for a minute: the join QR, a mission (your categories in turn) and a countdown. Photos still need your approval; the call counts the ones that reach the wall.
After a fresh install, the media keys and Alexa start working from the second launch of the app.
pnpm remote provides the existing local developer remote for a connected TV.
The Control panel
Unlock /control using the administrator passcode configured during setup. The old /admin address redirects here.
- Review waiting photos individually: approve or remove them.
- Open the on-wall list to remove an approved photo.
- Pause slideshow holds playback. Close uploads stops new guest submissions. These are separate persisted switches; neither deletes photos or ends the event.
- Start a photo call starts a one-minute photo call on the Fire TV app (the browser wall doesn’t have one).
- Open the display and follow the fullscreen guidance on that device.
- Copy the guest link or scan the basic guest QR, which points to
/snap. - Lock the panel when finished.
Presentation, branding and categories live in the configuration. This page has no settings designer, bulk editor, AI controls, print designer or recap tools. Older stored presentation overrides are preserved by the current compatibility API; see the upgrade note in Customising before changing an existing installation.
Privacy and safety
Manual approval is the default. A self-hoster may explicitly configure autoApprove for a trusted event. The standalone API has no automated photo reviewer; older review settings explains how to upgrade saved data safely.
Guests must confirm consent. After sending, they can remove that photo from its confirmation screen. Reloading, leaving the page or choosing “Add another” loses this browser action; it is not a restored personal photo history. Hosts can still remove photos from Control. Retention cleanup follows configured retentionDays, except photos marked keep through the API.
Pending photos require signed media access. Administrator requests require the passcode, and repeated wrong attempts are rate-limited. See abuse protection for upload validation and limits.
Before guests arrive
- Configure the event and deploy your own stack.
- Unlock Control and verify playback and upload intake are open as intended.
- Scan its guest QR with another device, submit a test photo, approve it and observe it on the display.
- Test pause/resume and upload closure separately.
- For a long event, perform a representative run on the actual screen and network. See the Vega OS notes for the recorded platform observations.