818 karma · joined March 6, 2012
But what's much more important to us is having HTML5 games in general move forward, and that starts by getting more folks (especially students) developing games with the technology versus Flash or Unity. If HTML5 "fails" for games, Clay.io no longer exists.
We gathered as much as we could for prizes, but the main issue was with securing more sponsors. Clay.io in its current state is 3 undergraduates at the University of Texas - we don't have funding at this point, so we have to be a bit scrappy.
The controller library itself has good performance on iOS since that's obviously one of the main targets of something like this.
This was me taking a game that completely didn't work on touch devices, and making it work - hence the "Spacebar to start". That functionality was mapped to the "B" key. I'll add that note into the documentation, thanks for pointing it out!
Using URLs to link to in-game content is an interesting idea, something I'll play around with in the next few days and see about getting that as another feature of our API.
Persistent data on all devices is fantastic - of course, we need more HTML5 games that work well on each device. The two main issues I've seen developers run into with getting their games on mobile are 1) the performance in mobile web browsers (the latest Safari is pretty good, but most games still have a tough time) and 2) handling user input - developers are able to take full advantage of a keyboard on desktops and limiting to touch is a big change (though it seems a lot of devs forget about the accelerometer). If the developer has tackled those issues, we're here with the data storage feature of our API to allow for easy implementation of that idea. [2]
As for interacting with the DOM, it's funny you mention that, just yesterday we updated our homepage to have a mini-game in it (calling it a game is a bit of a stretch though) that interacts with the DOM [1].
Here's a demo video: http://www.youtube.com/watch?v=6oBf-Rlm5_Y
Maybe I'm weird, but http://grab.by/dXiq just seems overwhelming to me and is a turn-off.
Also, as far as I know, OpenID 2.0 doesn't pass the username/name/picture (correct me if I'm wrong), so there is some extra work involved in getting that info from each individual provider (assuming they even provide it like Google does)
http://clay.io/docs - Let me know what you think and if you would have used the API if you had known about it. If not, I'd like to know what we can improve on!
I listed various other arguments for why I feel it's the "best" out there right now. I think the strongest arguments however are the two games in < 24 hours each.
I'm sure it was a very scary moment for him and his family, but I hope this lighter take on things helps a bit. However, should he want me to take it down, I'll respect that decision.
It's an HTML5 game, so it's cross platform (play on your phone if you'd like)
If any HN people see this, I'd appreciate an explanation as to why.
The API docs are here: http://clay.io/docs
You may have seen one of our games that was developed by a couple other UT students and polished up by us - http://wordwars.clayio.com (it's a good way to see our API in action)
We're looking for as much feedback as possible, so please do let us know your thoughts!