I built https://team-today.com in a lock down as a way for my remote team to see when people are on holiday, going to site, or wfh.
Since then it’s grown to include other features like desk booking and PTO approvals. But at it’s all been built around the core concept of seeing when your colleagues are working and where they’re planning on working from.
Great job!
How did you convince users to trust an unknown site to store their personal data?
This is one the things holding me back from implementing my side project ideas. I personally know that I won’t misuse users data but how do I really convince users.
We integrate into MS and Google which holds personal information such as names but we do make an effort to reduce the amount of personal information we hold.
The real difficulty is getting government or financial institutions to buy in, they have LONG approvals processes and require proof that certain security practices are being adhered to (ISO27001 helps but is costly).
Ding, ding, ding! This is correct. I was just ranting to my wife about this. Haha.
I always wonder, “How are these random companies able to convince folks to just give them personal data like that?” And of course, I already know the answer: Practically speaking, most folks don’t give a damn about their data! That’s unfortunate. (Well, not so unfortunate for the companies collecting all of it and their data brokers!)
React, Java, AWS. Took us about 6 weeks to build the initial MVP, each feature we add took a similar amount of time to implement, we typically iterate over things three times. We build something, make it better, then make it perfect. So far so good.
Since then it’s grown to include other features like desk booking and PTO approvals. But at it’s all been built around the core concept of seeing when your colleagues are working and where they’re planning on working from.