OhSnap!

OhSnap! is a photo booth for events, built for a Windows 11 machine that has to survive a night of strangers pressing things. It boots full-screen into an idle loop with the operator's own logo and prompt, waits for whatever has been mapped as the shutter, counts down with a tick and a flash, composites the shot at full camera resolution and offers keep, retake or print before returning to idle for the next guest.

Press anything

The input layer is the part most booths get wrong. OhSnap! takes keyboards, gamepads, MIDI pads, serial devices and HID burst typers — the button boxes that "type" a word and press Enter — and binds any of them the same way: open the inputs panel, press Bind next press, then press the thing. Every action can carry any number of bindings, a binding can be told to require a half-second hold so a knock can't fire the camera, and a keyboard binding can go global so the shutter works even when the window isn't focused. A running list of every press the app hears — bound or not — makes "the button does nothing" a thirty-second diagnosis at a venue rather than a phone call.

Their brand, not ours

Idle screen, subject box, frame, watermark and text are all set as percentages of the screen, which is what makes the preview honest: the saved photo uses the same numbers as the wall. Backgrounds accept a live camera, a still, a looping video or a flat colour, swapped mid-event as soon as nobody is mid-snap, with blur and dim to push a live feed back behind the guest. A whole look can be exported as a preset and loaded on the next machine.

Nothing on screen the guest can break

There is no menu on the stage. The admin hub, cameras, backgrounds, inputs, branding, output, gallery and diagnostics are each a key chord, quitting asks first, and Alt+F4 does nothing in kiosk mode. The operator guide is one printable page of chords and recovery steps, because at a venue the fix has to be findable by someone who isn't the person who built it.

Offline at the venue, honest about the installer

The app works with no network — photos land in a folder the operator chose and can find, with no account, no cloud and no product key. The installer is deliberately unsigned, so rather than pretend otherwise the site documents the entire "unknown publisher" path: the browser's download warning in Edge, Chrome and Firefox, the SmartScreen box, what Defender may do, and the SHA-256 to check the file against. A code-signing certificate is a real cost; explaining four screenshots is not.

The release path

A single command bumps the version, tags it, builds the Windows installer in CI, publishes it and redeploys the site — which is a Go binary with its templates and assets embedded, behind nginx and systemd, serving the download behind a password with the version, date, size and hash rendered from the release itself. The changelog on the site is the changelog in the repository.