Recent comments on posts in the blog:
Great games
I have a motorola droid4 with a physical keyboards, the arrow keys are correctly recognized but not the 1/2/3 buttons. I think it shouldn't be hard to map these actions in a first time to the 1/2/3 keys , and maybe in the future add a menu to permit user to define with keys are linked to the button 1/2/3. What do you think ?
Thanks for the motivating comments.
I like the suggestion of moving static info in other screens to gain space.
I'll see what I can do to improve the port 
Very awesome game; I have it on my phone via F-Droid.
One minor bug in the Android version: as far as I can tell, you can't get to the options screen except when you first launch the game after installing (or wiping data). Could you add a '...' menu to get to the options screen?
Bought it. Seems to run nicely.
Things worth improving (yes, I know they're pretty obvious):
- naming the buttons (A and B?) and having the game (dialogs, help, etc.) refer to them as such
- scaling the graphics for different screen sizes - trying to see what's happening (and reading the HUD) was a bit hard on a 4" screen
- maybe moving some of the info on the main screen (how far you are in the game, etc) into the map screen, since it's not really necessary to see them all the time
Saving your progress and killing the app without explicitly quitting the game seemed to work... except for the first time I did it. Once I started the app again, the continue button was there, but none of my progress was actually saved.
$ perl -le 'print 0x4eb172bd'
1320252093
$