This has been on my “to-do” for nearly a year and I’ve decied that I can no longer wait any longer and the time is now. So today I’m going to start working on My First Teams App - Validator for Teams.
What Is Validator?
Many years ago I wrote a web app to help individuals and customers with their Skype for Business Deployments. This app is still available(https://skypevalidator.com/) for those who are on Lync/Skype but one has to admit that it’s use has gone down with Microsoft Teams over the years. One of the items I wrote as part of Skype Validator was a tool to do simple HTTP/HTTPS Checks, Certificate Checks, Ping, etc.
These checks could be run ad-hoc or scheduled and run all the time. So I’ve decided that it’s time to take this tool, modernize it, and put it into Teams.
In order to have write an app we need to set some ground rules of what will be in the app, how it will function and more. So here is my list of to-do’s for my new app.
- Open Source: There is both a front-end and back-end we will need to open source as part of this.
- Language: We will use ReactJS for the front-end and WebAPI2.0 for the backend.
- Personal Tab: This will be where you can run ad-hoc tests.
- Team Tab: This is where you will be able to run reoccuring tests and report back.
- Bot: Not sure yet: Need to think if this would be helpful.
- Messaging Extension: I love Messaging Extensions. I was thinking maybe searching for past down events.
- Channel Messages: Yep, need to have them. System down alerts and such.
So that is my current plan. My hope is to weekly post where I’m at, what we accomplished and how you can also follow along and learn. Let’s see if I can keep up the weekly posts.