I recently built Fruit Merge Game, a browser-based puzzle game where players drop and combine matching fruits to create larger ones.
You can try it here:
👉 [Play Fruit Merge Game](https://fruitmergegame.net/)
At first, the idea sounded simple: drop fruits, detect collisions, and merge two matching fruits.
But once I started building it, I realized that making the game feel good required much more work than the basic merge mechanic.
The Core Gameplay
The main loop is simple:
- Drop a fruit into the play area.
- Let physics determine where it lands and rolls.
- When two matching fruits collide, merge them.
- Continue building larger fruits.
- Keep everything below the danger line.
The simplicity makes the game easy to understand, but the challenge comes from managing space.
As the board fills up, every drop matters.
Making the Physics Feel Natural
One of the most important parts of the project was the fruit movement.
I didn't want fruits to simply fall straight down and stop.
They needed to:
- fall naturally
- rotate
- roll based on their size and weight
- push nearby fruits
- react differently depending on where they landed
Small changes to physics values had a surprisingly large effect on gameplay.
Too much movement made the game feel chaotic.
Too little movement made the fruits feel artificial.
Finding the balance took a lot of iteration.
25 Fruits and Multiple Evolution Routes
Instead of using only a short linear progression, the game includes 25 fruits divided across four evolution routes.
That gave me more flexibility when designing progression.
Players are not only thinking about which fruit is biggest. They also need to think about which merge path they are building and how much space that route will eventually require.
This added much more strategy to what originally looked like a very simple puzzle game.
Increasing the Difficulty
One problem with early versions of the game was that they were too easy.
Players could keep merging fruits without feeling much pressure.
To fix this, I adjusted several parts of the game:
- fruit sizes
- spawn behavior
- physics
- available space
- progression speed
- danger-line behavior
The game now becomes increasingly difficult as the board fills up.
There is also a short delay before the danger line ends the run, giving players a chance to recover instead of immediately losing because of one bad bounce.
Adding Strategic Tools
The game also includes three tools.
I didn't want them to function as simple "save me" buttons.
The goal was to make tool timing part of the strategy.
Using a tool too early wastes its value.
Waiting too long can leave the board impossible to recover.
That creates another decision layer beyond simply choosing where to drop the next fruit.
Designing for the Browser
I wanted the game to be playable immediately.
No installer.
No account required.
No app store.
A player can open the website and start playing:
👉(https://fruitmergegame.net/)
Building for the browser also meant paying attention to performance, input behavior, responsive layouts, and how the game feels across different screen sizes.
A physics-heavy game can quickly become expensive if too many objects are being updated unnecessarily, so keeping the game loop efficient was important.
What I Learned
The biggest lesson from building Fruit Merge Game was that simple games are not necessarily simple to design.
The basic mechanic can be explained in a few seconds, but details like physics, difficulty, progression, fruit size, tool timing, and recovery behavior determine whether the game actually feels satisfying.
A lot of the development process was:
build → play → notice a problem → adjust → play again
Small changes often had a much larger effect than expected.
I'm still improving the game and experimenting with balancing, progression, and gameplay.
If you try it, I'd be interested to know:
- Does the difficulty increase at the right speed?
- Do the fruits feel natural when they collide and roll?
- Which part of the progression feels the most satisfying?
Thanks for reading!
Top comments (0)