Great performance and user experience remain a topmost priority for us. Application launch time has seen improvements in the recent build. We will continue making improvements across the product including channel to chat switching and overall resource consumption.
This is working today in the web client on Edge & Chrome. The team is actively investigating feasibility in the desktop client.
Please check “Teams/Skype Consumer chat and calling interop” on the public roadmap at microsoft.com/microsoft-365/roadmap?filters.. for updates.Phil Carbone commented
At my company a lot of people have teens at home during the summer, etc. It doesn't make sense that they have to run another app just to communicate with people. In 2017+ communication, federated, is just a must. Especially if MS owns the communication channel. I am the decision make at our business in regards to this stuff, and not being able to bridge Teams over to the public skype is a huge problem - administrators should be able to choose what makes sense at their business (enable/disable public skype)