feat: connection quality indicator and network preflight#34
Open
robinandeer wants to merge 1 commit into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
robinandeer
changed the title
In-call warnings use LiveKit quality plus WebRTC RTT/loss when the server still reports good. Preflight is WebSocket-only and non-blocking; optional ConnectionQualityDevTools for local verification.
robinandeer
force-pushed
the
05-26-feat-add-connection-quality-indicators-and-preflight-checks
branch
from
fe8f38a to
018a047
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Show a debounced in-call warning when the user’s network is degraded or reconnecting, without blocking the call with preflight UI.
Integrators need a subtle signal when avatar calls may stutter on poor networks. LiveKit’s server-reported quality often stays
goodunder bandwidth limits (e.g. DevTools 3G), so warnings never appeared without RTT/loss fallback.Verify
bun run build && bun test packages/just dev-nextjs-simple— start a call; no preflight banner<AvatarCall connectionDebug connectionPreviewWarning />or<ConnectionQualityDevTools />— amber dot on the warning pill, metrics top-rightManually verified locally with debug overlay and preview pill (debug not enabled in nextjs-simple by default).