
Built a company on top of Node.js before scuttling it. Competed in both of the previous Node Knockouts, winning Eran Hammer-Lahav's unofficial award for "Most Geek-a-licious" app in 2011.
I'm excited to see so many applications built to play with the Web Audio and getUserMedia APIs. This is a neat technical demo but doesn't really take it as far as it could have gone (maybe creating a multi-track mixer). (Note: I may come back and adjust the scores I give after judging more entries.) | |||
Thanks for the feedback!!
As it stands automated testing is the only reasonable way to manage testing for a website. The more tools we have for that the better. Currently it triggers a 500 error on /site/add and so I can't add a site to the system. (Note: I may come back and adjust the scores I give after judging more entries.) | |||
The premise of the game is simple enough and I like how it allows for ... "natural" selection. However this game–by its nature–is less accessible to the general populace. It will also be really hard to "win" or "eliminate" a player due to mutual die-offs reducing the scope and range of moving your cells. That being said, I enjoyed it and it has a lot of nice details with sound, differently shaped cells, and movement. (Note: I may come back and adjust the scores I give after judging more entries.) | |||
Thanks Nathan. I think it's sometimes a trap that us developers fall all to often - assuming the user will understand and not writing enough help esp given the time pressure. There is also a slew of features that we didn't get time to do that would of helped in this area. Cheers, Craig
Betting markets are a neat concept, but I'm not sure how this one is best incentivized. The easiest way to make a lot of "money" in this approach is to grab a popular series (eg. My Drunk Kitchen) early in the time during which it was posted. Also, there is no way to lose money, so nothing to dis-incent bad investments. The design and interface is plain but effective. I don't know where the future direction of this is headed, care to fill me in? (Note: I may come back and adjust the scores I give after judging more entries.) | |||
This neatly corresponds with how I often find myself ordering when I eat out. A person who is employed at a restaurant will have an opportunity to at least see everything that comes out of the kitchen, how much and of what people leave on their plate, and be more able to make an informed decision regarding what they recommend. However, I wonder if by democratizing this you lose some of the "house advantage" that the wait staff has which makes them so good at this. (In the deployed version I couldn't get it to add a pick.) (Note: I may come back and adjust the scores I give after judging more entries.) | |||
I have exactly two issues:
This is a really neat hack and I'd love to see this polished up a little bit and released as a toy project after the NKO is over. (Note: I may come back and adjust the scores I give after judging more entries.) | |||
Definitely! We are full of ideas for improvements, but we can't push them until the contest is over :)
Once it is, screamcasts will live on and add some more hot sauce.
Realistically, audio syncing has applications well beyond synchronizing music across multiple machines running the latest version of Chrome, if for nothing more than Improv Everywhere's MP3 Experiment (http://improveverywhere.com/missions/the-mp3-experiments/). Or, in a more practical application, something approximating this technique could be used to broadcast communicate amongst protesters without an amplification permit (http://www.litkicks.com/PeoplesMic) by attaching a touch of WebRTC magic to the approach. This is certainly a fun toy for hackathons and with a touch more interface control (eg, a designated "DJ") I could see this being used frequently at hackathons. (Note: I may come back and adjust the scores I give after judging more entries.) | |||
Thanks for the feedback! :)
Yeah, the microphone idea is a great one - would be an awesome way to give 'impromptu' talks to a big room. I was too busy trying to get everything to sync properly before the deadline, but it would be definitely be cool to add in the future.
Can you check your Facebook connectivity? "An error occurred with SettleApp. Please try again later." I'll check again later, current ratings are approximations. | |||
Two things really hurting your performance more than anything is that senju.sendScreen is passing the entire HTML body contents of the help requester's screen and simple latency. That being said, the approach you've taken is a very clever workaround for what might be an incredibly complex (and likely brittle) solution where you try to propagate browser events from one side of the connection to the other. One possible solution might be to send diffs of the body content to reduce network time, but that may increase draw time. Catch 22. :) This is a type of utility that is very much in active use by companies trying to get insight into how their customers use their sites. So popular in fact that last year's NKO Solo Winner implemented something much like this! The chat functionality would really take this to the next level, as would implementing WebRTC for audio. (Note: I may come back and adjust the scores I give after judging more entries.) | |||
Thanks for the review! We had the idea of sending only the diffs to the server in mind, but we hadn't enough time, so we had to implement the easier and faster solution in order to show the demo :)
This solves a real need and is clean and well organized. Issues:
Yeah, that is all of the comments I have because everything else is just about right. Please don't shut this down after the NKO.