Taking a book and bringing it back

The main loop of the product. No account anywhere in it. 1

passerby, no account curator, signed in the system

passerby Standing at the box. Scans the QR code taped inside the lid
↓
system Opens that box's page, no sign in asked for
↓
passerby Taps the title they're holding, then check this out
↓
passerby Offered a reminder. Types an email, or skips it 2
↓
system Flips the copy to out, stamps the date, shows it to everybody immediately
↓
only if they gave an email
Sends the receipt, which is really just a put it back button they can keep.
↓
system Two weeks later, one nudge. That is the last email, ever
↓
passerby Puts the book back, taps I put it back from the email or re scans the lid
↓
system Back to on the shelf. Logs it in coming and going, with no name attached

The ways it actually goes

Four branches, and every one of them ends somewhere defined. 3

takes it without scanning anything
The list is wrong until the curator notices a gap on the shelf and taps mark out, or until it turns up back in the box and nobody ever knew. The most common path by far.
brings it back without tapping
Same thing in reverse. The copy reads as out for weeks, then the curator sees it on the shelf and marks it in. The reminder email is the main defense against this one.
never comes back
Sits as out, rolls past a few weeks into the red, and eventually the curator marks it gone from the dashboard. No fee, no email, no record of who.
keeps it four months, then returns it
The I put it back link never expires, so the copy goes from gone to on the shelf. Every state in this product is reversible for exactly this reason. 4
design prototype, nothing here actually works. read the reference · press ? for settings
Prototype settings

0 notes on this page. h hides them, ? opens this.



Full written reference