3 ms·

I suggest you try the web app version, it’s faster and more stable. In fact, I believe Microsoft will replace the desktop client with a web app shell. You can

I suggest you try the web app version, it’s faster and more stable. In fact, I believe Microsoft will replace the desktop client with a web app shell. You can try it out today; 1. Install the Microsoft Edge Web browser on Mac or Windows 2. Log into https://teams.microsoft.com https://teams.microsoft.com 3. Click … > Apps > Install this site as an app 4. Enjoy!

listless 4y ago
Desktop version is electron
- naikrovek 4y ago
  that is changing "soon" (with an ever-changing definition of "soon")
  - gorbypark 4y ago
    What is the “new” version’s tech stack? I always thought that with the Office and Windows team slowly adopting React Native for some features that they would redo Teams with that. Realistically they could start out with a React Native shell and just use web views for most functionality at first to replace Electron (and eventually, hopefully, rewrite some core functionality in RN and/or actually native bits).
    - naikrovek 4y ago
      .net native application per platform, with WebView2 views but logic moved to some .net language, probably C#. I believe all application logic is moving to .net with the visible elements being HTML & CSS, but do not remember where I read it, so take it with a grain of salt. if there was mention of react native, I do not remember it, but I gloss right over mentions of most web frameworks, so it may play a role.
      - FastEatSlow 4y ago
        It's surprising that nobody has mentioned that MS is calling this Teams 2.0. They're rewriting to React with WebView2. I don't believe any of the functionality will be in the C#, but we'll see. It's probably worth me mentioning that I'm building a Teams client using Typescript and Tauri! https://opercom.co.uk https://opercom.co.uk
        naikrovek 4y ago
        you can check here now if you want to. https://github.com/ItzLevvie/MicrosoftTeams-msinternal/tree/master/src%2Fv2.0 https://github.com/ItzLevvie/MicrosoftTeams-msinternal/tree/...
TurkishPoptart 4y ago
Thanks so much, I will try this! Much appreciated!
Jaruzel 4y ago
For Chrome: chrome.exe --app=https://teams.microsoft.com you can also add these two for an isolated copy of each Teams instance: --profile-directory= --user-data-dir=

listless 4y ago

Desktop version is electron

naikrovek 4y ago
that is changing "soon" (with an ever-changing definition of "soon")
- gorbypark 4y ago
  What is the “new” version’s tech stack? I always thought that with the Office and Windows team slowly adopting React Native for some features that they would redo Teams with that. Realistically they could start out with a React Native shell and just use web views for most functionality at first to replace Electron (and eventually, hopefully, rewrite some core functionality in RN and/or actually native bits).
  - naikrovek 4y ago
    .net native application per platform, with WebView2 views but logic moved to some .net language, probably C#. I believe all application logic is moving to .net with the visible elements being HTML & CSS, but do not remember where I read it, so take it with a grain of salt. if there was mention of react native, I do not remember it, but I gloss right over mentions of most web frameworks, so it may play a role.
    - FastEatSlow 4y ago
      It's surprising that nobody has mentioned that MS is calling this Teams 2.0. They're rewriting to React with WebView2. I don't believe any of the functionality will be in the C#, but we'll see. It's probably worth me mentioning that I'm building a Teams client using Typescript and Tauri! https://opercom.co.uk https://opercom.co.uk
      - naikrovek 4y ago
        you can check here now if you want to. https://github.com/ItzLevvie/MicrosoftTeams-msinternal/tree/master/src%2Fv2.0 https://github.com/ItzLevvie/MicrosoftTeams-msinternal/tree/...

TurkishPoptart 4y ago

Thanks so much, I will try this! Much appreciated!

Jaruzel 4y ago

For Chrome: chrome.exe --app=https://teams.microsoft.com you can also add these two for an isolated copy of each Teams instance: --profile-directory= --user-data-dir=