Show HN: Bigwords.page – Turn any screen into a sign. The URL is the app

Original Article ↗ Hacker News Discussion ↗

A small web app called Bigwords.page lets users turn any browser-equipped screen into a simple sign, with the entire message and settings encoded in the URL fragment so no backend, accounts, or storage are required. Commenters praise the elegance of using the URL as state for things like conference timers, ad‑hoc signage, accessibility for deaf users, and kiosk displays, and compare it to similar “app-as-URL” tools for sharing text or files. Some critique the marketing-style tagline (“The URL is the app”) as sounding AI-generated or imprecise, while others see it as a natural evolution of minimalist, URL-driven web utilities.

Overall reception

  • Many commenters praise the idea as “simple, crisp,” “brilliantly simple,” and true to “do one thing well.”
  • People like that it’s static, free, no login/account, no backend, and very fast via caching/CDN.
  • Several note it’s the kind of tool you rarely need but is perfect when you do.

Design & architecture

  • Message and configuration live entirely in the URL fragment, so the server never sees the content and there is no storage.
  • The fragment effectively acts as argv/state for a static web app.
  • Fonts are shipped with the site and loaded only when needed. Wake Lock API is used to keep screens on.
  • Works well for kiosk / digital signage scenarios and fits nicely with Chromium-in-kiosk-mode setups.

“The URL is the app” / LLM-speak debate

  • A substantial subthread disputes the tagline “The URL is the app.”
    • Critics say it’s technically wrong (URL is state, not the app) and reads like AI/marketing copy (“LLM-ish,” “corpo-speak”).
    • Others argue it’s just normal slogan-style phrasing and that “LLM apophenia” (seeing AI everywhere) is overblown.
  • There is broader discussion about AI-written prose:
    • Some strongly prefer imperfect human English over polished LLM text.
    • Others think LLMs are fine for helping non-native speakers, but may erase personal “voice.”

Use cases & anecdotes

  • Proposed for conferences, cafes, countdown timers for panels, classrooms, game-night scheduling, and digital signage generally.
  • Deaf users find it useful for showing large text to communicate in noisy/voice-only contexts.
  • People mention using similar tools to warn drivers, order drinks in crowded bars, or prank unlocked laptops.

Related projects & patterns

  • Multiple similar tools are linked (big text displays, parameterized pages, file-in-URL sharers, game state in URLs/QRs).
  • Several commenters celebrate the broader “app/data in the URL” pattern as privacy-preserving and host-cheap, with no server to leak.

Feature requests & improvements

  • Desired: TV apps (Google TV/Apple TV), better PWA manifest, on-screen fullscreen/rotation controls on mobile.
  • Requests for less intrusive Open Graph preview image and ways to hide or neutralize rich previews in messaging apps.
  • Suggestions for optional base64 or compression of message content to hide jokes, and richer QR-code controls or data-URL export.

Bugs and technical notes

  • A layout bug in Firefox is reported (scrollWidth vs clientWidth with trailing spaces); a fix/workaround is shared.
  • Some minor SSL/blocked-site reports appear but are not deeply investigated.

Accessibility and safety

  • Concerns raised about flashing/epilepsy-inducing styles, referencing prior “big message” sites.
  • Questions about legality/safety of using such displays on cars; considered a potential moderation nightmare if networked.