Currently, the Linux client lacks its own UI - it must be used with a separate server to act as its UI. The problem is, if you're already using a remote central server to coordinate multiple clients you can't run that server locally - and having to depend on a remote server as the only form of UI makes it impossible to work while offline (i.e. on flights, out in the field, etc). Furthermore, the only way to use screenshots is by syncing them - which will consume an immense amount of additional data, which may not be feasible if your clients are on metered connections. Thus I really think some form of a true local UI is still needed. Options:

1) Port the Windows client to Linux, natively. Obviously this is by far the most ideal from a user's standpoint, as the Windows client is far more convenient & powerful than a browser-based solution.

2) Support the Windows client running in WINE.

3) Have the Linux client fire up its own internal webserver, to act as its own dedicated UI. This loses the benefits of that great Windows UI, but would greatly simplify setup, enable users to work offline, and avoid the need to remotely upload all screenshots. Then the Linux client could still be connected to a "true" central remote server, in the same way as Windows clients.