I joined Bubble Busters early as a senior Unity developer and gradually took on responsibility for the client architecture and technical direction, eventually becoming the Client Technical Lead.

Our product was essentially a prototype, without a clear structure for handling the game's different states.
helped design and implement a state machine that gave each state its own scope, so you could work on one without it bleeding into the rest.
I also built the client-side plug-in/plug-out feature architecture, letting features ship and roll back independently and without the need for a new client version every time.

Character abilities used to be one large class per buster with little shared code.
I broke them into runnable steps - a mix of buster-specific steps and reusable ones like "wait" - composed into a runnable, making sequencing simpler and more designer/artist-facing.
Runnables leaned on a synced animation system I also built to keep simulation-critical animations synced across clients in real-time play, keeping the simulation lean and the visual work on the Unity side.

Led the technical side for a team of 4-5 developers - architecture decisions, code quality, and making sure everyone knew what to build and why. Mentoring was an important part of that, helping people grow into work they could own and lead themselves.
Also, I worked with the team on code standards that fit us, and kept our tooling and systems built around that.

Part of the core team that kicked off Quick Hit V3 (Unity), rebuilding it from an existing company product into what's still live today. Played a central role in implementing two of the game's most prominent features - the Daily Bonus wheel and Wild Balls - both are still central to the game and getting regular updates.

Developed and maintained live-op features and events for Quick Hit's Flash version.
Built an AIR tool application that helped with automating tasks that we used to do very manually - it stayed in use until the Flash version of the game was retired in favor of Unity.

One of the original members of the company's tiny hyper-casual team.
During my time in the Hyper Games team we shipped two hyper casual games and were in the process of shipping the third.
‍
We also built some unusual architecture along the way - one of these was a "master" app to enable us to host multiple games within the same app. This app wrapper also exposed a consistent API to the games it hosted, keeping them agnostic of the specific services we used and helping speed up development on each game.

Another was a rule-based visual scripting framework to accelerate iteration time on mechanics as well as make it accessible for our designer.

Built the Flash version of the product from the ground up.

The project had a strong focus on quick delivery so I focused heavily on tooling. I built an import pipeline that parsed Slot Designer scripts our designer made, allowing new slot machines to be imported with minimal developer intervention.

We reached production pace of a slot machine per week give or take, even when those included new features.

Joined Diwip as a junior developer and worked on Slots Club, my first experience contributing to a large existing codebase.

I initially focused on understanding and extending the existing systems, using my animation background to build special-effects scripts and assets that could be added to slot machines. The effects proved popular internally and became one of my more visible contributions to the project.

Joined WDIFA as the sole client-side developer for a multilingual learning platform supporting Arabic, Hebrew and English, built around interactive Flash games.

I developed the Flash web application where users could track their progress through different learning tracks and play educational games. I designed it as a modular platform, allowing new games to be added and integrated into the application without rebuilding the core client. I also developed over five mini-games that integrated the educational content directly into their gameplay.

Working as the sole client developer gave me broad ownership of the interactive side of the product, from game logic and UI through to the underlying systems connecting it all together.

Starting as a GMTK Game Jam entry, Spectre's Wheel is a story about two women dancing through the night in a sacred circle to ward off evil spirits.

After receiving very positive feedback from the itch.io community, we decided to turn it into a fuller experience. We've been developing it on and off for about a year, refining the game, adding enemies and mechanics, and steadily tightening the overall experience.

This is a long-running side project with my wife, who is creating all of the art while I handle the rest - programming, game design, sound and music.

Skies Over Sand is an action-strategy concept where you pilot ships and build defenses to protect your planet from an invading force.

The idea was to have everything take place within a single dynamic world, where the conflict could develop in different ways rather than playing out through a fixed sequence of levels.

Most of my work went into prototyping the 3D ship controls and dogfighting mechanics.
The project was ultimately more of a prototype than a finished game, but I really enjoyed getting deeper into 3D - from the maths and controls behind the ship movement to render pipelines and visual effects.

A platformer prototype built with a small team around Unity's 2D physics system.

I designed and implemented the character controller and most of the gameplay interaction systems, including climbing, grabbing, picking up and throwing objects, weapons, and vehicles.

A big focus of the prototype was making objects interact in physical and systemic ways. Fuel cans and batteries could be moved between machines, most small objects could be picked up, thrown and sometimes even used (guns, flashlight, remote).

The result was a flexible interaction system that could support both combat and puzzle-solving.

Harvester is a prototype for a music-driven game where you ride a bike towards a world-devouring machine, hitting obstacles and dodging hazards in time with the music.
I wanted the game to feel like an interactive music video, with the world itself built around the rhythm of the track.

To make that possible, I built a custom tool that generated the road from Bezier curves and mapped MIDI notes onto it. This let me visualize exactly where each beat would occur in the world and position obstacles and events so the rider would reach them at the right time. It also allowed me to change the bike's acceleration and deceleration, automatically re-timing and re-positioning everything when the speed changed.

A lot of the work on this project went into these tools, making it possible to build and iterate on the experience directly around the music.

A collection of smaller prototypes exploring different ideas, built independently or with friends.

Built in a couple of weeks including visuals and audio. It grew into a surprisingly complete prototype, with several enemy types and a boss fight.

A 3D prototype of a visual novel with an integrated card game. My wife provided the art here and we experimented with a mix of 3D environments and 2D character cutouts, including custom Shader Graph effects to help integrate the characters into the world.

An earlier version of the physics platformer, focused more simply on movement and platforming. I mostly guided the team, which consisted of my wife and a friend, teaching him Unity and helping them manage the project.