Separate client/bouncer for using only client or bouncer part?

From the description of Convos I conclude that it has an integrated bouncer running on a server, and a client part that runs in a browser and connects to the bouncer. Is it possible using only the client part or only the bouncer part of Convos?

**Is your feature request related to a problem? Please describe.**

I use IRC on a desktop as well as on my smartphone with a dedicated Android app. Both are connecting to a running ZNC on my server. The advantage of IRC in general is that I do not have to use the same software on every device. Combined with ZNC I am also always-on (for others), have message logging and can connect with different clients, even at the same time.

On my smartphone using a web application in a browser just doesn’t work right. Notifications are difficult, and the graphical elements are mostly too small, compared with a native app. Also there are additional browser UI widgets that are unnecessary in this case.

**Describe the solution you'd like**

It would be great if one could configure using an external bouncer, e.g. ZNC. This way I would still get all the ZNC bouncer advantages, use a different client on mobile, but can use Convos on my desktop computers like a regular IRC web client.

Alternatively would it be possible accessing Convos’ bouncer with a different IRC client? In that case I could swap ZNC for Convos and use either Convos client (desktop) or a native Android client (on smartphone) without losing online status or logging.

Start by mapping how Convos separates its browser client from its integrated bouncer, then compare those boundaries with the external ZNC and native IRC-client use cases described here. Done means the project has a defined approach for using an external bouncer or accessing Convos through another IRC client, with the supported connection model documented.

Written by the indexing model from the issue text.