dotnet-smartcomponents / smartcomponents

Experimental, end-to-end AI features for .NET apps
694 stars 61 forks source link

Teams / Outlook Components #48

Closed DjeeBay closed 5 months ago

DjeeBay commented 5 months ago

If we have an AD user, could we imagine a smart text input where the user asks about his mails / calendar or Teams discussions and the component shows the results or links towards Teams/Outlook ?

Input examples :

A more advanced feature could be to interact with Teams / Outlook by sending emails or discussion, plan meetings, directly by asking it in the input.

This way it would give really powerful features where a Blazor app is easily connected with other Services and can centralize / deliver a lot of user data and interactions without the need to switch between dedicated apps.

User could access to almost everything from one input thanks to AI + Microsoft Graph APIs.

SteveSandersonMS commented 5 months ago

To me this sounds like a classic chatbot/copilot scenario, since it's about asking questions and getting answers. The UX would likely look more like a chat thread with multiple messages rather than a single text input. This is basically the core functionality of Windows Copilot or Teams Copilot.

It's all definitely possible but the hard part isn't really the UI, it's connecting it with many backend services. There's lots of documentation about how to do this kind of thing at https://developer.microsoft.com/en-us/copilot.

While I think this is all super functionality, I would consider it outside the scope of what SmartComponents is trying to achieve, since SmartComponents is specifically about scenarios where it's possible to drop in prebuilt UI components with very little developer work, and the full copilot scenarios always involve a lot more integration with external services than that. Hope that's OK!