DEV Community: Judexify

Evergreen Sentinel : Know Your Waste Laws Before You Toss It

Judexify — Sun, 19 Apr 2026 15:52:07 +0000

🌿 Evergreen Sentinel — AI Sustainability Auditor

This is a submission for Weekend Challenge: Earth Day Edition

What I Built

Describe any item — a plastic bottle, leftover food, an old t-shirt — and Evergreen Sentinel tells you exactly what to do with it based on your local 2026 waste laws and current weather conditions.

Every audit returns:

A category — Fabric, Food, or Materials
A Comfort/Spoilage assessment based on live local weather
A Circular Action grounded in your city's actual waste regulations

Demo

🔗 Live App

Code

(https://github.com/judexify/evergreen-sentinel)

How I Built It

Stack: React + Vite, Supabase and backboard (auth + persistent state), Groq/LLaMA 3.3 (reasoning), Tavily (real-time search)

On every audit, Tavily fetches live weather and 2026 waste laws for the user's city. Both are injected as context into a Groq prompt which returns a structured JSON audit. All results are saved per user in Supabase with RLS full isolation between accounts.

The key insight: sustainability advice shouldn't be generic. What you do with plastic in Lagos is different from Berlin. The app fetches real, location-specific context every time.

Prize Categories

Best Use of Backboard — user memory (location, eco score, audit history) managed through a getMemory/setMemory interface backed by Supabase

Kettly — A Fully Functional Dashboard Where the Only Navigation Is a Teapot

Judexify — Fri, 03 Apr 2026 00:53:53 +0000

This is a submission for the DEV April Fools Challenge
What I Built
I built a SaaS dashboard.
A real one. Sidebar. Analytics page. Reports page.
A status bar that logs everything in monospace like it means business.
The kind of thing you'd see in a YC pitch deck under "Product Screenshots."
Then I built it again. In 1998.
Kettly ships in two versions — a clean modern SaaS interface and a pixel-perfect 90s recreation styled after early eBay: gray tables, white background, Times New Roman, a hit counter, and a disclaimer that it is best viewed in Netscape Navigator 4.0 at 800×600. Both versions are linked. Switching between them is the second most disorienting thing about this app.
The first is the navigation.
There is one problem with both versions.
The sidebar does nothing. Every single link — Overview, Analytics, Reports — returns 418 I'm a Teapot (RFC 2324). The only way to actually navigate is by holding down a GIF of a kettle for one second. While you hold it, tea pours from the spout. The page changes.
That is the entire navigation system. A kettle. That you hold.
Short-clicking the kettle causes chaos — characters explode across the screen and the status bar says "SHORT CLICK — HTCPCP BREW refused — 418 I'm a Teapot — hold longer." There is no way to stop it. There was never a way to stop it.
When you finally visit all three pages, the UI fades and an 418 I'm a Teapot modal appears. On the 90s version it looks like a Windows 98 dialog box. The OK button does nothing. This was always the plan.
Kettly solves zero real-world problems. It brews nothing.
It is, technically, RFC 2324 compliant. It ships to production anyway.

Demo
The entry screen behaves normally. For exactly four characters.

Type 1–3 characters → nothing happens. Clean. Professional.
Type 4 characters → a Login button appears. You feel safe.
Type a 5th → it falls off the screen into the kettle below
The extra letters keep falling. You cannot stop them.
Click Login → you're in. The voice says "I am a teapot." Immediately. No warning.

The dashboard looks fine. It is not fine.

Status bar boots: BREW / HTCPCP/1.0 → 200 OK
Click any sidebar link → GET /overview → 418 I'm a Teapot (RFC 2324)
Short click the kettle → chaos
Hold the kettle 1 second → tea pours, page changes
Visit all three pages → UI fades, 418 modal appears
Bottom right corner → switch between the 90s and modern version at any time

The 90s version stays frozen at 800px wide, refuses to be responsive, and renders exactly as it would have in 1998. The chaos is authentic.
The modern version redirects you back to the 90s version on reload. You cannot escape the past.

DEMO

judexify.github.io

Code

judexify / kettly

A professional SaaS dashboard that can only be navigated by a kettle. Returns 418. Brews nothing. RFC 2324 compliant. for the Dev.to challange

Kettly — Enterprise Brewing Solutions

RFC 2324 compliant. Brews nothing. Ships to production.

What is this?

Kettly is a fully functional SaaS dashboard that secretly makes no sense.

It looks like a real product. It has a sidebar, analytics, reports, and a status bar that boots with system logs. But the sidebar does nothing. The only way to navigate is by holding down a kettle. Short-clicking it causes chaos. The app ends with an HTTP 418 error and a brief history of why that exists.

Built for the DEV April Fools Challenge 2025 — prompt: HTCPCP IYKYK.

The Joke

On 1 April 1998, Larry Masinter published RFC 2324 — the Hyper Text Coffee Pot Control Protocol — as an April Fools' joke. Buried inside was HTTP status code 418: I'm a Teapot, returned when a teapot is asked to brew coffee.

In 2017, someone tried to delete it…

View on GitHub

How I Built It
Pure HTML, CSS, and Vanilla JavaScript. No frameworks. No libraries.
No build tools. No backend. No real functionality whatsoever.
Two separate HTML files. One deliberately modern, one deliberately stuck in 1998. Linked to each other at the bottom right of every screen including the entry screens, because the joke starts before you log in.
The hardest part of building deliberately bad software is that it still has to work. The dysfunction has to be functional.

The long press — telling a short click from a long press required a setTimeout of 1 second and an isLongPress flag checked on both mouseup and touchend for mobile support. Short press fires chaos. Long press fires the brew sequence and the page cycle. On mobile, the browser's native long-press context menu kept hijacking the interaction — fixed by cancelling contextmenu events and stripping pointer-events from the image element so the browser stops treating it as a pressable asset.
The input — every character beyond 4 is animated falling off the screen via CSS keyframes, then stripped from the input value in JS. The field stays at 4. The chaos around it does not stop. The user did this to themselves.
The 90s version has no media queries. This is intentional. A 90s website was never responsive — it broke on every screen and that was just life. The broken layout on mobile is not a bug. It is the most historically accurate decision in the entire project.
The version switch — the modern version redirects to the 90s version on direct load or reload using document.referrer. You always land in 1998 first. Getting to the modern version requires actively choosing it.
The voice — Web Speech API reads "I am a teapot" the moment you enter the dashboard. No audio files. No libraries. One line of JavaScript. RFC 2324 compliant.

Prize Category
Best Ode to Larry Masinter
On 1 April 1998, Larry Masinter published RFC 2324 — the Hyper Text Coffee Pot Control Protocol — as an April Fools' joke. Inside it was one line: if you ask a teapot to brew coffee, it must return 418 I'm a Teapot. A joke. Nobody thought it would last.
In 2017, someone tried to delete it. The internet revolted.
Thousands protested on GitHub. A website — save418.com — launched in its defence. 418 survived. It is now permanently reserved. Forever.
Kettly exists entirely in his honour.
The app is named after a kettle. The only navigation is a kettle. Every sidebar link returns 418. The status bar opens with BREW / HTCPCP/1.0 → 200 OK. The 90s version is set in the exact year he published the RFC — 1998 — and the copyright footer never changes.
The voice says "I am a teapot" because he wrote a teapot into internet law.
The 90s version exists because he published it in 1998 and the internet never really moved on.
Larry Masinter hid a punchline inside internet infrastructure, watched the world argue about it for 27 years, and won.
Kettly is the least we could do.

Stop DoomScrolling! I Built the Tab I Actually Want to Open.. - Focus.radio

Judexify — Sun, 01 Mar 2026 21:12:11 +0000

This is a submission for the DEV Weekend Challenge: Community

The Community

I know the type because I am the type. I open a new tab to "just focus for an hour" and twenty minutes later I'm deep in a YouTube spiral I didn't ask for. I've got three Spotify tabs open, a lo-fi playlist I've heard so many times it's basically silence, and a deadline that keeps getting closer.

I'm a student pulling late-night study sessions with cold coffee and too many browser windows. I've been the solo developer learning and coding into the midnight. The writer who needs forty-five uninterrupted minutes just to get one good paragraph out and get my thoughts together, I and 4 others most times context-switching between tasks and forgetting what we were actually supposed to be doing.

We have the same problem everyone in my study group at school and developer learning community too . Focus is hard, the internet is everywhere, nothing built for productivity actually feels good to use except the one you build. I needed something that felt like a place. Something I'd actually want to open.

What I Built

focus.radio : a lo-fi focus app built around the way I actually work. I open it and there's music already a lo-fi stream running quietly in the background, a dark ambient interface, a GIF playing behind ,I set an intention before each session. I breathe for a moment. Then I lock in. When the timer ends, I reflect on what I did. Over time it becomes a journal. A record of every late night, every locked-in hour, every project I showed up for. But the feature I keep coming back to is the plant. There's a small SVG plant that lives at the bottom of the app. It starts as a seed. It grows sprout to seedling to young plant to branches to a full flower based on how many sessions I complete. If my streak breaks, it wilts. One session brings it back. Just a quiet little thing that reflects my consistency back at me. My consistency is its water.
Everything it does:

24/7 lo-fi stream with an offline audio drone fallback so silence never catches me
Independent ambient mixer — rain, café, white noise, hearth — runs with or without the radio
Focus timer with Deep, Focus and Drift modes
Custom durations from 25 minutes all the way to 6 hours for the really long nights
Custom session colors — changes the ring, the page gradient, every accent
Work journal with intent and reflection logged per session
Work stats time tracked per project, "locked in" badge when I keep showing up
The plant
Snake + Dino Run for breaks, with a stretch reminder at 5 minutes
Timer survives page reloads — calculates drift and picks up exactly where I left off
Fully installable PWA with lock screen media controls

Demo

https://focus-radio.vercel.app/

Code

judexify / focus.radio

A minimalist online radio and productivity app streaming lo-fi beats to help you concentrate, reduce distractions, and maintain workflow momentum. Includes focus timers, micro-break games, motivational prompts, simulated live listener counts and a plant that grows with your consistency.

This project was bootstrapped with Create React App.

focus.radio

A quiet place to do your best work. Lo-fi radio, ambient sounds, focus timers, a work journal, and a plant that grows with your consistency.

Features

Radio + Ambient

24/7 lo-fi stream with offline drone fallback
Independent ambient mixer — rain, café, static, hearth
Ambient plays without the radio. Radio plays without ambient. Both have their own controls.

Focus Timer

Three modes: Deep (90m), Focus (50m), Drift (25m)
Custom durations from 25 minutes up to 6 hours
Custom session colors — change the ring, gradient and page accent
Breathing ritual before every session
Sessions survive page reloads — timer keeps running even if you close and reopen the tab
Distraction shield for Deep Work mode (fullscreen lockout)

Work Journal

Every session logged with intent and reflection
Partial sessions saved automatically if you end early
Grouped by day with total time…

View on GitHub

How I Built It

No backend. No database. No account required. Everything lives in the browser and on the device.
Stack:

React 18 + Zustand for state : with persist middleware for the journal and streaks
Framer Motion for every animation : transitions, plant sway, ambient pulse
Tailwind CSS for the dark, minimal aesthetic
Lucide React for icons throughout
Web Audio API : all ambient sounds are generated programmatically. Rain is pink noise through a bandpass filter. Café is brown noise. Fire is pink noise with an LFO tremolo. Static is flat white. No audio files, no network required for ambience, it always works.
Web Workers : the timer runs entirely off the main thread, immune to tab throttling
localStorage : timer state saved on every tick with a timestamp. On reload: newElapsed = savedElapsed + Math.floor((Date.now() - savedAt) / 1000). If the session finished while the tab was closed, it clears cleanly. If not, the worker boots with the corrected value and picks right back up.
Media Session API : lock screen controls on iOS, Android and desktop
Service Worker : PWA with cache-first for assets, network-only for streams
Claude helped me think through architecture decisions and debug edge cases, the drift calculation, the AudioContext lifecycle fix, the plant stages.