Hey folks, appreciate the comments! Another relevant thread you might want to check: <a href="http://news.ycombinator.com/item?id=1415480" rel="nofollow">http://news.ycombinator.com/item?id=1415480</a><p>@metachris sorry the video format didn't work for you, but you're lucky I made quite a few takes with it -- my first try was 37 minutes of unfocused babble (instead of only 12 minutes of unfocused babble).<p>I plan to have followup videos which walk through coding up an app from scratch. Actually, I find screencasts tedious to make. I'm very comfortable giving talks in front of people, but something about sitting and talking to my laptop doesn't sit right. :)<p>And persistence is underway. Jo is built from my game UI library that is about a year old now. Jo is also my fifth JavaScript framework, and first to be made open source. I'm in it for the long haul. :)<p>@karanbhangui Thanks! The nice part about mitigating most platform issues through CSS is that apps should degrade pretty well without much JS fiddling. I plan to continue to push into less capable web platforms, though I really could use some help testing from folks who have those devices.<p>Check the docs: <a href="http://joapp.com/docs/#Class%20Heirarchy" rel="nofollow">http://joapp.com/docs/#Class%20Heirarchy</a> a lot of the widgets are up and running. Noticeable gaps which are due to be in the beta are: select (popup selection), knob, slider, checkbox, tab, option, and typed input like numeric and email. These have been lower on my list because they're all extension of core Jo UI elements.