For a quick, breezy puzzle that you should be able to do within the space of a coffee break, this feels like it moves way too slowly. Takes a bit for the ball to start rolling and the fancy zoom-in animation gets tedious fast.
[deleted]
Google I/O '24 Puzzles
31–40 of 100 posts
Re: Google I/O '24 Puzzles
#32What a frustrating, poorly designed puzzle.
[deleted]
Re: Google I/O '24 Puzzles
#33Seems like this crowd is upset over a children's puzzle game. Thought it was alright, has decent graphics that shows what can be done procedurally without the need of carefully hand crafted assets.
Re: Google I/O '24 Puzzles
#34Cool, solving the puzzles gives you pleasing designs.
Re: Google I/O '24 Puzzles
#35There's a "help" popup indicating the existence of keyboard controls. Then, in level two , you have to rotate tiles, for which no control is documented. What gives?
Oh man I was so confused when I couldn't solve level 2. I even double checked the instructions that there was no rotate key. I'm on a laptop with a nub for a mouse and I'm spamming various keys to try to figure out how to get a piece to rotate and I haven't been successful.
I can also select a piece and hit space and it grows in size and goes outside of its box for some reason? Is that relevant to solving puzzles? Or a bug? I guess I won't find out since I can't rotate pieces to progress further ....
Re: Google I/O '24 Puzzles
#36Seems like this crowd is upset over a children's puzzle game. Thought it was alright, has decent graphics that shows what can be done procedurally without the need of carefully hand crafted assets.
See if being a children's game has any impact on your feelings about Winnie the Pooh's Home Run Derby then :p.
Small Google games are often actually really decent, especially in comparison to this, so I think that's where some of the disappointment comes from. The Doodle Champion Island one was my favorite.
Re: Google I/O '24 Puzzles
#37For a quick, breezy puzzle that you should be able to do within the space of a coffee break, this feels like it moves way too slowly. Takes a bit for the ball to start rolling and the fancy zoom-in animation gets tedious fast.
> the fancy zoom-in animation gets tedious fast
Broadly, this criticism applies to nearly all UX.
Re: Google I/O '24 Puzzles
#38That lack of antialiasing is horrible. I'm pretty sure it's not my browser settings because the three.js examples look ok.
Re: Google I/O '24 Puzzles
#39Seems like this crowd is upset over a children's puzzle game. Thought it was alright, has decent graphics that shows what can be done procedurally without the need of carefully hand crafted assets.
There are frustrating implimentation details like puzzles not being solved if you do something that looks obviously right but some subtle unwritten rule means it's wrong. In game design (and all UX really) when something looks right then it should be right. The user shouldn't ever have to think very hard to understand why something is wrong. This game fails in that regard.
Re: Google I/O '24 Puzzles
#40Seems like this crowd is upset over a children's puzzle game. Thought it was alright, has decent graphics that shows what can be done procedurally without the need of carefully hand crafted assets.
I don't think it was intended to be a children's game; they're not the target market for Google I/O.
But also, in this be situation there isn't much positive to be said about the game. Everything about it is badly done. I'm fairly sure the criticisms (vague and badly communicated rules, clunky UI, graphics style that doesn't fit the puzzle, announcing music without a separate music control, way too many slow animations in the wrong places, browser compatibility issues) would be the same if this was a Show HN.
It's just that none of it is being given as constructive feedback. But even that makes sense: unlike for a Show HN nobody will be applying the feedback to fix the game.
(What I don't get is how this is so high on the frontpage, unless it's just for the schadenfreude.)