3 ms·
I can't find any reason other than "we will only code things once and run everywhere". Considering the scale of users, a native client is a no brainer For a wh
by collaborative 4y ago
I can't find any reason other than "we will only code things once and run everywhere". Considering the scale of users, a native client is a no brainer
For a while I have contemplated creating a lightweight native version of Teams. According to the Teams API it should be possible, I believe
It can simply be c#, no need to go any deeper. But it would be a huge boost in performance
- JohnFen 4y agoI would love ANY alternative to Microsoft's Teams app!
- FastEatSlow 4y agoI'm working on a vanilla JS web app alternative if you're interested, OperCom. You can see its current status at [1] and keep updated at [2] [1] https://blog.opercom.co.uk/posts/news-13-08-22/ https://blog.opercom.co.uk/posts/news-13-08-22/ [2] https://www.opercom.co.uk/contact https://www.opercom.co.uk/contact
- pjc50 4y agoAt this point you discover that there are at least three different options for C# UI, all of which have significant drawbacks. The performance of a WinForms Teams UI would be fantastic, though.
- collaborative 4y agoAgree on WinForms, but why wouldn't WPF also be fine? Granted it leaks a bit of memory here and there, but not much
- marwis 4y agoDevelopment of WPF was abandoned more than decade ago.
- collaborative 4y agoI thought WPF was the de facto current standard for Windows apps and everything else (MAUI etc) is too experimental and hardly promising MS certainly is using WPF in some areas (Dynamics 365 client framework comes to mind)