Client Apps Overview: Happ, v2rayTun, Hiddify, and Who Gets What

The client app is the face of your service. A person sees neither the panel, nor the cascade, nor Reality — they see one app and one button. Pick the right app for them and half your support tickets simply won't happen. Let's unpack who gets what for which platform and how the clients differ from one another.

This material is about engineering your own infrastructure and is educational in nature. You are responsible for complying with the laws of your own jurisdiction.

Why the client-app choice is no small thing

You can configure the server perfectly, but if the client installed a clunky app, they'll still write "it doesn't work." The app is responsible for subscription import, device-side routing, kill-switch, DNS, and whether it sniffs domains (which determines whether a Russian site goes direct or takes a detour through the node). Half of support tickets aren't server problems — they're a wrongly chosen or unconfigured app. So it's worth assembling the "what to install" list once and dropping it into the client's bot.

What to install for which platform

There's no universal "best" — there's the convenient one for a specific platform. But if you have to name two names that cover almost everything and almost everyone, it's Happ and Hiddify. They're the friendliest: they understand multi-subscriptions, can do routing (bypass for Russia out of the box), and auto-update the subscription. Those I recommend first.

Two classes of clients: "extended" and plain

This distinction is important to understand, because it determines how you set up the subscription.

Extended clients — Happ, INCY, and kin (FlClash X, Flowvy, and others). They understand extra hints from your panel: human-readable labels instead of VLESS | TCP | REALITY (Server Description), an encrypted subscription, announcements under a name. With such clients you can present the service in a human way — the user sees "Connect," not a jumble of protocols.

Plain clients — v2rayTun, v2rayNG, V2Box, Streisand, NekoBox. They work and are reliable, but they don't read panel hints: where an extended client shows "YouTube ad-free," a plain one shows a technical string. That doesn't make them bad — the presentation for them is just poorer.

The takeaway for the operator: if you're building a service around nice UX, aim for Happ/INCY as the primary client. If your audience is mixed — keep instructions for all, but know where your hints will fire and where they won't.

Who gets what: quick selection logic

• Mass non-technical client, iOS/Android → Happ. One button, clear import, RF bypass out of the box.
• Someone who cares about iOS nativeness → Streisand. Light, tidy, free.
• Desktop, Windows/Linux/mac → Hiddify. Cross-platform, does everything Happ does, plus it's convenient on a big screen.
• Android, if Happ didn't click for some reason → v2rayTun. Flexible, but needs attention to sniffing settings (otherwise RF sites go the wrong way).
• Advanced user / desktop with fine-tuning → NekoBox / sing-box. Maximum control, but also maximum manual work.

What to explain to the client regardless of the app

Three things that cut the most tickets are almost the same everywhere:

• Kill-switch / always-on VPN — so that on a drop, traffic doesn't leak past the tunnel. On Android this is turned on in the system VPN settings, not in the app itself.
• Bypass for Russia (split tunnel) — Russian sites and banks go direct, everything else through the node. Without it the client loses access to banks and marketplaces that cut VPNs.
• DNS — if the app connects slowly, switching DNS to Google (8.8.8.8) or Quad9 (9.9.9.9) often fixes it. Cloudflare (1.1.1.1) is slow in RF — I don't recommend it.

The mechanics of each of these settings, as well as step-by-step subscription import, we cover in separate practice articles for each client. Start with the one matching your client's platform, then continue through the section.