😸 Time travelling phones

gm legends and welcome back to another fine edition of the Leaderboard. In today's issue: an app that brings your phone back to 2001, a tool to create automations as easy as speaking, and a secret weapon to win all of those online arguments.

P.S. Want your launch to be featured in this newsletter? Drop us a line with your pitch at editorial@producthunt.co 🫶

Brick 1100 turns your touchscreen into an old-school brick phone. No apps. No swipe. Just pixel fonts, loud buttons, and that beautiful, stupid simplicity.

🔥 Our take: This isn’t about being useful. It’s about shutting your brain off and pretending Snake is the only thing that matters. Everything feels clunky in the best way. You’ll probably last ten minutes, and that’s the fun of it.

n8nChat lets you build automations by describing them in plain language. It takes what you write and generates full workflows inside the n8n editor, with real logic and connected nodes.

🔥 Our take: There’s something strange about watching a chatbot build a system faster than you could sketch it out. It doesn’t always nail the details, but it skips the part where you stare at a blank canvas and forget what you were trying to solve. That alone makes it useful.

Qibble is a social polling app where anyone can post a question and get votes from the crowd. You can settle debates, gauge opinions, and finally see if your hot take actually holds up.

🔥 Our take: Everyone’s got that one argument that keeps coming back, online or over Thanksgiving dinner. Qibble gives you a way to end it, or at least back it up with numbers. Of course, if you lose the vote, that’s on you.

Gabe Perez kicked this off with a familiar dilemma: when you’re building with AI tools like Cursor, do you sit down and plan the whole thing or just open the editor and start typing?

He used to vibe-code everything. Now he writes a proper problem statement, turns it into steps with ChatGPT, and feeds those into Cursor to stay on track. Others in the thread argue that skipping structure leads to garbage UX, technical debt, or worse—like exposing user data.

If you’re building with AI tools, how structured is your process? Are you drawing it out, or just hoping the AI gets what you mean?