The latest articles on DEV Community by David Ivanda (@davidivanda). https://dev.to/davidivanda https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3989710%2F4f8bc908-1718-4f64-acad-a67da0797f2e.jpg https://dev.to/davidivanda en David Ivanda Wed, 17 Jun 2026 19:51:48 +0000 https://dev.to/davidivanda/i-built-a-fastest-click-wins-platform-because-drawing-names-from-a-hat-isnt-fair-g9a https://dev.to/davidivanda/i-built-a-fastest-click-wins-platform-because-drawing-names-from-a-hat-isnt-fair-g9a <h2> The problem </h2> <p>For years I had a recurring problem at work. When equipment gets <br> written off — laptops, phones, gear — it's often still in great <br> condition and more people want it than there are spots available.</p> <p>I tried everything:</p> <ul> <li> <strong>Drawing names from a hat</strong> — people would "accidentally" draw again when no one was looking</li> <li> <strong>A shared spreadsheet</strong> — easy to manipulate, timestamps unreliable</li> <li> <strong>First come, first served</strong> — whoever lobbied hardest won</li> </ul> <p>None of it felt truly fair. So I built a solution — for myself.</p> <h2> It started in Croatian </h2> <p>The first version was entirely in Croatian. It was a personal tool, <br> just for my workplace. I never planned to share it publicly.</p> <p>Then I showed it to my wife. She's a professional translator, so <br> language is her thing. She looked at it and said: <em>"This is really <br> good. Other people could have the same problem — translate it and make it <br> available to everyone."</em></p> <p>That was the push I needed. So I translated everything, polished <br> the UI, and decided to launch it properly.</p> <h2> The solution </h2> <p><a href="https://www.dibsl.com" rel="noopener noreferrer">dibsl.com</a> — create a timed event, share <br> a link, and whoever clicks fastest wins a spot.</p> <ul> <li>Server-side timestamps — no cheating</li> <li>Anonymous codes — transparent results without exposing emails</li> <li>Waitlist — if a winner steps down, next person gets notified</li> <li>Bot detection — clicks under 150ms are rejected</li> <li>Campaign system — organise multiple drops under one campaign</li> </ul> <h2> Tech stack </h2> <ul> <li> <strong>Frontend:</strong> Next.js 16, Tailwind CSS</li> <li> <strong>Backend:</strong> Supabase (PostgreSQL + Realtime)</li> <li> <strong>Scheduling:</strong> QStash (Upstash) for precise event timing</li> <li> <strong>Emails:</strong> Resend</li> <li> <strong>Hosting:</strong> Vercel</li> </ul> <h2> The interesting technical challenge </h2> <p>The hardest part was ensuring fairness. Reaction time is calculated <br> server-side: <code>reakcija_ms = server_click_time - actual_start_time</code></p> <p>This means network latency is part of the game — just like in real <br> drops. But server-side ranking means no one can cheat with <br> autoclickers or scripts.</p> <h2> What's next </h2> <p>Currently in beta — free to try. Would love feedback on the fairness <br> angle and any use cases you can think of.</p> <p>👉 <a href="https://www.dibsl.com" rel="noopener noreferrer">dibsl.com</a></p> showdev webdev startup nextjs