Adding node.js as a requirement to do client side development seems like it would be a big deterrent.
221 karma · joined September 9, 2009
Adding node.js as a requirement to do client side development seems like it would be a big deterrent.
Mine is online here: http://labs.brianstoner.com/paintsamples
It only works in new Firefox 4 beta cause it uses the new audio API.
I'd make it clear to the user you want them to click Sign Up, and make Learn More smaller or just a link below it. Also the 'Free' sticker almost looks like a call to action button too, and IMO slightly spammy.
Good luck with all the feedback.
Godaddy tries to sell less add-on services than U-Haul. They seriously have like 10+ pages of add-on's that no one wants.
I think we're going to move towards the browser as a music composition tool soon, and I can't wait. Some people at Mozilla are working on an awesome audio data api spec, check out their demos/videos: https://wiki.mozilla.org/Audio_Data_API
My problem before was that I would quickly scan through artist names/song titles and listen to one here or there and then move on. Now I give almost every song a chance before I go to the next. I get instant visual connection with each artist via the high-res pic, and i'm diving deeper into learning about artists with the little bios and pics that pop up during playback.
This is a win for music discovery UI's, even though it may be a loss for the social network aspects of their site.