Built a Flask + Vue prototype and deployed to a cloud server. It validated the workflow but hit a heavy network dependency wall.
💾
Nov 2025
Attempt: Nuitka packaged app
Tried shipping the Python backend as a packaged app. Size bloat and runtime deps made it hard to run on regular member devices; laptops were inconvenient to carry.
🚀
Dec 2025 – Present
Refactor: Tauri local application
Rewrote the backend in Rust, built with Tauri v2. Achieved high performance, zero external deps, and fully offline on Windows/Android.
Use Cases
Comic conventions / offline events
Network
LAN only (phone hotspot works)
Data Storage
Local (exportable to Excel)
License
MIT · Free forever
🚫 Why did we build Booth-Kernel?
We tried many approaches running a fan club booth and hit these pitfalls.
📝
Paper-based bookkeeping
Error-prone math: Bundle pricing is hard to calculate under pressure; even calculators slow you down.
Inventory mistakes: Juggling cash, handover, notes, and stock marking leads to errors quickly.
Hard to review: Messy notes make post-event reconciliation and analysis painful.
🌐
WeChat/Alipay mini-program ordering
Network dependent: Convention networks are complex; heavy assets often fail to load fast enough.
Complicated setup: Certification and configuration are high-friction; every event needs fresh forms.
Split ecosystems: WeChat and Alipay payment/data are not interoperable — fragmented experience.
Poor visibility: Mini-program QR codes are easy to miss; customers can’t find them.
☁️
Web-based booth system (early attempt)
Data risk: Centralized servers are sensitive in multi-club contexts; product and sales data must stay private.
Complex deployment: Cloud servers, domains, HTTPS — unfriendly and costly for non-tech users.
Offline failure: Server or network issues can halt your booth entirely.
✅ Our answer: Local app + LAN sync
Booth-Kernel centers on local data + LAN synchronization: enable phone hotspot, connect devices, and collaborate — rock solid even offline.
📶 Offline LAN architecture
No internet needed. Turn on phone hotspot (no data usage) → connect devices → sync instantly.
⚡ Workflow built for vendors
Order → Confirm → Fulfill; the system automatically deducts stock, logs sales, and generates reports.
🎨 Easier for customers to order
Tablet as "digital menu": big images, clear pricing, quick ordering — less friction and crowding.
🔒 Data stays under your control
No centralized cloud. Data stays on your devices, with one-click Excel export for review.
🔄 How does it run on-site?
Two devices are enough for a full workflow; multiple tablets/phones scale easily.
Order alerts · payment confirmation · picking guidance
🎨 UI Preview
Two landscape shots (customer/statistics) and one portrait (vendor).
Statistics: revenue, best sellers, and stock changes at a glanceCustomer: large images + self-service cart + QR paymentVendor: order alerts, payment confirmation, and picking prompts
Make selling fun again
Let the system handle the tedious parts — keep the passion for fans.
