Latchline

A shared workshop entrance, ready for the next handoff.
Latchline’s workshop overview showing open handoffs, arrivals, resolutions, entrance health, and shift status.
Overview panels highlighting handoffs that need attention and recent workshop activity.
Searchable handoff queue with priority filters, assignment controls, and CSV export.
Event timeline for reviewing and searching workshop arrivals.
Entrance and device status dashboard with simulated battery and connection health.
Team roster and shift closeout showing assigned work and carry-forward notes.
Automation rules for routing deliveries, visitors, and device alerts.
Insights dashboard summarizing arrivals, open handoffs, resolutions, and assignment rate.
Workspace settings for preferences, Ring connection, and demo data.

Inspiration

Shared workshops run on handoffs. A parcel arrives, someone rings the bell, or a vehicle pulls up while the floor lead is busy. Ring notifications tell one person that something happened; the rest of the team still needs to know who should follow up and whether it was handled. Latchline turns entrance activity into a shared operations queue for maker spaces and community workshops.

What it does

Latchline groups entrance events into a practical handoff desk. A package becomes a collection check, a doorbell press becomes a visitor assignment, and a vehicle arrival becomes an expected-arrival log. Teammates can assign an item, mark it handled, and review an entrance timeline. The public demo starts with sample workshop activity; click “Run a handoff drill” to add a new event and try the workflow without hardware.

How we built it

The interface is a responsive HTML, CSS, and JavaScript dashboard. A Node.js server runs the local version. The hosted demo uses a lightweight Worker to serve the app and proxy Ring Playground device and event-history requests. Temporary Ring tokens stay in browser memory and are sent only to the app's API proxy for each request; they are not written to browser storage or disk. A normalization layer maps Ring event types to workshop follow-ups, and the dashboard uses the same queue for simulated and Ring events. The prototype uses event metadata only and does not identify people or store video.

Challenges we ran into

The main design challenge was making an entrance event useful for a team workflow without creating another stream of noisy alerts. We focused the interface on ownership and closure: every item shows a follow-up, a suggested owner, and a clear handled action. We also needed a no-credential demo path so judges can explore the workflow without Ring hardware or Playground access.

What we learned

A useful event integration needs to close the loop after detection. A shared owner, a short explanation, and an explicit handled state make an arrival actionable across a shift change. Keeping sample data clearly labeled lets people explore the idea without mistaking simulation for a live Ring event.