All posts

Case Study: Building a Playable Tetris Clone with Gemini and Hostilo

tetris.hostilo.page is a working Tetris clone, generated with Google Gemini and published on Hostilo. It is a useful example precisely because it was not perfect on the first try — and that is normal.

The brief

The goal was simple: a playable Tetris clone as a single HTML file, built entirely by prompting Gemini, with no hand-written code. Falling pieces, rotation, line clearing, keyboard controls — a small but genuinely interactive project, closer to a real application than a static landing page.

It took a few rounds, and that is the point

The first version Gemini produced had bugs. That is a normal part of asking an AI to build something with real logic — collision detection, rotation, and scoring all have edge cases that do not always work correctly on the first pass. Getting to a working game took several rounds of iteration: run the code, see what was broken, describe the problem back to Gemini, get a fixed version, repeat.

This is worth saying plainly because a lot of "AI built my website" stories skip straight to the success and make it sound instant. In practice, anything with real interactivity — games, calculators, tools with state — usually needs a few iterations before it is right. A static landing page rarely needs this; something with game logic almost always does.

Where Hostilo fits into that process

All of that iteration happened inside the chat with Gemini, testing the file locally between rounds. Hostilo was not part of the slow part. Once the final, working version was ready, publishing it was the same one-step process as anything else: paste the finished HTML into the editor, click save, and the game was live at tetris.hostilo.page. The back-and-forth with the AI took the time; going from a finished file to a public link did not.

The takeaway for your own project

If you are building something more interactive than a static page, expect to iterate with the AI before you publish, not after. Test the file locally in a browser first. When something is broken, describe exactly what happens instead of what should happen — "the pieces don't rotate when I press the up arrow" gets a better fix than "it's broken." Only paste the final version into Hostilo once it actually works the way you want.

Frequently asked questions

What AI tool was tetris.hostilo.page built with?
Google Gemini. The game was generated as a single HTML file through several rounds of prompting.

Did it work correctly on the first attempt?
No. Like most AI-generated projects with real interactivity, the first version had bugs. It took a few iterations of describing what was broken and asking Gemini to fix it before the game worked correctly.

Does Hostilo support interactive pages like games, or only static content?
Yes. Hostilo hosts any single HTML file, including inline JavaScript, so games, calculators, and interactive tools work the same way a static landing page does.

Why did publishing stay fast even though the game needed several iterations?
Because the iteration happened in the chat with Gemini, before anything touched Hostilo. Publishing is one step — paste the finished file and save — regardless of how many rounds it took to get the code right.