What I Built

HTTP 418 — I'm a Teapot is the definitive web experience for the most important HTTP status code ever written.

In 1998, Larry Masinter published RFC 2324 — the Hyper Text Coffee Pot Control Protocol — and declared, with the gravity of a standards body, that any teapot asked to brew coffee should return 418 I'm a Teapot. The world wasn't ready. The world is still not ready. But now, at least, there's a proper frontend for it.

This app lets you:

Send BREW and STEEP requests with custom headers via a Postman-style request panel

Order tea from a full HTTP status code menu (each status has its own blend)

Watch an animated SVG teapot pour in real time

Generate thermal receipts for your tea orders

Customize your teapot with colors, patterns, and accessories

Unlock 10 achievements for dedicated tea enthusiasts

View a full RFC 2324 Compliance Dashboard (A+ rating, naturally)

Upgrade to Pro Tier for $418/month — the only appropriate price point

Coffee requests are firmly, politely, and RFC-compliantly refused.

Code

arnoldwender / http-418-teapot

The ultimate HTTP 418 'I'm a teapot' experience — brew tea, refuse coffee, honor RFC 2324. Built for the DEV April Fools Challenge 2026.

🍵 HTTP 418 — I'm a Teapot

The ultimate HTTP 418 "I'm a teapot" experience — brew tea, refuse coffee, honor RFC 2324.

Built by Arnold Wender

🚀 Live Demo

Features

Animated SVG teapot with pouring animations
Full HTTP status code tea menu — each status has its own blend
Interactive brew timer with steam effects
Thermal receipt generator for your tea orders
Teapot customizer — colors, patterns, and accessories
10 unlockable achievements for dedicated tea enthusiasts
Sound effects for brewing, pouring, and sipping
Confetti celebrations when you unlock achievements
Coffee requests are firmly and politely refused (as per RFC 2324)
Postman-style Request Panel — send BREW and STEEP requests with custom headers and tea parameters
RFC 2324 Compliance Dashboard — full compliance report with an A+ grade (naturally)
Fake Changelog — version history of increasingly elaborate tea-related protocol updates
Pro Tier ($418/month) — premium brewing features at the only…

View on GitHub

How I Built It

Built entirely on a road trip to the Ostsee — from my phone, no laptop, just Claude and a mobile browser.

I used Claude (Anthropic) as my AI coding partner throughout the entire build. No desktop IDE, no local dev environment — just prompts, iteration, and a lot of trust that the code would work when I finally got home to deploy it.

The actual stack:

React 18 + TypeScript — because even a teapot deserves type safety

Vite — fast builds for a fast brew

Tailwind CSS — utility-first, just like a good cup of tea

Framer Motion — smooth pour animations and transitions

Web Audio API — brewing, pouring, and sipping sound effects

canvas-confetti — celebrations when you unlock achievements

html2canvas — thermal receipt generation

Lucide React — icons

Proof that you don't need a computer to ship something. You just need a bad idea, a long drive, and an AI that doesn't judge you for spending a road trip implementing RFC 2324.

Prize Category

Best Ode to Larry Masinter 🫖

This entire project exists because of RFC 2324. Larry Masinter co-authored a joke protocol in 1998, it accidentally became an IETF standard, and 28 years later developers are still implementing it. HTTP 418 survived multiple attempts to remove it from the spec. It has its own save418.com movement.

This app is a proper tribute: a full HTCPCP-compliant frontend, a $418/month Pro Tier, a Postman panel that actually sends BREW requests, and an uncompromising refusal to serve coffee under any circumstances.

Larry, this one's for you. ☕❌🫖✅

DEV Community

I Built an HTTP 418 Teapot App from My Phone on a Road Trip (RFC 2324 Compliant)