Two people open the same class. Both screens say one spot left, both tap Reserve, and both get a confirmation. Each app read the counter, saw space, and wrote its booking before the other write landed. Disabling the button after the first tap does not help, because each phone only knows about its own button. Running the transaction from the Flutter client is the wrong place too: the client would need permission to write the shared counter, and anything that can write it can set it to whatever it likes. Put the check and the claim in one Firestore transaction on a trusted server, which reads capacity, refuses the request when it is full, and otherwise creates a hold and increments the counter in the same commit. The retry is the easy part to miss. Give each attempt a request ID generated once on the device, so a replay returns the original hold instead of taking a second seat. https://www.duskolicanin.com/blog/flutter-firestore-transactions-limited-capacity

The retry part is the bit people miss. Generating the request ID once on the device is a neat way to avoid a second seat.

The Last Postman of Tomorrow began with one Victorian-era plate of a passenger pigeon, [ARCHIVE / MUSEUM NAME, ARTIST, YEAR, Public Domain]. I turned that single image into a Recraft Style and asked what an extinct messenger would deliver if it were still flying today. The same pigeon, in the same hand-colored print style, now carries a sealed letter through a Victorian post office and then across a modern world of phones and laptops, objects its original illustrator could never have imagined. The idea is a message that travels through time: the medium keeps changing, but the pigeon, and the need to be heard, stay the same. Every object is generic, with no real brands or logos, and a short animated film follows the pigeon from the 1800s to today.