Waitlist, reminders or recurring bookings: which problem should come next?

[DimaGutierrez]

Try the public browser demo → — no installation or account required. Bookings, conflicts and the 201 / 409 race are simulated in this tab; reloading resets the examples. The full backend described below uses real HTTP requests and PostgreSQL when installed locally. Demo scope.

SlotGuard v0.1 handles room booking, cancellation, conflicts and an isolated race demo. What would make you use it again next week?

Candidate	Problem	Design cost
A — Waitlist	A full room becomes available later	Fair ordering, expiry and confirmation
B — Reminders	People forget reservations	Delivery, retries and preferences
C — Recurrence	A team books the same weekly meeting	Timezones, exceptions and partial conflicts

These are proposals, not shipped features or promised release dates. The artwork illustrates options.

Choose one and describe the last situation where it would have helped. Another idea is welcome if you explain the user problem.

My pick:
Who needs it:
Concrete situation:
The simplest useful version:

If you want to contribute, mention UI, Python/API, SQL, tests or documentation. Start with the contribution guide. No commitment is needed to comment.

También podés responder en español: ¿qué te haría volver a usar la app la semana siguiente?