Mihri Minaz

The idea was like, how can we help individual to be more on time for their meetings, but also managing their time better with simple improvements. And then we later added a calendar integration, a focus Pomodoro timer, Slack integration so that everyone in your company can see that you are working on this specific task now and when you will be available next.

All these little features made people have less communication issues with their team. And then they loved it and they started using it. They gave feedback. Then from there, the next step for us was building the insights, the dashboard, something we call Fitbit for your calendar. We launched it on Product Hunt and we became the product of the day. And there, people loved it.

All these little features made people have less communication issues with their team. And then they loved it and they started using it. They gave feedback. Then from there, the next step for us was building the insights, the dashboard, something we call Fitbit for your calendar. We launched it on Product Hunt and we became the product of the day. And there, people loved it.

All these little features made people have less communication issues with their team. And then they loved it and they started using it. They gave feedback. Then from there, the next step for us was building the insights, the dashboard, something we call Fitbit for your calendar. We launched it on Product Hunt and we became the product of the day. And there, people loved it.

It's so crazy that people don't take this time to critically think about their meetings or they cannot protect their time for focus as well. So as a developer myself, I have seen so many people struggling with it. And the idea of this like insights was like so powerful that people could bring it to their retrospective meetings and show, okay, we have this much of meetings. How can we work on this?

It's so crazy that people don't take this time to critically think about their meetings or they cannot protect their time for focus as well. So as a developer myself, I have seen so many people struggling with it. And the idea of this like insights was like so powerful that people could bring it to their retrospective meetings and show, okay, we have this much of meetings. How can we work on this?

It's so crazy that people don't take this time to critically think about their meetings or they cannot protect their time for focus as well. So as a developer myself, I have seen so many people struggling with it. And the idea of this like insights was like so powerful that people could bring it to their retrospective meetings and show, okay, we have this much of meetings. How can we work on this?

the new feature. So that kind of helped people already address the problem with more data. And then, yeah, like the last feature we have is this work tool in size. And then people can also see what other team members are using. And for managers and team leads, that also gives lots of information around tool adaptions.

the new feature. So that kind of helped people already address the problem with more data. And then, yeah, like the last feature we have is this work tool in size. And then people can also see what other team members are using. And for managers and team leads, that also gives lots of information around tool adaptions.

the new feature. So that kind of helped people already address the problem with more data. And then, yeah, like the last feature we have is this work tool in size. And then people can also see what other team members are using. And for managers and team leads, that also gives lots of information around tool adaptions.

So we used the native app building like we build it with Swift. And the first version didn't even have any backend, just had the version check endpoint. So everything was local, except the tracking. So we were tracking people's activities to understand if this feature is used, how it should be used, and for iteration. We just released it in a couple of weeks, actually.

So we used the native app building like we build it with Swift. And the first version didn't even have any backend, just had the version check endpoint. So everything was local, except the tracking. So we were tracking people's activities to understand if this feature is used, how it should be used, and for iteration. We just released it in a couple of weeks, actually.

So we used the native app building like we build it with Swift. And the first version didn't even have any backend, just had the version check endpoint. So everything was local, except the tracking. So we were tracking people's activities to understand if this feature is used, how it should be used, and for iteration. We just released it in a couple of weeks, actually.

It was just a DMG file on a Google Drive folder, and we were sending the link of the drive and we didn't even have decent version system. And then of course, everything else followed later.

It was just a DMG file on a Google Drive folder, and we were sending the link of the drive and we didn't even have decent version system. And then of course, everything else followed later.

It was just a DMG file on a Google Drive folder, and we were sending the link of the drive and we didn't even have decent version system. And then of course, everything else followed later.

Not having a backend, but having a tracking system that shows a lot of our methodology, right? We always want to ship code where we can experiment something and we can understand if this worked or not. We did not need any backend because we could use local event calendar from Apple's system.

Not having a backend, but having a tracking system that shows a lot of our methodology, right? We always want to ship code where we can experiment something and we can understand if this worked or not. We did not need any backend because we could use local event calendar from Apple's system.

Not having a backend, but having a tracking system that shows a lot of our methodology, right? We always want to ship code where we can experiment something and we can understand if this worked or not. We did not need any backend because we could use local event calendar from Apple's system.

be needed that if people really used it daily or not so our versioning was very important for us because when we wanted people to update we did not want them to keep using an older version so from the first release you need to have some fundamentals and that's how we went about it and then