v2rayN: desktop subscriptions and routing
Top pick for desktop
v2rayN is a good fit for managing multiple subscriptions on a desktop. Create a separate group for each source so you can tell which subscription each node came from after an update. If one group fails to refresh, you won't need to rebuild the others. Windows x64 users can choose between the desktop and classic WPF editions. For a first install, start with the desktop edition's cross-platform interface; if you're used to the classic layout, stick with WPF. On macOS, choose a package for your chip. On Linux, first check your distribution's package format, then confirm your processor architecture.
For your first connection, start with the system proxy and test with an app known to use system proxy settings. If a browser connects but another app does not use the same outbound route, check whether that app has its own proxy settings before rewriting your rules. Enable TUN only when you need to handle traffic from apps that ignore the system proxy, and check whether it affects local network access. When editing routes, start with one easy-to-test rule to confirm the match order and outbound selection, then add exceptions one at a time.
v2rayNG: Android subscriptions and per-app proxy
Top pick for Android
v2rayNG is a good choice for setting up a subscription on Android for the first time. After importing the URL, update it, wait for the node list to appear, then select a node. On the first connection, approve the system VPN permission prompt. If the list is still empty after an update, check that the subscription URL is valid, the client can reach it, and its response uses a format the client can read. An empty list and a failed node connection are different issues and should be troubleshot separately.
Per-app proxy settings determine which apps send traffic through the VPN; client routing determines which outbound route handles that traffic. If an app is outside the VPN, adding a domain rule won't change its connection. Start testing with an app included in the VPN, then expand the scope as needed. If the connection often drops after the screen locks, check whether background restrictions, battery-saving settings, or another VPN app may be involved. Change system settings one at a time only if you can reliably reproduce the problem.
v2flyNG: for v2fly-compatible setups
Android alternative
Choose v2flyNG for core compatibility. If your configuration provider specifically requires v2fly, or you already have a configuration verified with that core, import it into v2flyNG and test a node. A successful import only means the client can read the input; it doesn't guarantee that every transport, security, and routing setting will work as-is. In particular, don't assume a configuration that relies on Xray-specific features can be migrated just because the subscription imports successfully.
To compare clients on the same phone, disconnect the active VPN before starting the other client. Test the basic connection on the same network, with the same compatible node and the same app, so VPN switching or node differences aren't mistaken for core issues. If you're keeping an existing v2fly configuration, check DNS and routing results separately. Being able to open a webpage doesn't prove that your original direct-connection exceptions were migrated correctly.