5 votesNathan Hartley shared this idea ·
A co-worker has found that a "secondary ringer" feature is now on the road map. https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=Teams%2Csecondary%2Cringer
I was excited to learn that within Teams the headset controls are separate from the primary device audio controls used for the ringer. This meant it should be possible to use the new "App volume and device preferences" within Windows 10 to configure settings specific to Teams. At first, I did not see Teams in the list and wondered if this was due to it not being installed in a standard Microsoft way (Hockey App). I then called myself and the app appeared. Unfortunately, changing the settings for the app did not work as expected. If it worked, this might be the answer.
How is it that a User Voice request like "Compact mode" could have 7,700 votes, or "Need full capabilities of Planner in Teams" has over 6,000 votes or "Support for Private Channels" has 16,500 votes, when a basic feature missing from the application only has 319 votes?
Could the problem be that Teams is a Progressive Web App (PWA)? Do PWAs only have access to a single audio device at a time?
At least the ability to turn off the automatic emoji conversion of emoticons and code that looks like an emoticon.
This feature is on the backlog. We’ll update when we have more details to share.
Sean Ellis, "By using a decently-supported cross-platform UI framework".
Like, using .Net Core?
This feature is still in the works. There was some adjustments to the overall strategy.
I’ll try to get some additional details and share them with you.
If this ( https://www.microsoft.com/store/productId/9NSV22GV8Q6N ) is the new Store App, why does the name restrict it to being the "Windows S" version? I thought the goal was for ALL Windows software to eventually be installed/updated/removed through the Store.