One wonders if their choice of Open webOS is simply a matter of security through obscurity given their product. That's the only reasonable rationale here, but very likely not the rationale they used when deciding to use Open webOS as their platform.
They could have easily gone with TideSDK (http://www.tidesdk.org/
) and had a desktop application ready to go in very little time using HTML5/CSS/JS
with optional back-end code and deployed it to any number of desktop platforms--even Linux.
Using Open webOS for something like this seems almost backwards when you look at how many more fitting solutions are sitting out there--with far better APIs--that don't require plunking an entire OS on top of Linux to achieve the same net result.