I'm traveling for the holidays and only have my laptop, which I don't really have many full fledged games I can run on it (it's a macbook, so a combination of poor macOS support in general + the 32bit cliff means many games just don't run on here). I'm also more interested in casual games while traveling anyways.

Let me know if you have any recommendations for browser-based games, ideally something a little off the beaten path. Multiplayer suggestions welcome too for completeness.

Flash is gonna die for good in a few days (dec 31st) so I felt this is a good time to ask this question. (Although obviously, there have been large efforts to preserve these when the developers did not. And even then, HTML5 means browser games will continue to exist, even though mobile games have mostly replaced browser games anyway.)

Mine personally were (taking away some of the more well-known ones):

Gravitee 2

Basically a game of celestial golfball. Had a level editor, which was quite fun.

Bonk.io (although this one has a sequel that's not in flash)

Pretty popular for a flash game made in 2016. Basically a game where balls need to "bonk" eachother out of the playing field.

Effing meteors (Definitely one of the games that I probably remember being better than it is.)

Basically a game where you clump up small meteors into bigger meteors to destroy stuff.

Ribbit

A game where a rabbit and frog are fused together and need to bounce like a pogo to the end.

Frost bite

A mountain climbing platforming game.

Sushi cat

A game where you need to eat sushis quickly. Also has cutscenes.

Flash cat

An aesthetic racing game? Not entirely sure.

Chisel

A game where you drill through the planet enough times to move to the next level (man, I had some weird gameplay preferences.)

Dillo hills

A game where you need to time your descents to pick up speed in the hills and fly.

Dino run

An 8 bit game where you as a dinosaur need to outrun extinction.

Raccoon racing

A power-up racing game I remember playing quite a bit. Definitely designed for children, even if that's not very surprising.

I've been working on the mobile version of password for a while now, mostly lending to the fact that much of the infrastructure of the game required expansion to accomodate for that. Plus, this sort of gameplay on mobile is a new territory for me, which makes it both worrisome and exciting.

Long story short, you can preview the mobile gameplay of password with the same link:

Play the game.

The gameplay is different from the desktop version. Here, you have to tap the keys in the order of their number: 1, then 2, then 3, and so on until the last key. Tapping keys out of order (4, then 6) results in a foul, which takes away a bit of time. Tapping all keys in the correct order means you win the round and get awarded the score. Other instructions are on screen.

It is NOT the final version. It's playable but contains some visual bugs. I'm gonna work on fixing those in the coming weeks. Right now, I'm looking for feedback:

• How does the mobile gameplay feel?
• How does the sizing of the score looks?
• Are there any problems with swiping or tapping?
• How does the timer bar look on smaller screens? (Think smaller than iPhone X.)
• How does the timer look on devices that have a notch?
• Does it load the correct version at all? (If you're on a mobile device – smartphones and tablets – you should not see keyboard references. If you do, it didn't load the correct version of gameplay.)

Desktop gameplay has only received visual updates. You can still play it with the same link.

Let me know if you encounter issues. You can post here, or you can open an issue in the GitHub repo. If you do, make sure to provide what information you can on the issue, like what sort of a device you're using (maker, model, OS version, browser etc.): this helps figure out the problem easier and quicker.

I know of these issues so far, and am working on resolving them:

• after pressing the last key of the order (8 right now), the red border flashes, as if you've received a foul (you don't)
• score has to fully animate towards the final value before it resizes to fit the screen
• swiping distance may or may not be too short, so it may feel as though it doesn't register