Brain Sniper
Live Cognitive Competition & Entertainment Platform
On May 11, 2026, I pushed the first production build of Brain Sniper to live users.
I wanted to solve a specific friction point: cognitive gaming is incredibly lonely. You solve a puzzle, get a score, and close the tab. I wanted to see if we could take the high-stakes pressure, spectator energy, and production value of live esports and apply them to mental performance.
So, I spent the last 66 days building a browser-based Live Cognitive Competition & Entertainment Platform.
As a solo developer, the goal wasn't just to build a game, but a live broadcast engine. The stack is relatively lightweight but highly leveraged: HTML, CSS, Vanilla JS, Firebase (Auth, Firestore, RTDB), Agora (for live interaction), and Stripe.
Currently, the architecture supports:
Dual-Database Syncing: Using Firestore for persistent player records and Firebase Realtime Database (RTDB) for sub-second game state, active rounds, and live player synchronization.
Broadcast Integration: Seamless YouTube embeds and real-time overlays for live streaming.
Velur Liun (The Promenade): A private, native community hub for post-match discussion.
AMP Rating: A custom, real-time performance rating system designed for competitive matchmaking.
The Technical Reality of "Live"
Building a real-time multiplayer platform solo means you don't get to hide behind "good enough" caching. If a player’s timer is off by 400ms, the integrity of the competition is broken.
Some of the hardest engineering challenges over the last two months weren't the UI—they were the invisible mechanics:
Security at the Edge: Preventing client-side inspection of game data. I had to architect the system so secret words and puzzle keys never touch player-facing console logs or memory space until the exact millisecond a round resolves.
State Machine Clashes: Managing the state transition between multiple game modes (Stage Sniper, Free-For-All, Duel, Round Robin) without stale state bleeding over when a player switches lobbies.
Firebase Rule Hardening: Writing granular Security Rules that allow rapid-fire writes for live gameplay inputs while strictly locking down administrative controls.
The Cache Nightmare: Deploying multiple hotfixes a day to active users meant wrestling with browser caching. I had to implement aggressive cache-busting strategies to ensure players didn't get out-of-sync UI states during live tournaments.
What I’ve learned is that real-time web apps don't fail gracefully. They fail in tiny, chaotic ways: a single unresolved promise, a race condition between Firestore and RTDB, or an assumption that Client A's connection speed matches Client B's.
The Solo Founder Bottleneck
Right now, I am the developer, system architect, game host, customer support desk, and live broadcaster.
Building in public has been my saving grace. My alpha testers are essentially my QA team. They are the ones flagging when a player card locks up, when a timer fails to fire, or when a system message feels too mechanical.
Because of this, the project is evolving. It's shifting from a pure "game" to a broader digital environment where spectators want to hang out before the live broadcast, players want to debrief in the Velur Liun community space, and creators want to host live "Headliner Exhibitions."
The platform is still in Public Alpha. I'm currently manually handling some membership access and auditing our backend Arena Intelligence metrics before I trust them enough to scale.
I’d Love Your Feedback on Three Things:
Stripe-to-Firebase Automation vs. Manual Friction: At what point of active alpha testing do you transition from manual, high-touch user onboarding to fully automated Stripe-to-Firebase provisioning? I want to keep the community high-quality and verified, but manual admin is becoming a bottleneck.
Metrics that Matter for "Live + Community": If you were analyzing a platform that is part game, part live broadcast, and part community, which core metrics would you watch? (e.g., concurrent spectator-to-player conversion vs. standard daily active users).
The One-Sentence Category Problem: How do you succinctly explain a product that bridges two very different worlds (cognitive training and live interactive broadcasting) without sounding like marketing fluff?
If you’ve wrestled with real-time state synchronization or solo-launching a community platform, I’d love to hear your horror stories and lessons learned.
7 Comments
The interesting challenge isn't real-time synchronization—it's creating enough competitive tension that people come back even when they're not playing. I'd keep validating whether users are attracted by the cognitive games themselves, or by the live tournament experience and community. That's the harder position for future competitors to replicate.
This hit the nail on the head. I'm realizing the real product isn't the word engine—it's the "Monday Night Football" effect for cognitive performance.
I'm actually wrestling with this exact tension right now in the victory overlay: do I prioritize "Challenge a Friend" (game loop) or a direct path into the Velur Liun lounge (community debrief)? I'm testing the latter to see if the spectator hangout retains better than the puzzle itself.
For those who've built community-first platforms—how do you differentiate between "game loop" retention vs. "event/spectator" retention in your analytics? I'm tracking session blend (combat time vs. hanging time), but I'd love to hear how others split the metrics.
That's exactly the interesting decision.
Reading your reply gave me one thought about how I'd separate those two retention loops. I don't think I could explain it properly in a thread because the answer depends on what role you want the community layer to play in Velur Liun.
If you're interested, what's the best email to reach you on?
The platform is free to join. Did you look around it? Is that why you say it is not distinguishable the role the community layer might play just by looking at the platform?
I should clarify — I don't mean the role isn't visible from the platform.
My point was more about the long-term retention question: whether the community layer becomes valuable because it enhances the competitive experience, or because it creates a reason to return even when someone isn't actively playing.
Those are different retention loops, and I think the interesting part is figuring out which one becomes the core habit.
Time will tell us which is the core habit. Great probing questions.
I appreciate that.
There are a couple of thoughts I have on how to separate those retention loops, but I think they depend heavily on what role you want the community layer to play long term.
Rather than stretching the thread, I'd be happy to continue the conversation privately. What's the best email to reach you on?