3 ms·

What sets this project apart from the MS Graph API? Are there any API features that Graph does not have? I have built an alternative Teams client for smart gla

by zorr 4y ago

What sets this project apart from the MS Graph API? Are there any API features that Graph does not have? I have built an alternative Teams client for smart glasses using only MS Graph and Azure Communication Services and it can already do most interactions related to chat/meetings/org etc.

denysvitali 4y ago
It's not using the MS Graph API and it's copying what the Teams Desktop client is doing. This gives you a way to run an alternative client in corporations where you don't have the possibility to use third party apps. On top of that, since it's not using the Graph API, we might get better features that will take long time to be available in the Graph API.
- Firmwarrior 4y ago
  I think it's funny that casual hobbyists can easily outproduce Microsoft's supposedly world class engineering organization. It's not even a question in anyone's mind either. You guys know you're going to beat them (or already have), everyone here takes it as a given, even the engineers at MSFT probably know it. Even if they try to stop you guys, they probably won't be able to pull it off unless they can manage it in court
  - zorr 4y ago
    Why is that funny? I think it is normal that a hobby team working in a silo on an alternative client with a low amount of users move faster than a full engineering organization working on a mass rolled out product used in corporate environment all over the world. For a new feature the hobby team can just hack away for a few nights, push the release and they are done. The engineering org needs to plan and coordinate the feature across multiple teams (web app, desktop app, mobile app, Graph, teams admin panel, o365 admin panel,...) and then make sure it fits well into the rest of the MS infrastructure (policies, permission scopes, IT admin controls, licensing, auditing,...). Legal might need to be involved. And then after aligning all those teams and waiting for each team to prioritize and do the work it needs to get into the MS roadmap as well going through the usual stages (private preview, public preview, General Availability). And once it hits GA it needs to be supported for many years.

by zorr 4y ago

denysvitali 4y ago

It's not using the MS Graph API and it's copying what the Teams Desktop client is doing. This gives you a way to run an alternative client in corporations where you don't have the possibility to use third party apps. On top of that, since it's not using the Graph API, we might get better features that will take long time to be available in the Graph API.

Firmwarrior 4y ago
I think it's funny that casual hobbyists can easily outproduce Microsoft's supposedly world class engineering organization. It's not even a question in anyone's mind either. You guys know you're going to beat them (or already have), everyone here takes it as a given, even the engineers at MSFT probably know it. Even if they try to stop you guys, they probably won't be able to pull it off unless they can manage it in court
- zorr 4y ago
  Why is that funny? I think it is normal that a hobby team working in a silo on an alternative client with a low amount of users move faster than a full engineering organization working on a mass rolled out product used in corporate environment all over the world. For a new feature the hobby team can just hack away for a few nights, push the release and they are done. The engineering org needs to plan and coordinate the feature across multiple teams (web app, desktop app, mobile app, Graph, teams admin panel, o365 admin panel,...) and then make sure it fits well into the rest of the MS infrastructure (policies, permission scopes, IT admin controls, licensing, auditing,...). Legal might need to be involved. And then after aligning all those teams and waiting for each team to prioritize and do the work it needs to get into the MS roadmap as well going through the usual stages (private preview, public preview, General Availability). And once it hits GA it needs to be supported for many years.