Microsoft 365 Microsoft Teams Microsoft Office365 Microsoft Azure Microsoft Graph Microsoft Flow Microsoft SharePoint
Mol, Flanders, Belgium
What experience would bring value to my users? Which development framework to use? What UI framework to use? These are just a couple of questions that come up in that design phase of your new Microsoft Teams application. We'll run through 10 most common things you need to consider when architecting your application, discuss the pro's and con's of each and provide you with the knowledge to make informed decisions next time you are architecting an application for Microsoft Teams.
Yannick (a Microsoft Office Development MVP) is born and raised in SharePoint, starting out his career almost 10 years ago when SharePoint 2010 was still new and shiny. The changing reality of the cloud made him expand his knowledge to the whole of Office 365 and Azure, but SharePoint and Microsoft Teams are still his focus areas. He is a Managing Partner and Cloud Solution Architect at Qubix, a Belgium-based consultancy firm, responsible for the technical underpinnings of products and solutions. Problem solving and development are his passion, still working day to day with code. He always asks the important questions: How does it work? What do you want to achieve? Do we really need development for this? Where's the coffee?