Our PracticeTeamPricingConsultingInvestorsGet Started
← All Field Notes
November 1, 2026 Β· by Ravlunar-cloverlive-opstelegramniimbotworkshop

Shipping mid-event: a workshop where the site changed under everyone's feet

During a live herbalism workshop we added a Telegram Mini App, a pay page, a label printer driven by a phone, and a rotating print-authorization QR. All of it went in mid-event. The site never went down, and the only thing guests noticed was new features appearing.

The setup

Lunar Clover ran "Tea & Recovery", a hands-on essential-oil blending workshop. On the sign was a static page with blend cards, shown on the Duo. The day started with a pre-flight check of the site. Then the requests kept coming while guests were in the room.

What changed, live

  • Mobile admin over Telegram. Winter needed the admin backend without a VPN. Telegram's signed Mini App launch data now gives her and Rav a short-lived admin session, and everyone else gets a welcome page.
  • Scan to pay. A QR on the sign opens a four-option page: Tea, Workshop, a $5 Bonus Kit, and "Make your label".
  • A Launchpad as the sign's remote. Each pad opens a card's zoom view, and the pad stays lit red while that card is open.
  • Guests print their own labels. A guest fills in a form on their phone. A worker drives Winter's own phone over USB, types into her saved NIIMBOT label template, and prints. The guest page shows their place in the queue and says "Printed!" when it's done. The template is never saved, so every job starts from the same point.
  • Print Authorization. A small QR in the sign's header rotates every two minutes. A guest has to scan it to print, so only people in the room can send a label.

Why nothing broke

  • Every change was staged first, then swapped in as one file at a time. Each file had a snapshot taken before the edit.
  • Backend restarts take about a second, and the pages fail soft. If the QR can't fetch its code, it simply hides.
  • New routes were added beside existing ones and changed none of them.
  • Each fix was verified on the real device: phone screenshots, Caddy headers checked with curl, and a real test print.

Lessons

  • A grid's visual order isn't the DOM order. Hardware mapping follows the DOM.
  • A security-headers snippet beat a local override until the override was deferred. Check headers, don't assume them.
  • An accidentally unplugged phone survived because USB debugging authorization and the stay-awake setting persist. We checked rather than assumed.