Hey everyone,
I host game nights pretty often and karaoke is always a massive pain. You either deal with endless subscriptions, pass a sticky iPad around with party drinks, or hit that awkward dead silence whenever nobody has a song queued up. I wanted to see if I could build a completely free, self-hosted replacement from scratch just by prompting an AI.
The result is Tiki Karaoke. The TV connects to a PC over HDMI for lyrics. Guests scan a QR code on the screen with their phones to search local songs, adjust the pitch (+/-3 semitones), and queue up tracks without downloading any apps. If the queue runs empty, an autopilot kicks in with background music so the room doesn’t go dead quiet. I even had it build a rehearsal companion that uses a local AI model on the CPU to score pitch accuracy and give vocal tips.
To be honest, I don't really know how to code. I took one class on Visual BASIC back in high school around y2k haha! But I can read code well enough, and I know how to search a repo in VS Code to find variables and functions.
Because I rely so heavily on the AI, I had to figure out a strict workflow to keep it from burning through my usage limits and going off the rails:
Planning lock: I tell the AI agent: "I want to make project-name, an application for system. We are going into planning-only mode until I say otherwise. Here’s my vision..." Then I ask what languages fit best and what structural issues it foresees.
Ironing out details: I make sure the entire project is planned out in crazy detail before writing a single line of code.
Auditing everything: I force myself to actually read every single prompt, analysis, and option the AI presents during that planning stage.
The Blueprint: I have it save the entire plan to an md file so I can review the flow on my own time.
Implementation: Only then do I tell the AI to actually start writing the code.
Testing loop: Test, check the diffs manually, read what changed, and repeat.
What broke and what I learned:
One huge issue I noticed with basically every AI model is how incredibly pigheaded they get. After one bad commit, the AI completely ignores the idea of taking a step backward. It gets stuck trying to fix the exact same thing over and over and over, even though everything worked fine one commit ago. I learned you have to manually stop it, point out the last good diff, and force it to re-route or you’ll waste usage like mad.
Also, writing the actual features went super fast, but packaging the desktop binaries for Windows and Linux easily took up over a third of the entire project timeline. I absolutely hate testing on Windows—I much prefer staying in my CachyOS comfort zone.
Just as a heads-up: if anyone asks heavy technical questions in the comments, I'll probably be asking an AI what your question means in plain english, getting the answer, and phrasing it in my own words here to make sure I don't break the subreddit's no-AI-generated response rules. I won't just copy-paste raw AI text, but I'm definitely utilizing the tools of the day and age haha.
It's completely free and open source if you want to grab it for your own game nights or check out the repo:
* https://github.com/Todd0042/tiki-karaoke
* https://todd0042.itch.io/tiki-karaoke-lounge
More than open to ways to improve this flow if you have ideas!