4 ms·
(self-promotion ahead) Since the Microsoft Teams client is well known for being quite frankly, terrible, as many have pointed out in this thread, I am working
by FastEatSlow 4y ago
(self-promotion ahead)
Since the Microsoft Teams client is well known for being quite frankly, terrible, as many have pointed out in this thread, I am working on my own, alternative Teams client: OperCom.
I'm building it as a simple, vanilla JS web application, in a SaaS model (since I need to keep bending to Microsoft's will). The Teams API isn't great to reverse engineer, but it's do-able and has been done (partially) before, but never to the extent required to create a full-featured app.
If anybody's interested, you can see its current status at [1] and keep updated with its progress 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
- halvo 4y agoNo need to reverse engineer, Teams has a public API https://docs.microsoft.com/en-us/graph/api/resources/teams-api-overview?view=graph-rest-1.0 https://docs.microsoft.com/en-us/graph/api/resources/teams-a...
- FastEatSlow 4y agoMicrosoft Graph requires the organisation administrator to enable extra user permissions or to add an app to allow users to use this, whereas by reverse engineering users don't need organisation administrator permission.
- ldh 4y agoOrg-level admin requirements are what stopped me from pursuing my own solution. Hopefully your approach will have better luck.
- FastEatSlow 4y agoThat's a shame. What was your product, and did you have any troubles with reverse engineering or did you not consider it?