InDomino’s
dev diary.

The dominoes already had a more pronounced border, but the score panels and buttons still looked thin beside them. The adjustment started with that difference: use the tile as a reference for border thickness and corner size.

Panels came first. Then buttons received the same proportions, without increasing their size or changing colors, text, or clickable areas.

Rounding the corners revealed another detail. The study brought the shape closer to the dominoes, but lost the highlights and shadows that gave the border depth. This option was still a visual test, not the version used in play.

Restoring the depth solved one part. The outside corner was rounded; inside, the border still closed diagonally. In the next revision, the inner curve followed the outer one while preserving the finish of the straight sections.

These adjustments belong to the development version from September 12 and 13. They are not in the site’s demo yet.

You can now play InDomino here on the site. The first demo contains the campaign’s three opening stages and runs in a desktop browser, with keyboard and mouse.

It is a short slice: build your first sequences and try to reach the targets. Bosses are not included. The campaign’s first encounter happens at stage 5, and it was not moved forward to fit the demo.

After your third win, the demo ends and you can start another run. Progress is saved in this browser when storage is available. If the browser blocks saving, the page tells you and the game continues.

The full campaign is still in development, with 25 stages and five bosses. For now, you can get to know the game at these three tables. The “Play the demo” button is at the top of the page.

On September 12, InDomino was already running in the browser in a local test version. You could check the image and interaction with the table, but there was no public demo on the site yet.

In the same phase, bosses gained temporary expressions to signal some effects. Score panels were also rearranged in the order Golden, Bonus, Pass, and Player.

The difficulty study covered all 25 stages and found results outside the expected ranges. But those numbers came from a simplified simulation, not a person playing the campaign.

The results stayed as a reference for investigation. They were not enough to start changing the game’s values.

Running locally was one step. Opening the demo through the site still required checking loading, saving, and publication.

Closing and reopening the game should not change the random sequence of a saved run. In the native version, resuming started preserving that sequence alongside the rest of the state.

Endings received work too. Victory and defeat gained adjustments to the summary, restart options, and what remained on screen after the result.

Fixes addressed temporary states carried between stages and Echo’s presentation. These were details that needed resolving before continuing or starting another run.

The changes were checked in test scenarios and Windows packages. This delivery, recorded on September 11, concerns the native version. Browser saving still needed its own verification.

Those tests record specific situations. They do not replace someone playing through a complete run.

A tile can gain a level, receive a special, and need to return in the same state after a save. The adjustments from this phase reached those combinations.

Between March and May, I worked on support-item wear, level displays, and used tiles. Each change needed to keep making sense when the run advanced or was resumed.

Specials also received adjustments. Mimic variants arrived, along with changes to wildcard interaction and fixes to dragging and application limits.

In May, overlay specials became able to target the play area. The target no longer had to stay within the hand. That expanded the feature’s use and the situations that needed checking.

The campaign expanded to a 25-stage foundation. During this period, the Gambler also brought wagers into encounters.

Encounters, actions, and rewards were reorganized to happen at defined points in the run. With a longer route, there were more transitions between those states to check.

The shop gained rarities and new options. Golden rewards started accumulating free offer refreshes. You can use those chances to change what is for sale without spending money.

Browsing the set of dominoes also gained its own screen. It became more straightforward to see which tiles were available in the run.

More stages did not mean the difficulty was settled. Targets, rewards, and the pace of progression were still being studied.

The Bully was the first boss to get his own encounter. Portraits, dialogue, and introduction and defeat sequences followed.

His expressions started following his mood during the run. Confidence, pressure, and irritation appear on his face while the table keeps working.

His interference also entered the game. Tile Flick knocks a tile out of your hand, so the taunt has a consequence you need to consider on your next play.

To fit that into the flow, I had to adjust the timing of the action and the table’s waiting periods. The character’s presentation, the effect, and resuming play needed to happen in the right order. Those adjustments were part of the work from March 12 to 15.

Rewards now had somewhere to go. Between stages, the shop arrived with offers and options to buy, sell, and repair.

From March 9 to 12, this part gained navigation, item selection, and a connection to the previous stage’s result. Money earned after a win became part of preparing for the next table.

You look at what is for sale, check your money, and decide what to take. You can also sell or repair. These choices happen between stages, but they are still part of the same run.

The shop’s presentation came together alongside that flow: green felt, wooden frames, and items on cards. The screen brings together what you own, what you can buy, and the actions available at that moment.

With wildcards and multipliers, your hand no longer depended only on the values printed on the tiles. Specials started changing what you could do with the dominoes you had.

From March 4 to 8, I worked on both the effects and the steps needed to use them. A special needed to leave the reserve, reach the chosen tile, and show what had changed on screen.

Support stones also started taking part in stages and scoring. They added effects to the run alongside the features already on the tiles.

That combination brought more situations to check. One effect can change the result of the next, so application order is part of how a play works. Checking each special on its own is not enough.

In March 2026, I started using InDomino as the game’s name. Dominox was the previous name and still appears in some files. The public name changed before the rename was finished inside the project.

On the table, tiles started gaining levels and multiplier bonuses. Evolution also received animations to show when a domino changed.

Progression now showed up in the tiles themselves. It was not just about reaching a higher target in the next stage: the dominoes taking part in the run could evolve too.

Scoring studies started gathering limits and assumptions for those bonuses. Having the effect working did not settle the balance. The values were still being studied.

Playing tiles and getting a total does not show how much each domino added. Tile order and effects are part of the calculation, so that result also needs to show up on the table.

In February 2026, I adjusted the sequence: the dominoes enter the play area first, the chain joins together, points appear tile by tile, and then the total is counted.

The next hand started waiting for that sequence to finish. Previously, replacement tiles could appear while the last play was still being shown. Two things were happening on screen at once.

Stage success and failure messages also received adjustments. This change was about presentation: follow the connections, watch the points come in, and only then move on to the next hand.

Selecting a tile, rearranging your hand, and dragging it onto the table are actions you repeat throughout a run. In June and July 2025, I spent a lot of time on that part.

Tiles entering the hand, selecting several at once, and movement on hover all received adjustments. Panels and fonts changed alongside the interaction.

Behind the screen, I separated the rules from the code that draws and moves the tiles. I reorganized that structure and added tests to check what still worked after the changes.

Part of this period was rebuilding what already existed. Looking only at new things on screen does not show all the work from that stage. Dragging was changing, but so was the foundation that handled it.

I started with the tiles. They needed to appear on screen, respond to clicks, and reach the table when dragged. Then came scoring. That was the core of the prototype in May 2025.

Through that month, I worked on the set of dominoes, the stages, and the sequence of rounds. You could already pick a hand, play it, and earn points. Animations and the first sounds also started to follow those actions.

It was not the campaign we have today. This first version was about getting the dominoes moving and making a play happen from start to finish.