Following up on the recent discussions about client fragmentation: my previous text post was a bit too abstract without anything visual to show, so here is a quick GIF of our UI running on a real device.

We've been heads-down building \*\*VPNStack\*\*—an all-in-one Android client on top of Sing-box 1.14 with a custom Jetpack Compose interface.

The monolithic core is already built and working under the hood. It compiles VLESS-Reality with Vision, Hysteria 2 with port-hopping, native AmneziaWG, and a fallback WebRTC video stream transport into a single Go/CGO binary without runtime conflicts.

On the UX side, we wanted to completely move away from raw config tables and JSON editors: the central power glyph pulses into glowing fuchsia with a 60 FPS live oscilloscope trace reflecting network pulse through the hollow center, Remnawave subscriptions sync cleanly in the header with remaining days, and per-app bypass is accessible right from the main view. We're also packaging a White-Label engine so node operators and communities can generate their own branded APKs tied to their server fleets with built-in billing.

The core is solid, and we're currently polishing the UI and edge-case routing before dropping the first public alpha build.

Would love to hear your thoughts on the visual feedback and layout. Any specific indicators or controls you feel are missing from the main screen?

[Showcase] Our last text post was pretty dry without visuals, so here's a quick GIF of VPNStack running on Android: Sing-box core (Reality, Hys2, AWG, WebRTC) + Remnawave sync + live ECG UI.