Full-stack application
QueueLess Pulse.
A virtual queue system connecting customers, staff, business owners, and reception displays.
01 / The context
A problem worth solving.
A queue is shared state. Customers need clear ticket progress while staff and owners need consistent, permission-aware controls across multiple services.
02 / My contribution
The engineering underneath.
Built role-specific React interfaces over Flask APIs, with tenant-scoped memberships and service assignments. PostgreSQL service-row locks serialize ticket issuance and queue actions to keep concurrent operations consistent.
Implemented features
- QR entry and customer ticket tracking
- Staff call, complete, and skip actions; customer ticket cancellation
- Owner management and reception displays
- Role checks, database constraints, and event history
The actual interface
Inside the system
Follow the thinking.
Explore a source-based interaction study. No live data, AI calls, or transactions.
Join the queue
A customer enters through a QR flow. The service issues a waiting ticket; service-row locks serialize competing queue actions.
Illustration of documented behavior
Read the complete flow as text
- Join the queue · WAITING
A customer enters through a QR flow. The service issues a waiting ticket; service-row locks serialize competing queue actions.
- Call next · CALLED
Staff call the next waiting ticket. A service cannot call another while it already has a CALLED ticket.
- Complete service · COMPLETED
Staff complete the called ticket. The event history records the transition; skip and cancel are separate supported paths.
04 / Scope & boundaries
An honest account of the scope.
Development project with synthetic demonstration data. No claim of clinical readiness or production healthcare use. A hosted demo is not linked until its availability is verified.
Read the implementation.
The repository contains the source and supporting context for this project.
View on GitHub (opens in new tab)