Having worked extensively on a project that used something similar (we switched from Titanium Desktop to Mozilla's Chromeless project over the course of the dev

Having worked extensively on a project that used something similar (we switched from Titanium Desktop to Mozilla's Chromeless project over the course of the dev cycle) as an underlying technology, I see a few things this needs to address. There IS a valuable niche here - Chromeless and Titanium are the only real competitors - and neither are solving it particularly well (though both slightly nicer than Appify as it currently stands). First: Lower-level APIs. That means I need Javascript hooks into file access, menu bar content, cross-domain requests, camera and microphone, etc etc etc. Without this, no meaningful apps can be created. Second: Config. Let me specify the startup window parameters (perhaps using a config JSON file included with the app source). Height, width, and position at least. Maybe support for multiple windows? Third: Support. This one is where Titanium and Chromeless both fall flat on their face. Titanium Desktop is dead; the company has shifted 100% of efforts into an equivalent platform for mobile devices. Things are broken and aren't getting fixed, which makes it unfeasible to use for long-term development. The same applies to Chromeless; I've submitted dealbreaking bugs to the github - things simply Don't Work - and receieved no developer response whatsoever. Again, it seems as if the dev team has lost interest. I really hope that you're planning on pursuing this as more than a one-off github project, because you have the opportunity to dominate an area of the "app development for web developers" market that NOBODY is currently solving. Best of luck. * EDIT: And for all of those who (largely correctly) will claim "desktop is dead, stop pretending it's the web" - you're right. The thing is, the project I was working on found ourselves in an interesting position, and we certainly weren't the only ones. We wanted to build a web app, and knew that the web was the future of our product. However, there was functionality we needed (filesystem access, non-flash microphone access, etc etc) that simply doesn't exist (yet!) on the web. Specifications and standards have been proposed and are being implemented, but we unfortunately can't assume that every potential user has a Chrome nightly build. Distributing an app running in an invisible web environment allowed us to develop the code we would be able to use long-term, while giving us a predictable, highly up-to-date, and extensible (via native hooks thru javascript) access to the local machine. Also: cocui looks awesome, and worth checking out. My team has since decided to accept our limitations and move to strictly web, but if I was considering a similar project again I would definitely consider it.