← All posts
2026-04-25 · 8 min read

Why I built IGNOLUXBIT

Hi. I'm Ankit. I'm building this studio alone, and this is the honest version of why.

The dream that didn't have a path

I always wanted to make games. Not as a job, not as a startup — just as a thing I'd build with my own hands. As a kid I watched Pokémon, Doraemon, Digimon. I played every video game and board game I could get my hands on. I spent hours imagining what it would feel like to take an idea I'd had in my head and turn it into a thing other people could actually play.

I didn't learn to code, though. Not because I didn't want to. I just couldn't.

There was no internet at home until I was 14. No laptop or PC of my own until I was 17. No one in my life to guide me toward the path I actually wanted. So I did what my situation asked of me — I took a career in commerce, started supporting my family, and quietly locked the games dream away for "later."

Seven years of feeling lost

By 2019 the lock had grown heavy. I was busy enough with work and life that I'd stopped even pretending I'd find time to chase the dream. What I had was imaginations — fragments of games I could see clearly in my head, with no way to build them. Some of them were good ideas. I think.

Years went by like that. The dream didn't die, but it didn't move either.

The week the path opened

On 10 April 2026 I was scrolling Instagram and watched someone make a game with AI. Then I watched someone build a website without writing code. I'd known AI existed; I hadn't understood what it actually meant for a person like me.

I tried ChatGPT first. It built me a small game. I didn't love what came out — but for the first time in twenty-something years, the thing I'd wanted to do was actually possible. That changed something I can't unchange.

So I started reading. How do you make a game that doesn't feel like a tutorial demo? How do you turn a one-line idea into something that feels finished? I tried Claude next. Then I started using ChatGPT and Claude together — one for some things, one for others — and I started building.

The ten games on this site are the result of those first weeks. They're small. Some are still rough. They are mine.

What this studio is, deliberately

Not a startup. Not a roadmap to a hundred-thousand users. Small calm browser games. New one most months. One person making them.

The studio is called IGNOLUXBIT. The name reads as Ignite · Light · Digital — a digital spark that chooses to become light. It's a fancy etymology for a simple intent: make small things, keep them honest, ship them anyway.

The kill-memo

A few hours ago I asked an honest critic to tear the studio apart. I got back a brutal twelve-section brief written in the voice of a competitor analyst. Headline forecast: under 25% chance of survival at 24 months. The studio is too small, the brand is unmemorable, the catalog is thin, the moat doesn't exist, and indie studios with this profile usually die quietly.

It was the most useful thing I've read about my own work. I read it twice. For a few minutes I thought about quitting.

Then I asked the same critic — but as a mentor this time — to write the matching solutions. The answer wasn't "you can win." It was "you can survive if you cut about 80% of the plan." Which is what I did, in one afternoon:

None of those moves are clever. They're the obvious moves. I did them because the kill-memo made the obvious unavoidable.

The honest part about how this is built

I'm not a coder. The code that runs these games was written by me with heavy AI assistance — every game's HTML, every shared module, this devlog's CSS, all of it co-built with ChatGPT and Claude. I prompt, I steer, I review, I decide what to keep, I fix what's wrong, I ship what's ready.

The in-game visuals are procedurally drawn by code, not generated by Midjourney or Stable Diffusion. The audio is synthesized in the Web Audio API, not produced by an AI music tool. The brand kit — emblem, wordmark, the silver lockup you see on the hero — I built that too, with ChatGPT and Claude, across two or three days and roughly a hundred hours of back-and-forth iteration. No designer was hired. It was just me and the tools.

I'm telling you this because it would be silly to pretend otherwise. The honest summary: a non-coder who waited twenty years for a tool he could actually use, finally building the games he'd been imagining the whole time. If that bothers you as a player, fair. If it doesn't, you're playing what I'd have made anyway — just years sooner than the old way would have allowed.

What's also coming, eventually

There's a flagship game in development too. Bigger than the mini ones. Quieter. I won't say much about it yet — it's parked from the public homepage until it's actually playable — but it's the thing I most want to make. The mini games are practice. The flagship is the answer to the dream.

Why I'm writing this

Indie studios live or die by personality. The kill-memo was right that we have no moat: tone, tech, IP, distribution, talent, capital — all weaker than competitors who have ten years and a team. The only defensible thing IGNOLUXBIT has is the person making it, sharing what's hard about it, in public, for years.

So this devlog exists. One short post per shipped game. One per month minimum. Slow, true, no algorithm-bait.

Small things, fully made, outlast large things half-finished.

That's the principle. It's the line I keep rewriting in private. Now it's in public.

What you can do, if you're reading this

I'm walking this journey alone with big dreams and a small budget. I'm not going to give up. But the support of even a few people who care matters more than the algorithm makes you think it does.

Three small things. None obligatory.

Thank you for reading this far.

— Ankit
Building IGNOLUXBIT alone, from India.

All posts · Studio home · Discord