Welcome traveler!

It is almost three weeks after the Steam Next Fest, and all stats and feelings have settled down. Here is a summary of my experience with the festival: how my game Just Fly started and sailed through it, whether it helped, and what I will do next with it. I didn’t have any expectations because I joined with under 100 wishlists, which is too few. So let’s dig in.

The Steam Next Fest October 2026 started yesterday, and I am participating with my game Just Fly. Here is my journey from the initial prototype to a polished demo ready for the event.

I’m polishing my new game, Just Fly, which means I’ve been restarting it dozens of times a day. After a while, I got really tired of the gray flicker between the native Godot boot splash and my custom loading screen. I finally tracked down and fixed the root cause, without just masking the symptoms.

With my first game, Soma Cube, I made one big mistake: I didn’t know about Steam Next Fest, so I never registered it. I’m not making that mistake again. This time, I met the deadline with my new game, Just Fly.

My full build of Soma Cube passed Steam review and is now available!

I recently started learning game development, inspired by YouTube videos in which developers “speedrun” small but complete games in one to three months. Making games has been a dream of mine for decades, and I finally got the chance to work on one full-time – if you know what I mean :)

I started learning game development a couple of months ago, and I just joined my first game jam. The theme was “spin to win”, so I made a marble-rolling game with a twist: a rolling lollipop called Lolli-Roll. Can you handle the stick?

I’ve been using the Wear OS DataLayer (now called DataClient) wrong for over a decade – ever since the original Android Wear 4.4W. I always thought it was a shared storage layer where all connected devices got notified whenever data changed. It’s not.

I was upgrading an older Android project, the other day, to the latest Android version. It was built with the Jetpack Compose using its Material 3 (M3) design libraries. I recalled that it uses both M3, and the older Material 2 (M2), compose libraries because the pull-to-refresh component was poorly designed in M3. It’s better now, but it still lacks the enabled property of the original. Let’s fix that.

I got a chance to build a medium-budget PC for light 3D CAD modeling. This PC replaced an older machine running a 5th-gen i5 with and integrated GPU. I wanted to wait for the AM5-based Ryzens G APUs, but they still haven’t arrived, and with RAM prices skyrocketing recently, I’m glad I completed this build at the end of last summer.