case study

Learn more
Scroll down

Timeateam App

Project's milestones

Phase one


The concept behind Timeateam originated from a need for better communication between our project managers and developers. We had been relying on Google Docs, but as our company and project log expanded it became painfully obvious we needed something more streamlined and intuitive.


We needed an application that allowed us to maintain our liberal and open policy towards employee work-time schedule while not undermining the development process. Timeateam was the simplest solution, conceived as a minimalist application with a few basic functionalities. We just wanted something simpler and easier than a pen/paper system.


With Timeateam, employees manage their schedule in an open environment for all members of an assigned group. They can adjust their hours as needed without having to communicate to project managers or anyone specifically. Everyone can see their schedule in real-time.

Phase two


Timeateam was designed entirely in-house which gave us the freedom and time to design the product without a strict deadline.


For the prototype, we wrote a list of functionalities we wanted built into an MPV.  We started with basic A/B testing of wireframes.


We continued to experiment with the wireframes, adding and removing features until we settled on a design we felt was most consistent with our core needs. This phase took 3-4 weeks as we didn’t have to consider a client’s deadline and deliver a project as quickly as possible.

Phase three


We have learned bringing a new software to our established process is normally more time-consuming than going with what our developers are already familiar with.


But since Timeateam was being developed independent of a client, we knew it was an excellent opportunity for us to learn a new design technology.


One of our designers assigned to Timeateam starting playing around with Principle, and it soon became clear to everyone this program would help us create the most dynamic animation.

For the design process, we like to have a prototype completed – with all details planned out on the final layouts and exported with our Sketch plugins. Only then do we start writing code and begin the development phase.

Phase four



At the beginning, developing was definitely challenging for us. We wanted the project to be workship-oriented and team-developed, giving our interns and level-one developers the opportunity to improve their skills.


Kuba, our CTO, chose Laravel as the fundamental tech solution. For the back-end, Laravel was a game-changer for us and took our PHP developers to the next level.


Although the project was more costly and time-consuming than our previous work, it paid for itself through the knowledge we gained during the development cycle.

Tech solutions

These are tech solutions used to develop Timeateam


  • Principle
  • Sketch


  • Angular
  • Laravel