After years of talking about games for science, I'm finally going to jump in and make one. I've got an idea (which I will elaborate on soon) and now I'm trying to figure out how to go about implementing it. The challenge right now is to decide which of the infinite options that I should use to make it happen.
My basic requirements are pretty simple:
- the game should be accessible in most Web browsers
- it should run happily on an iPad
- it should have basic graphics (e.g. blocks and arrows) and sounds
- it should talk to a server running Java that will perform some computations and keep track of the data
- it should enable fast prototyping
- I should be able to do the prototyping myself
Here is a year-old list of 66 game-related javascript libraries that clearly is an underrepresentation of what is out there. One that isn't listed is a Google product called PlayN (formerly 'forplay') based on GWT. PlayN is tempting for me because you write your code in Java (which I guess is appealing to those of us in their thirties or greater) and it can generate deployable games in HTML5, Flash, the desktop and there are rumors maybe someday for iOS. Its also easy to distribute the games via the Chrome store. It doesn't have a lot of the Unity3d bells and whistles but, like I said, I don't need to use it to build the next Call of Duty. Still, PlayN is still alpha code and, as my colleagues enjoy reminding me, Java and other compiled languages are for old farts...

