Venue requirements and station branding
Who is this for
Section titled “Who is this for”Sales people agreeing terms with a client, and the operator preparing the site.
- On site: a tablet with a front camera in a modern browser, a stand, a power socket, stable internet with a backup, and even light on the guest’s face.
- The station page must be opened over HTTPS — the camera does not work otherwise.
- Branded: the station screen — colours, background and logos. Not branded: outfits, the stickers themselves, the pack title.
- Internet and power at the venue are the client’s responsibility; agree it explicitly.
- Brand materials are needed about a week ahead, because changing the station’s look is a code change today.
Requirements at the venue
Section titled “Requirements at the venue”| Item | Requirement | Why / source |
|---|---|---|
| Tablet | Front camera; a current Chromium-based browser that can run in kiosk (full-screen) mode; charger connected all day | The kiosk is a web page using the browser camera API. The project’s own checks render it at 1280×800, 800×1280 and 1920×1080, in both orientations. No specific tablet model is prescribed by the code. |
| Stand | Camera at face height; stable; the guest stands about an arm’s length away | The on-screen tip asks for the whole face in frame, with hair and ears visible. |
| Internet | Stable Wi-Fi or wired-to-Wi-Fi for the tablet plus a mobile hotspot as backup | The tablet talks to the server for every step. If the connection drops, the kiosk shows “no connection” and keeps retrying. |
| Guests’ connectivity | Mobile data or guest Wi-Fi that reaches Telegram | The guest scans a QR code and uses a Telegram bot. |
| Power | One socket for the tablet charger; a second for the hotspot | A full event day. |
| Space | Room for the stand and a short line that does not block a passage | The guest spends about a minute at the tablet. |
| Light | Even, soft light on the face; no strong back-light or spotlight straight into the face | Overexposed photos shift skin tone; the pipeline compensates only partly. |
| Background | Any; nothing is required behind the guest | The stickers are drawn, not cut out of the photo. |
| Staff | One person near the station at peak times | Helps guests scan, handles “my pack did not arrive”, can reset the screen. |
Nothing is installed on the tablet. The operator opens the station address on the API domain, allows the camera once, and switches the browser to kiosk mode.
Who provides what
Section titled “Who provides what”| Party | Provides |
|---|---|
| Client / venue | Space, power, internet, access for set-up and rehearsal, a contact person on the day |
| Our side | Tablet and stand (unless agreed otherwise), the station set-up and branding, the bot, the rehearsal, monitoring and support during the event |
“Internet and power on site are the client’s responsibility” is item 5 of the project’s risk register. Write it into the agreement instead of assuming it.
How many stations
Section titled “How many stations”One station handled a pilot of about 70 guests. As a planning figure, one station serves roughly 40–60 guests per hour — an estimate from “about one guest every 60–90 seconds”, not a measurement. Ask when guests arrive in waves and size for the peak hour. Details and formulas: Capacity.
Branding
Section titled “Branding”What can be branded
Section titled “What can be branded”| Element | How it looks | How it is done today |
|---|---|---|
| Station colours, background, typography | The whole kiosk screen follows the event’s brand book | A brand layer of styles and images in the product repository; a developer adapts it |
| Event logo at the top of every screen | Present on all station screens | Mark-up and styles in the kiosk page; a developer changes it |
| Two logo slots in the footer | Organiser and partner logos | Transparent PNG files placed in the kiosk’s static folder and deployed |
| Light or dark variant | Two themes of the same brand | A server setting; the light variant is also available at its own address |
Preview on any laptop before the event: the station address accepts a ?preview=<width>x<height> parameter that
shows the screen in a frame of the tablet’s size.
What cannot be branded
Section titled “What cannot be branded”- Outfits. Six catalogue outfits: teal bomber, business suit, denim jacket, black hoodie, cream sweater, burgundy dress. A new catalogue outfit is possible with lead time — see Outfits, templates and art styles — but branded clothing, logos on clothing and props are not offered.
- The stickers. They carry no logos, text or frames; the prompts forbid them.
- The pack title and the bot name. Fixed per installation.
- The art style. One style per installation; guests do not choose.
What we need from the client, and when
Section titled “What we need from the client, and when”| Material | Format |
|---|---|
| Logos | Vector, or PNG with a transparent background |
| Colours | Brand book or hex values for background, accent and text |
| Fonts | Font files with a licence that allows web use, or permission to substitute |
| Texts | Only if the event needs a different name on the start screen |
Timeline used for the pilot: brand materials about a week before the event, a code freeze a few days before, then a rehearsal on the final build. Later changes are limited to server settings.
Language
Section titled “Language”The bot and the station speak Russian. For an Uzbek- or English-speaking audience the texts must be translated and tested before the event; treat it as a separate preparation item with its own lead time. See i18n.
Rehearsal
Section titled “Rehearsal”A rehearsal on site, or with the final tablet and connection, is part of the service: the full guest journey from Start to a delivered pack, on the real network. Checklist: Event playbook.
Where to go next
Section titled “Where to go next”- Client FAQ.
- Event playbook — the operator’s checklists.
- Multi-tenant and white label — the limits of branding in detail.
Last verified: 2026-11-13 against ai-sticker-pack@b715418 and ai-stickers-landing@e350ff5.