Vibe-coding tool stack for a 2-3 hour workshop on shared wifi

Decision. Pick Lovable as the primary tool — chat-only UI, server-side rendering, one-click publish to *.lovable.app, and the only vendor with a real K-12 / no-account classroom track [2] [7] [38] [55]. Keep Bolt.new warm as the backup (faster cold start, no account, but WebContainers hate locked-down laptops and Lovable has logged 314+ outages since May 2025) [4] [5] [31] [71]. Have attendees sign up 24–48 h before the room, off the venue wifi, and bring a phone-hotspot kit. Host budget: ~$0 if you stretch free tiers, ~$50 if you pay for one shared Pro seat as fallback; the per-attendee marginal cost is zero [27] [76].

The recommended stack at a glance

1. Tool shortlist — what survives contact with a non-coder

The 2026 vibe-coding field has six tools you can plausibly hand to a stranger. They are not equivalent.

In a head-to-head non-developer test, Lovable and v0 both shipped a working photo-booth app from a single prompt while Bolt.new failed across six attempts — the camera feature never loaded [1]. One facilitator who has run multiple workshops moved from Bolt to v0 to Lovable as her default classroom tool — non-coder friction was the driver [78]. Lovable’s own docs concede Bolt has the lowest barrier for a complete novice (no account, no config) — but Bolt’s output is also the most demo-grade [4].

The trade. Lovable produces things that look done; Bolt produces things that exist. For a 2-3 h workshop where the deliverable is a working URL to show a friend, Lovable wins; for a one-prompt-and-done warmup, Bolt is the quickest path.

2. Free-tier math — does this break the bank?

Short answer: no, if you plan it. Long answer:

Host-pays math. A solo vibe-coder spends $100-250/month unnoticed [27]. For 20 attendees on Pro for one month, expect ~$500 (e.g. 20 × $25 Lovable). No vendor publishes a workshop SKU — group rates are extrapolated from per-seat. Cheaper paths exist:

• Students (verified .edu). Replit Core: $10/mo for six months [26]. Cursor Pro: free for one year (~$240 value) [21]. Verified educators get Replit free with student credits [25].
• Multi-account chaining. Stacking free credits across alt Google accounts violates OpenAI ToS §4(e) explicitly [24] and equivalent clauses on the others. Don’t.
• Host shares one Pro seat. $25 covers the demo, the room watches the screen, attendees stay on free. Marginal per-head cost: $0.

3. Shared-wifi survivability

The tools split into three bandwidth tiers. Pick by your venue.

The Bolt trap. Bolt’s troubleshooting page admits that ad-blockers, VPNs, and non-Chromium browsers — all common on locked-down work/conference laptops — break the cross-origin-isolation handshake outright [31]. On a slow venue wifi the 30-second boot timeout will fire before the WebContainer initialises, with no partial-load fallback [32] ⭐ 16k. If you bet on Bolt, screen-test laptops before the room.

The venue-wifi reality. 100+ laptops doing previews, npm, Git pushes routinely saturate APs not provisioned for power users; backup hotspot kits are standard event-ops advice now [39]. A teacher’s mobile hotspot used as a wifi-failure fallback is a pattern borrowed from VIPKid-era ESL workshops and still works [76].

4. Signup friction (the silent workshop killer)

Most attendee minutes lost in a vibe-coding workshop are lost at the signup screen, not the prompt.

Shared-NAT hazard. Cloudflare Turnstile escalates challenges on shared-IP wifi; the most common silent failure is device clock skew rejecting the token [50] [51]. On a school NAT, OpenAI returns “too many sessions from 1 IP” and offers no fast support channel [69]. Schools also block ChatGPT at the firewall regardless of the ToS [53].

The 24-48 h pre-flight. Established AI-coding curricula explicitly tell learners to create their accounts 24-48 hours before the room, off the venue wifi, citing 30+ minute downloads and trial-clock concerns [52]. Do this — it’s the single highest-yield mitigation.

Institutional escape hatch. Universities like Harvard front a pre-provisioned “AI Sandbox” that wraps GPT/Claude/Gemini behind SSO, removing every per-student phone/age/payment gate [54]. If your venue has anything similar, use it.

5. Deploy & share — fastest path to a public URL

Every recommended tool has a built-in publish button on free. Use it. Do not route attendees through Vercel/Netlify dashboards on workshop day.

Generic hosts as fallback when you need to migrate the build off the generator:

Cloudflare Pages wins for workshop fallback — unlimited bandwidth means a viral demo can’t bankrupt you [63].

Sharing in the room. Generate one QR per URL with QRStuff or Canva — both free, static, unlimited scans, native iOS/Android camera readable [67] [68]. Display on the projector; attendees scan with their own phones. Don’t email links — captive-portal browsers eat them.

6. Failure modes seen in the wild + mitigations

These keep showing up across multiple host write-ups [73] [78]:

The most consistent cross-host recommendation: keep two tools warm and stay flexible [73]. One facilitator who has run many sessions describes converging on Lovable as default after starting with Bolt and v0 — the friction with non-coders is what drove the migration [78].

7. The runbook (TL;DR for the host)

T-48 h.

1. Email attendees: create Lovable + Bolt.new accounts using Continue-with-Google. Include screenshots [52].
2. Build one reference app in Lovable yourself; save the share URL.
3. Fork a public starter repo (any minimal Vite/React) — backup if both generators fail [72].

T-2 h.

1. Charge your phone. Enable hotspot. Tell venue IT how many SSIDs you need [39].
2. Print 3 QR codes: Lovable login, Bolt login, the workshop’s shared starter repo.

T-0.

1. 10 min: “what does your app do?” — forced planning step, ungoverned by LLM [77].
2. 90 min: build in Lovable. One prompt → preview → one revision prompt. Discourage debug rabbit holes.
3. 20 min: hit Publish. Generate QR. Show your app to the person next to you.

If wifi melts → flip to hotspot. If Lovable is down → flip everyone to Bolt and shorten scope to “landing page”. If both fail → the starter repo plus Claude Artifacts (runs inline in chat) is enough to ship something visible [8].

Total host spend.

• Free path: $0. Lovable + Bolt free tiers cover one app per attendee with no iteration room.
• Comfort path: $25 (one Lovable Pro for the host, attendees on free) [12].
• Insurance path: $50 (Lovable Pro + a Cloudflare Pages-backed static repo).

The $100-250/mo “vibe-coding budget” reported for solo builders [27] does not apply at workshop scale, because three hours of guided activity is well below a single user’s monthly burn.

8. What this report did not answer

• No named-host, dollar-itemised post-mortem of a vibe-coding workshop (“I taught 20 strangers Lovable for $X”) was found — workshop budgets here are extrapolated from per-seat pricing [27].
• No first-person Reddit/HN thread of a vibe-coding workshop killed specifically by conference wifi; the wifi-fail evidence is industry-vendor framing [39].
• Bolt.new’s total first-load weight including npm dependencies is not publicly documented — only the <1 MB WebContainer runtime is confirmed [29].

If you run this workshop, write up your spend, your wifi survival rate, and what broke. Future Scout runs would pick up your post and tighten these numbers.