Awesome work @andrea_sdl! I like how the mechanics are simple.
1) There isn't a hierarchy of projects, tasks or subtasks... Everything is simply a project and you define your own granularity. That is an interesting design decision that I think I prefer but I can also see how it might be appealing to have some level of categorization for stats. What are your thoughts?
2) There isn't a timeline. That reduces the complexity which is a great thing. If I have to spend 30m reporting my time per day then I probably wouldn't keep it up very long. So I'm not sure if it makes sense to introduce more features but one thing a timeline might give you is a better sense for the relationships between projects. For example, If I have a project for "Working Out" and I spend 45m doing that in the morning, how does that impact the rest of my day verses working out at night? I actually think this is doable without a timeline but it takes a bit of thought when setting up your projects. Maybe you have 2 projects "Morning Workout" and "Night Workout".
3) This is kind of an extension of #2 but are stats silo'ed meaning, is each project reported independently or do you try to draw correlations between projects? I'd love to be using Haptime for say 3-6 months to get a baseline, then start experimenting by introducing new projects and see how they impact my overall happiness.
4) What's the next big thing for Haptime?
@duilen Wow! Awesome questions here. I'll do my best to answer them all :)
1) Yes, I love keeping things as simple as possible. This is mostly because I do believe tools shouldn't add questions, but give answers.
Although it is really simple I plan on expanding it as long as I find a viable way to keep things this way (fast, easy, 1 tap).
Categorizations for stats could be a good way to see if there are areas where you want to understand your mood weaknesses.
You might be less motivated to work on Design instead of Development (as an example) and with categorization you will have this info too.
This is a nice proposal, and what sparked up in me is having some kind of "survey" where you 'tag' the projects to help the system understand more deeply what you do.
Nice!
2) Timeline is something I didn't considered, mostly because atm Haptime is a passive time tracker, which means that you get the best out of it if you track your time once per day at the end of the day and not incrementally.
To put a timeline it would require the user to input the data right away which is a burden I'd love to keep away from the user.
For now the workaround would be to have 2 projects as you say, but another option would probably be to use the same tagging system as before to differentiate through day times (morning, afternoon, night) not only in projects but also in tracked hours. This might take a bit longer to create mostly because I want to keep things as simple as possible :)
3) This is something I'm thinking about and it all revolves around getting deeper insights about correlations and user behaviour.
At the moment the algorithmn is simple and the stats are per project but I plan to expand it and this is a great example of what's important.
Questions like:
- Which project has dropped my mood?
- was I happy this week?
- why this week was worst?
should be answered by the system itself.
Haptime already answers these questions partly thanks to the weekly/monthly email, but there's room for improvement.
4) Thanks for asking!
I've got 3 things that will come out in the next weeks, but honestly I like to take inspiration from what the people really want and shaping it the easy way.
Anyway here's the list
- freshbooks integration
- a more detailed project report
- Project working estimates (to compare how much I thought it would take with how much it really took)
Thanks again Dane for these great questions!
@andrea_sdl very nice!
What do you think about an IFTTT or other similar integration? That could be a good way to automatically add interesting meta data to your projects.
Use cases:
1) Someone could connect their github repo to a project to add the number of commits in a given day to a project.
2) Get Fitbit data added to your workout.
@duilen yup! IFTTT is the way to go.
I plan to integrate with it as soon as I've got a full functioning api, but didn't look too much into it for now.
Also, both are great use cases, I'll keep those in mind ;)
wow, excited to see my app featured in producthunt, thanks @dskaletsky !!!
I built this because me and my friends were frustrated of how troublesome time tracking can be.
We wanted to have a time tracker that didn't require too much attention (or timers to start) and could help us understand our happiness.
I'm here to clear up any questions ;)
Wyndy
The Daily Subset
Haptime
The Daily Subset
Haptime
Haptime