English 简体中文

Go Backend / WebRTC Engineer

I build and debug backend systems and real-time media applications, with a focus on signaling, call reliability, Android and OpenHarmony integration, and production troubleshooting.

Portfolio · Selected work · Engineering notes · Contact

• RTC gateways and call reliability — signaling, session lifecycle, ICE/STUN/TURN, coturn relay paths, and weak-network troubleshooting.
• Production Go backends — concurrent services, gRPC, WebSocket and MQTT event flows, deadlock analysis, and lifecycle reliability.
• Audio and media debugging — Pion WebRTC, FFmpeg workflows, RTP-based media, WebRTC audio 3A, and AEC dump analysis.

A Windows screen-mirroring and remote-control tool for OpenHarmony and Android devices. It supports ADB/HDC device routing, single- and multi-device workflows, local-network connections, and offline Windows distribution.

Product page · GitHub releases

A Go service for managing FFmpeg streaming processes and RTMP, RTSP, HLS, and FLV workflows. The project extends earlier EasyDarwin work and documents implementation tradeoffs and known limitations.

Source code

Most of my production RTC gateway work is private. The engineering notes below document the parts I can share: Android and OpenHarmony call behavior, coturn and ICE paths, audio 3A, playback latency, and production failure analysis.

• 2026-06-14 — Debugging Android WebRTC Audio 3A with AEC_DUMP and Audacity
• 2026-06-09 — Debugging WebRTC Audio Playback Latency on OpenHarmony 5.0
• 2026-06-06 — WebRTC Echo and Noise Optimization on Android 14 Bedside Devices

Read all engineering posts

• Backend: Go, gRPC, WebSocket, MQTT, MySQL, Redis
• RTC and media: WebRTC, Pion, coturn, ICE/STUN/TURN, FFmpeg, RTP/RTSP/RTMP/HLS
• Platforms: Android, OpenHarmony, Linux, Docker

I'm open to Go backend, RTC infrastructure, and real-time media roles or technical collaboration.

Portfolio · Contact · X / Twitter