4 ms·
"For Android" implies Java is usable, and bytecode can be very dense, so IMHO this could be even smaller.
by userbinator 2y ago
"For Android" implies Java is usable, and bytecode can be very dense, so IMHO this could be even smaller.
- MaxBarraclough 2y agoThere's a Flappy Bird clone for the GameBoy, in the form of a 32kB ROM. [0][1][2] This isn't to downplay this Android-based project though. They aren't claiming to have written the most compact Flappy Bird clone. [0] https://laroldsjubilantjunkyard.itch.io/flappy-bird-gameboy/devlog/333675/flappy-bird-gameboy-homebrew-v100-completed https://laroldsjubilantjunkyard.itch.io/flappy-bird-gameboy/... [1] https://laroldsjubilantjunkyard.itch.io/flappy-bird-gameboy https://laroldsjubilantjunkyard.itch.io/flappy-bird-gameboy [2] https://www.youtube.com/watch?v=m839Vg_qXzM https://www.youtube.com/watch?v=m839Vg_qXzM
- im3w1l 2y agoI'm honestly surprised at the 100k figure. In my mind it should be possible go far lower. 10k sounds vaguely realistic.
- londons_explore 2y agoif you're willing to compromise on the graphics and just get the core gameplay, I reckon you could do it in a 512 byte x86 bootsector.
- im3w1l 2y agoRight. I meant with the graphics though.
- Lerc 2y agoWeirdly, I think the challenge would be more difficult going to Android than adding graphics while keeping the size down. It would not at all surprise me to see a near perfect Flappy Bird under 4k (graphics and all) as a PC .com I'd be curious to see what the minimum size of a simple C program would be. Say something that displayed a pixel that bounced up and down as you tapped.
- lifthrasiir 2y agoI think it can be optimized quite a lot by not using a stock PNG decoder library, because all images are quite simple and can be generated from non-pixelated smaller sprites (many images are pre-scaled by 2x, which can be done during the postprocessing) or from a simple algorithmic code.
- Frenchgeek 2y agohttps://github.com/nanochess/fbird https://github.com/nanochess/fbird