Back to projectsProject PDF
Event photography software

SnapBooth Pro

A Windows photography workspace, now developed as Photodigi, that connects event organization, photo booth sessions, templates, and finished exports.

Client project · In developmentDevelopment preview · PhotodigiElectron · React · Node.js · SQLite · Sharp
My contribution

Desktop application development for event management, photo capture, editing, template composition, and managed exports.

Interactive demo

Try the browser layout sample. Camera and printer integration are outside this demo.

Product walkthrough01 / 02
An event workspace

Actual development application with synthetic QA artwork and an isolated test event. SnapBooth Pro is now developed as Photodigi; these are not photos or records from a client event.

An event workspace
SnapBooth Pro development dashboard with event overview, recent synthetic capture, templates, and export controls
Try a small part of the workflow

Make a little keepsake.

Choose a layout, set the mood, and add a caption. Then save your composition.

Photo strip in the midnight theme, with illustrative sample landscapes and your captionIllustrative sample artwork
Layout
Theme

600 × 1260 px · PNG

A browser demonstration of template composition. The full desktop app handles captures, event libraries, and exports. This demo uses sample artwork, does not access a camera, and sends nothing to a server.

The workflow, before and after.

The starting problem

An event photo moves through capture, review, editing, layout, and delivery. Unfinished captures need to stay separate from final outputs.

The implemented flow

Organize a test event, capture a booth session, review its images, compose a template, and finalize a managed export. Recovery and explicit finalization keep the steps connected.

Development workflow shown with synthetic artwork and camera fixtures. Actual client event data, physical printing results, and release dates are not published.

The challenge

Event photography moves through capture, review, editing, layout, and delivery. Keeping those steps connected requires preserving originals and making sure each output belongs to the right event.

What I built

  • Event and photo management, Quick Capture, and multi-photo booth sessions with review and recovery.
  • Template composition and a Photo Workshop with editing, layers, saved recipes, and rendered outputs.
  • Managed final exports, a persistent print queue, and customizable desktop workspaces with Light, Dim, and Dark themes.

Key implementation decisions

Protect originals throughout the workflow

The main process owns files and native operations. Capture and template flows preserve source photos while creating separately managed outputs.

Finish a session as one deliberate operation

Unfinished booth photos stay private until finalization. Recovery and retry handling help avoid publishing duplicate or incomplete results.

The result

An integrated development preview for moving event photos from capture and editing to export. Public release and hardware qualification remain pending; physical printing is not presented as verified.