Hey Devin, thanks a lot for taking the time to test the game and write detailed feedback. Even as a first-impression test, this is very useful!

The first six levels are intentionally easy and chill. The difficulty starts increasing slowly after level 10, becomes much more noticeable after level 20, and the final 4–5 levels are meant to be challenging. The main thing I still need feedback on is whether those late levels feel difficult but motivating, or simply too stubborn and frustrating. Reaching level 20 probably takes around 15 minutes, so I know that requires a longer test.

There is already a fast-forward system. When the balls keep bouncing without hitting bricks for a while, the game speeds them up automatically. If a shot continues for around 10–12 seconds, a fast-forward button also appears. You probably didn’t encounter it during this session, which may mean the feature needs clearer feedback.

For aiming, the intended control is to hold, adjust the line, and release to shoot. I’m not sure about showing the aiming line before the player starts aiming, because I think that could make the mechanic feel heavier or clutter the screen. Still, your point about wall-bounce readability is fair.

“Power Left” shows the total remaining durability of all the bricks. I agree that the wording is not clear enough, but I also need to keep it very short because of the limited UI space. Would “Brick HP” have been clearer to you? I’d also be interested to hear any other short label you think would work.

You’re right about some of the text being a little small. I was already aware of it, but it slipped through during the final work. A simple How to Play button in the main menu could also be useful for explaining aiming, touch controls, and the X2 Power button.

I’ll also reconsider whether the level should finish immediately when the last brick is destroyed instead of waiting for the remaining balls.

Thanks again for the helpful feedback!

Hey, thank you very much for the detailed feedback and for spending time with the game!

Adding new mechanics as the levels progress is definitely something I would enjoy doing. However, I recently started focusing on making several small games in different genres to build a wider portfolio, so I intentionally kept the scope of this one limited and cut some ideas to finish it faster. Still, I agree that this kind of game benefits a lot from new mechanics appearing over time.

I did not think as deeply about the increasing ball count, but I spent quite a lot of time on the level difficulty and layouts. I used some formulas and shape analysis while designing them, so the progression, fairness, and satisfaction of the levels were probably the main things I focused on in this project. I’m glad they felt fair to you.

You should actually be able to access previous levels. On the level selection screen, drag the white current-level tile upward and the list should scroll back toward the earlier levels. It may not be clear enough, though, since you did not notice it.

An endless mode would also fit the game well, but I left it out because of the limited demo scope.

And yes, the plain blue loading screen looks a little rough. I usually create a loading scene early because I may later connect memory management, pooling, or other loading processes to it. This game actually has a short prewarm process, but since I was treating it as a quick demo, I did not spend time decorating that screen.

Thanks again for the careful testing and all the helpful comments. I really appreciate it!

Hey, thanks a lot for testing the game and sharing your feedback!

The aiming issue near the sides is useful to know. I’ll take another look at the reflected trajectory, especially when aiming close to the walls and corners.

The early difficulty curve is intentionally quite gentle. The difficulty starts increasing slowly after level 10 and becomes more noticeable after level 20, so level 12 still feeling similar is partly expected. Still, the increase may be a little too subtle during those early levels.

There is already an automatic fast-forward when the balls keep bouncing without hitting anything for a while. The button also appears if the shot continues for around 10–12 seconds. I kept it hidden at first because I wanted normal-speed hits to remain readable and didn’t want the UI to feel crowded, but I understand why having it visible all the time would feel more predictable.

I also agree that the main menu could communicate its flow a little more clearly.

Thanks again for taking the time to play!

Hey, thank you very much for the detailed feedback and for playing all the way to level 21. That genuinely made me happy!

About the aiming line: while developing this, I tested many mobile brick breaker games and noticed that small trajectory mismatches were surprisingly common. Later I understood why. Unity’s collider physics and a manually drawn aim line do not calculate collisions in exactly the same way. The line is strict and linear, while the ball and brick colliders calculate collisions between shapes with actual size, especially around corners. I spent quite a lot of time improving it, and the current version is much more accurate even with several zigzag bounces. You would need to see the earlier versions to understand why I was so happy with it :D Still, corner cases can remain.

The game was originally developed for Android in portrait mode. I later made a WebGL version because it was much easier to share it as a portfolio project and receive feedback. That is why fullscreen desktop resolutions can cause some layout problems. I am not sure whether I will have time to fully polish the desktop fullscreen version before starting my next project, but I at least want to fix the mobile edges, since playing it on a phone feels more enjoyable to me.

You are also completely right about the ball count and brick durability increasing together. I noticed the same thing while testing other games in this genre. Mobile versions usually solve it with bombs, lasers, temporary extra balls, or purchasable power-ups. Since I did not add those additional systems, the progression can feel a little neutral even though the numbers increase.

The X2 Power was designed to add some strategy. You first unlock it by reaching the Great Shot threshold, and then you can choose which later turn to use it on. Since the ball position and board situation change after every turn, choosing the right moment can make a large difference. It doubles the damage of every ball for that turn. There is a popup when it is activated, but it seems the mechanic still needs a clearer explanation.

The shot messages are also connected to performance:

• Nice Shot: at least 2× your current ball count in damage
• Great Shot: at least 4×, and it unlocks the power if it is not already available
• Magic Shot: at least 6×

So they show how efficiently your balls performed during that turn, rather than being purely decorative. I also used this efficiency metric while designing the difficulty curve. For example, around level 10, each ball is expected to produce at least about 2.7 hits worth of damage per turn. By level 30, that target rises to around 10.8 per ball. Since the player has 68 balls there, the expected turn damage is roughly 734 or more. The idea is that later levels require better angles and more repeated bounces, rather than only giving the player more balls.

I already knew the game still had some clarity and polish issues, but feedback like this is exactly what I needed. It is surprisingly difficult to know which details deserve the most attention without seeing how other players understand the systems. Thanks again for the careful testing!