> is no match for an unreliable network with zero latency guarantees
UX is a disaster. At least they could display latency / packet loss charts for both directions. Volume gauges. Warnings on audio feedback or high compression.
We spend too much time asking if volumes and quality are ok.
> We spend too much time asking if volumes and quality are ok.
I agree, but that happens on teleconferences using phonelines, too. So not really a video conference only thing.
I'm not sure if all those problems are truly UX only problems though. How useful is an n-way latency graph Volume gauges, I see that more as a hardware fault. When using a phone or an iPad, that question never comes up. Audio feedback, IMO hardware/driver issue. Again, speakerphone is okay. High compression is obvious from the blockiness.
UX is a disaster. At least they could display latency / packet loss charts for both directions. Volume gauges. Warnings on audio feedback or high compression.
We spend too much time asking if volumes and quality are ok.