4 ms·
1) Is it really? Slack already has chat, and 1-1 calls. I don't see a huge UX leap to expand 1-1 calls to big meetings. 2) So what? If you have the technology
by serverholic 6y ago
1) Is it really? Slack already has chat, and 1-1 calls. I don't see a huge UX leap to expand 1-1 calls to big meetings.
2) So what? If you have the technology for big meetings then you don't need to engineer anything else for 1-1 meetings. That's just UI at that point.
3) This makes sense and is probably the main reason hangouts failed. However, I wonder if they could have multiple sub-products under the hangouts umbrella but still keep it a unified piece of software.
- crazygringo 6y ago> If you have the technology for big meetings then you don't need to engineer anything else for 1-1 meetings. Unfortunately not. A framework for large video meetings is necessarily routed through a central server which can add tremendous latency, even between two people near each other. The architecture for 1-1 meetings tends to be peer-to-peer and focus on minimizing latency. There are a lot of architecture tradeoffs between the different models. Choosing an optimal architecture for each product turns out to be quite necessary.