So I did some testing, and with a little tweaking the Signal Chrome App can be run under the NW.js alpha as a standalone client. Both need to mature more before the combination becomes fully usable [1][2], but once everything is ready, this looks like a very simple way to set Signal up with cross-platform desktop apps.<p>[1] Signal-Browser doesn&#x27;t seem to be able to add contacts properly when used with the production server, and the staging server looks like it&#x27;s down right now.<p>[2] NW.js currently refuses to recognize Signal-Browser as a Chrome App unless I rename package.json to something else. Remote debugging doesn&#x27;t seem to work with Chrome Apps running under NW.js at the moment - the inspector just gives me an empty response for each page I try to access. And there will need to be some way of configuring the Chromium engine to use Signal&#x27;s self-signed SSL cert, though they&#x27;ll have to solve this for the Chrome App as well.