Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> As far as Teams vs. Meet, it seems like Teams is great when you are working with people that have climbed it's learning curve.

Can you give one example?



I can give several. Most of them are not Meet specific but how Meets integrates with rest of Google Products. This is actually overall massive problem with Google Workspaces in general IMO.

1) You can call someone in Teams. Sure, Google Chat has "Start Meeting now" but it's very passive. I know some will see this as negative but ringing has massive advantages around UX.

2) Chat, Teams will persist chat after meeting ends. In fact, depending on how you hold the meeting, it might dump the contents into chat channel so it's preserved in more open manner.

3) You can have visible meetings. You can start a meeting in a Teams chat channel so everyone can see the meeting is going on. It creates that in the office feeling of two people working on a whiteboard nearby that if topic interests you, you can join in.

4) Sharing Documents, Add Word Document to meeting, everyone is granted permissions. Done.

The fact so many Google Workspaces companies have Slack is just frustrating. You have these two products that barely talk.


> The fact so many Google Workspaces companies have Slack is just frustrating

True, but Teams is so buggy and had in many areas has no UX per se.

I'd take for 2 great products (Slack + Meet) with bad integration vs great integration of shitty products.


Coming from a google meet org I consider the lack of "call someone" a killer feature


unreachability is not a driving feature of communication infrastructure though


You've nailed a lot of the problems I see with slack+meet

They do not integrate at all on these topics. Slack really could expand here (outside of huddles).


Google meet has 4 now




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: