Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Crowned is a small digital side project with one rule: only one person holds the spotlight at a time. When someone takes the throne, everyone else sees the change live, and when that person is dethroned, their message is kept in a Hall of Fame. The project’s author, publishing as “Lazy coder” on DEV Community, names Next.js 16 and Supabase Realtime as the stack behind it.
What Crowned is
Crowned is a real-time “King of the Hill” experiment. Its defining constraint is exclusivity: at any given moment, one user occupies the throne. The author describes the core interaction in the launch announcement, posted to DEV Community on September 19, 2026 (the year is inferred from the publication context), and the project is presented as a digital side project rather than a commercial product.
The rules of the throne
The announcement states the mechanic in one sentence, which is worth reading exactly as written:
“Only 1 person holds the spotlight at a time, and when dethroned, your message is saved forever in the Hall of Fame.”
#1 Best Overall
Two things follow from that wording. First, the spotlight is a single slot, so taking the throne means displacing whoever holds it. Second, the displaced user’s message is archived rather than deleted. The “1” in that sentence describes the product rule, not a measured performance figure.
Taking the throne
The author’s pitch centres on the moment of takeover. The announcement asks readers for feedback on “the real-time throne takeover animation” and whether “the transition feel[s] smooth on your screen.” That is a request for impressions from visitors, not a report that the animation has been tested across devices or browsers.
Rank #2
The Hall of Fame
The Hall of Fame is the project’s record of past holders. A dethroned user’s message is stored there, which turns each takeover into a permanent entry. The announcement does not describe how entries are displayed, moderated, paginated, or removed, so those details should not be assumed.
Recommended Free Tools
The stack: Next.js 16 and Supabase Realtime
The author names Next.js 16 for the web application and Supabase Realtime for live updates. Supabase Realtime is the component that pushes changes to connected browsers without a page refresh, which is why it fits a single shared state like a throne. The announcement names the stack but does not publish the code, the database schema, or the exact channels used, so the way these pieces interact inside Crowned is not established by the primary source.
Inspiration
The author cites The Million Dollar Homepage as an inspiration. That site, a well-known early-2000s experiment in selling pixel space, shares Crowned’s idea of a single shared canvas that visitors compete over and that keeps a record of contributions. The comparison describes the concept only; the two projects share no code or mechanics beyond that.
What is and is not established
- Established by the launch post: the King of the Hill premise, the one-holder rule, the Hall of Fame archive, the stated Next.js 16 and Supabase Realtime stack, and the Million Dollar Homepage inspiration.
- Not established: performance, latency, scalability, user counts, traffic, or any monetization plan. The announcement gives no figures for any of these.
- Not confirmed: the architecture. A later secondary article discusses broadcast and database-change approaches to this kind of app, but those are general patterns that the author’s announcement does not confirm for Crowned.
- Availability: the project is referenced at crowned.wtf. The primary announcement page could not be checked for this article, so whether the site is live, and how it behaves today, should be verified directly before relying on it.
General real-time options for similar apps
The following are general techniques for shared, live state in web apps. They are not confirmed as the mechanisms Crowned uses.
| Approach | What it does | Fit for a single-throne app |
|---|---|---|
| Broadcast channel | Sends an event to all subscribers on a named channel when a client sends one | Good for announcing a takeover instantly to every viewer |
| Database change subscription | Notifies clients when rows in a table are inserted or updated | Good for keeping the current holder and Hall of Fame entries in sync with stored data |
| Polling | Clients re-request state at a fixed interval | Simplest to build, but slower to show a takeover and more requests than push-based options |
A common design for a single-slot app combines a stored record of the current holder with a broadcast on takeover, so that a late-arriving visitor can load the current state and live viewers receive the change immediately. Any takeover system also needs a rule for two users claiming the throne at nearly the same moment; the announcement does not say how Crowned resolves that race.
Why the project is worth watching
Crowned is a clear example of a shared-state web experiment built on a modern stack. Its appeal is the constraint: one slot, one holder, and a permanent record of who held it. Readers interested in the project should treat it as an announced concept whose implementation details are still unpublished.
Quick Recap
“
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
