Three states your network client must show, and one it should hide
Most network clients have a single button and a lot of hidden state. That works until something goes wrong, and then the user has no vocabulary to describe what happened. Three states solve most of it.
1. Connecting is not the same as connected
The moment between pressing connect and traffic actually flowing is where users get lost. If the button keeps saying "Connect", people press it again, and again, and now you have three connection attempts and a support ticket.
Show the state explicitly: idle, connecting, connected, reconnecting, error. A spinner alone is not a state, it is an anxiety indicator.
2. The route is part of the state
"Connected" on a route with 400 ms latency is technically true and practically useless. Users cannot tell the difference between a slow route and a broken client unless you surface both facts together: which route, and how slow.
This one change replaced an entire diagnostics screen that nobody opened. The status line became the diagnostics screen.
3. The device count is invisible until it breaks
A per-account device limit is the most common "it stopped working" cause in consumer network clients, and almost nobody shows the count in the UI. One line under the status, 2 of 3 devices online, prevents a whole category of support requests.
What to hide: the route list
The opposite mistake is showing everything. A list of twenty endpoints with latency numbers is not transparency, it is a decision the user never asked to make. Probe, pick, remember, and expose a single override control for the people who actually want it.
The client I have been writing about is QuickQ: one-click connect, automatic route selection per network, native clients for Windows, macOS, iOS, Android and Ubuntu Linux, and one account with up to 3 devices online at once. I keep notes on the flow, and the product page is here if you want to see the result: https://quickq-check.com.cn/ — it is an independent write-up, not the vendor site, so verify current details before relying on it.