4 ms·
I really like using tuple, but there’s a couple of things I’d really like to see: - an idea of how much bandwidth it’s currently using or needs. I often find i
by glenjamin 5y ago
I really like using tuple, but there’s a couple of things I’d really like to see:
- an idea of how much bandwidth it’s currently using or needs. I often find if I’m on a patchy connection it’s unclear how changing the settings will have an effect
- make the video face stuff more prominent, especially for multiple monitors. I work 100% remote so when pairing I like to put my Co-workers full size on my second screen while I work on the primary screen, which helps us feel more connected.
- r00k 5y agoMessage received!
- univerio 5y ago+1 on making video better. The janky video feature feels like such an afterthought compared to the impeccable screensharing/pairing feature. I've had to resort to using Tuple with Zoom just for the video sometimes because the webcam freezes for no reason. I'll also offer one related piece of feedback: the "calling" metaphor for initiating a session is quite awkward. Compared to Zoom, where you share a link/code once and then you're free to join/leave the room, in Tuple you have to ask the other person to call you every time you drop; this in particular does not play well with the forced version upgrades -- you ask the other person to call you out-of-band, and you answer, except oops, you need to upgrade Tuple, so you upgrade and restart Tuple, and now Tuple has forgotten about the last call so now you have to ask the other person to call you out-of-band again! This is a UX wart that I'd love to see fixed!
- r00k 5y agoI agree with all of this! Thanks for writing it up. Improving webcams (a lot), URL-based rooms, and never having a call interrupted by a required update are all on my list for next year.