{"id":2455,"date":"2016-01-22T10:41:47","date_gmt":"2016-01-22T07:41:47","guid":{"rendered":"https:\/\/everhour.com\/blog\/?p=2455"},"modified":"2023-04-11T17:02:54","modified_gmt":"2023-04-11T14:02:54","slug":"everhour-v2-coming","status":"publish","type":"post","link":"https:\/\/everhour.com\/blog\/everhour-v2-coming\/","title":{"rendered":"Start Working on Everhour 2"},"content":{"rendered":"

Folks,<\/p>\n

As always, before making any significant changes in Everhour we are sharing our thoughts with you, our super loyal customers, to make sure we are on the right track.<\/p>\n

The huge changes are ahead.<\/p>\n

For the very first time, we have introduced integrations in Everhour more than a year ago. At that time the idea was simple:  “What if not just reporting the activities but making users able to refer to their existing tasks in third-party project management tools!<\/em>” This is how synchronization was born.<\/p>\n

<\/p>\n

Then we thought: “And what if we can enhance these third-party tools with all the necessary time tracking features! Right there!<\/em>” Soon afterward, we introduced our browser extension.<\/p>\n

The first tool we integrated with was GitHub, as we were actively using it internally. And that was the exact time we were barking up the wrong tree.<\/p>\n

What\u2019s the common number of repositories (= projects) a small company has? How often are they created?<\/p>\n

\u201cWHEW, pretty rare,<\/em>\u201d we thought. For this reason, we didn\u2019t bother that you must first create a project in Everhour and then link it to the project in GitHub. Just a few minutes once a month or even rarer.<\/p>\n

Problem #1<\/h3>\n

The real problems began when we started to integrate with systems like Asana, Basecamp, and Trello. In these cases, the \u201cproject\u201d is a more flexible and general entity. The project can represent a client (Google), activity (Marketing, Development), campaign (Blackfriday Sale), or even a feature (Integrate X with Y).<\/p>\n

In other words, projects are very common and there are many.<\/p>\n

With our approach users have to keep in mind constantly that if they have a new project, they need to create it in Everhour. The majority forgets to do it that is why we were missing a timer button.<\/p>\n

Furthermore, all new users struggled with signup complexity. It requires some diligence to transfer your existing structure from an external tool into Everhour.<\/p>\n

It should be about something different.<\/p>\n

Solution<\/h3>\n

So, what are we going to come up with? It\u2019s pretty damn simple! \ud83d\ude42<\/p>\n

A new user clicks the “Connect to Asana” button (or other systems) thus telling us, “OK, I use Asana – here it is (giving us access) – sign me up!<\/em>“<\/p>\n

We automatically synchronize all the existing parts of the structure – projects, tasks, team members – and let the user track time right away. Each team member (upon standalone invitation) clicks the same button to log in. During the first login procedure, we’ll automatically associate him with the right team and authenticate. That\u2019s all.<\/p>\n

In the future, when there is an action in Asana, Everhour detects and handles it automatically. No need to duplicate the same steps.<\/p>\n

Ok, what\u2019s about existing customers?<\/h3>\n

Right, once the new version is ready, all new users will only be able to sign up there. At the same time, the old version will keep working.<\/p>\n

The migration will take place gradually and consistently. We will do a script that transfers all the clients\u2019 existing data into a new structure, so no data will be lost.<\/p>\n

Yes, it sounds like a perfect scenario, but there is always a place for some sort of force majeure (let’s be honest!). Therefore, migration will be done in portions. If something goes wrong, we will be able to focus on each individual case and solve the problem as quickly as possible.<\/p>\n

Problem #2<\/h3>\n

The second important issue is our reports. Yes, we have plenty of combinations, but sometimes it\u2019s not easy to find the right one. In addition, all of them are static, so you can\u2019t change their structure e.g. add a new column or change the order.<\/p>\n

In the new version, we want to go the other way. You\u2019ll have a few predefined reports (just as an example), but you are free to change them, create new and save them.<\/p>\n

When?<\/h3>\n

We have already finished with the new synchronization engine. Looks pretty good, it is left to verify some extreme cases.<\/p>\n

In addition, we are almost done with new UX for the major pages and some early working prototypes, so we can try them internally and make sure they are easy to use.<\/p>\n

You can see some early mockups below:<\/p>\n

Wireframe 1<\/a> – Time Tracking page<\/p>\n

Wireframe 2<\/a> – As-You-Type Suggest<\/p>\n

Wireframe 3<\/a> – Reporting<\/p>\n

Wireframe 4<\/a> – Reporting (Expanded filter)<\/p>\n

Wireframe 5<\/a> – Reporting (Reports menu)<\/p>\n

In the near future, our main priorities will be designing and assembling all standalone pieces. We think the first beta version will be available in about 3 months.<\/p>\n

During the next weeks, we planned to come up with some more articles, to specify certain issues and the way we addressed them in a new version.<\/p>\n

Hope for your interest and participation in the discussion.<\/p>\n\n\n