Shipping one client is a UI problem. Shipping five that behave identically is a process problem. These are the practices that kept parity manageable on a network client that runs on Windows, macOS, iOS, Android and Ubuntu Linux.
1. Write the connect flow down once
Before any code, we wrote the flow as a numbered list: install, sign in, connect, show status, switch route, disconnect. Every platform implements that list, in that order. When a platform wanted a different order, the default answer was no, and the reason had to be a platform constraint rather than a designer preference.
2. One status vocabulary
States are named identically everywhere: idle, connecting, connected, reconnecting, error. The words on screen differ by language, never by platform. This sounds trivial until a support ticket says "the Mac version is stuck" and the actual state is reconnecting on all platforms.
3. Latency is data, not decoration
The status line shows the live route and its latency. It is fed by the same measurement on every client, so a screenshot from a phone can be compared with one from a laptop. That single decision replaced a diagnostics screen that nobody opened.
4. Ship the boring platform first
We stabilised on desktop before mobile. Mobile adds background restrictions, battery rules and store review, and doing that before the core flow is settled means you debug two problems at once.
5. Keep the account model boring
One account, up to 3 devices online at the same time. No per-platform pricing, no separate mobile subscription. Users move between devices; the account should not care which one is in front of them.
What parity is not
Parity does not mean identical code. It means identical behaviour. The Linux build uses a different networking stack than iOS, and that is fine, because the user-visible contract is the same.
If you want to see the result, the flow is documented here: https://quickq-check.com.cn/ — it is an independent write-up, not the vendor site, and platform support or pricing can change, so check before you rely on it.
Top comments (0)