Most of your points are already covered. 1. You could do this from day one. You didn't have to include Mojo or any other device specific framework. index.html

Most of your points are already covered. 1. You could do this from day one. You didn't have to include Mojo or any other device specific framework. index.html was enough (you would also need appinfo.json for metadata and packaging.) With Enyo, even if you use the framework, there is no longer a need for any specific directory structure. 2. They have CouchDB (really not sure, it is a JSON object store though) running and accessible to all apps via a service bridge. This db is also backed up to the cloud for when user restores or changes devices. 3. Same service bridge. Which is nothing more than an AJAX call to a specific url. 4. They already run in Chrome with Enyo. With Enyo, I think this is actually possible. 5. Or keep it as a huge source of revenue. Nobody but HP's marketing dept wants webOS on printers though, I'll give you that. Think John Deere acquiring Ferrari and putting their engines into lawn mowers, because "it's the logical thing to do." I'll add 6. 6. You can write your own Node.js services that are accessible via the same service bridge mechanism. webOS is the mobile OS we should be cheering for to survive. It is slightly ahead of the curve and is about to be killed off. The news about Mozila WebAPI are an indicator.