I've seen a lot of variations of this, and i myself would love an open-source personal/project management system, but they all ignore just how crucial UX is in one way or another. They either make it so simplistic that you may as well just be using an actual text editor, or they make it so complex with assumptions that everyone cares about things like recurrence and goal tracking. Not hating on this project at all, but i've used about every single system out there that's been built, if often only to compare, critique, and work out how i should build such a system.
There are currently only two absolute truths to what i feel is necessary to combine power and ease of use, and honestly i think i learned that from git more than any todo list, or habit builder, or project management app, but it applies very well to the things that an intelligent personal/project management system needs to be powerful and accessible.
1. The source of truth should be an append only log of events, in this way state can be infinitely rebuilt and reused. That said, rewriting history could be an allowable function, such as the way a distributed git branch COULD be rewritten, but is generally avoided and requires serious intent to do so. I once considered (and built) a file-system driven personal management system, but too much valuable data is lost when your source of truth is the current state rather than the 'story'.
2. The UX needs to be both simple & powerful, with graceful complexity. As a simple example, allowing the ability to tag todos is a good idea, but you shouldn't have a tag sidebar taking up real estate if none (or even just a couple) of your todos are tagged. There should be a combination of enabling features and having the system be able to build a suggestive state based on the actions you take in the app in an attempt to delight users and give them what they would presumably expect given the path they've chosen. Think of the user experience as a Choose Your Own Adventure novel, where the choices they make progressively shape it.
That said, i humbly admit that aside from a successful career making other people money, i haven't yet built a successful product of my own, so take that opinion/advice with a grain of salt. I applaud your efforts and i hope one day the world has a great piece of software that makes it delightful to get shit done. If anyone is passionate about making that software, i'd love to talk to you, as i recently left my position as a software architect and have been doing my damnedest to avoid working for another shitty S-Corp that claims to have an altruistic vision while consistently putting profit over people.
(As an aside, i do realize that git does not really use an append-only log, in the way that databases and message brokers do, but it is very similar, and in many other ways is much more robust. The point isn't so much that the record of what happened should be absolutely immutable -- especially if one has their heart set on rewriting history --, but to keep the 'story' intact so that you can build a meaningful application state that improves over time.)
(As a last aside, i realize in English, the word 'i' is traditionally capitalized, i won't go into why i refuse to capitalize it, though i am open to discussing it, but i just wanted to point out that it's intentional, not a grammatical error. Throughout my professional life i've refused to capitalize and it hasn't hurt my career.)
I've released just a couple of days ago my own FOSS project for data management. It's called [Anita](https://anita-app.com), which is an acronym for Any(i) Type of datA
It's still in very early beta, you could consider it a very very essential MVP. I'd be interested to know your opinion!
I see the problem as being one some History professors refer to when they remind students to consider that life is remembered backwards but it is lived forwards. A good tool would have the flexibility to adjust previously defined activities dynamically as events unfold. Yes, last week I blocked Tuesday afternoon to writeup a test plan but the phone rang and things changed and that single activity 4 hour block ends up being completed in 5 chunks over three days. The UX should be easy to break that work plan up but it isn't and I certainly don't want 5 tasks for this little thing anyway. Likewise, as a result the journaling of that time as it actually happened is lost along with the ability to gain useful metrics except at a less granular level.
Also, for what its worth I'm not sure about the 'i' thing or why u felt the need for a throwaway in this case, but it would be interesting to hear what tools you do use after trial and error.
Hehe, fair. It was late and my first time commenting on HN and for some reason felt it necessary to point out that my grammatical incorrectness is intentional, not based on ignorance. In retrospect, i see that was unnecessary.
I currently use Notepad++ for programming related todos/notes with a file/tab per project, partly because i'm always at a PC, so it's quick and convenient, no extra clicks, the active/undone stuff stays at the top, and i scroll down or search for historical references, split up by each date as a markdown header.
My personal todos, routines, lists, and the family's grocery shopping and the like are managed by my own app that works ok for our current needs, but not quite ready for MVP. Perhaps i'll post a ShowHN someday ;)
> I've seen a lot of variations of this, and i myself would love an open-source personal/project management system, but they all ignore just how crucial UX is in one way or another.
It's not so much that they ignore it, but that everyone has a different understanding on what is important and what is the goal. The major problem of this area is that all apps and systems are their own walled garden. They all play for themselves, with barely to none interaction with anyone else. There is a reason why hyperflexible ecosystems like Microsoft Office are so successful, because while they are also walled, the garden is so big and open that it's actually a park where everyone can build their own small garden, where everyone can interact which each other.
What we need is a solid backend, which is topped by a flexible frontend, so everyone can build their own individual optimized workspace-garden. But what we have so far is people reinventing the same patterns again and again in their preferred flavors.
8 comments
[ 3.2 ms ] story [ 27.4 ms ] threadThere are currently only two absolute truths to what i feel is necessary to combine power and ease of use, and honestly i think i learned that from git more than any todo list, or habit builder, or project management app, but it applies very well to the things that an intelligent personal/project management system needs to be powerful and accessible.
1. The source of truth should be an append only log of events, in this way state can be infinitely rebuilt and reused. That said, rewriting history could be an allowable function, such as the way a distributed git branch COULD be rewritten, but is generally avoided and requires serious intent to do so. I once considered (and built) a file-system driven personal management system, but too much valuable data is lost when your source of truth is the current state rather than the 'story'.
2. The UX needs to be both simple & powerful, with graceful complexity. As a simple example, allowing the ability to tag todos is a good idea, but you shouldn't have a tag sidebar taking up real estate if none (or even just a couple) of your todos are tagged. There should be a combination of enabling features and having the system be able to build a suggestive state based on the actions you take in the app in an attempt to delight users and give them what they would presumably expect given the path they've chosen. Think of the user experience as a Choose Your Own Adventure novel, where the choices they make progressively shape it.
That said, i humbly admit that aside from a successful career making other people money, i haven't yet built a successful product of my own, so take that opinion/advice with a grain of salt. I applaud your efforts and i hope one day the world has a great piece of software that makes it delightful to get shit done. If anyone is passionate about making that software, i'd love to talk to you, as i recently left my position as a software architect and have been doing my damnedest to avoid working for another shitty S-Corp that claims to have an altruistic vision while consistently putting profit over people.
(As an aside, i do realize that git does not really use an append-only log, in the way that databases and message brokers do, but it is very similar, and in many other ways is much more robust. The point isn't so much that the record of what happened should be absolutely immutable -- especially if one has their heart set on rewriting history --, but to keep the 'story' intact so that you can build a meaningful application state that improves over time.)
(As a last aside, i realize in English, the word 'i' is traditionally capitalized, i won't go into why i refuse to capitalize it, though i am open to discussing it, but i just wanted to point out that it's intentional, not a grammatical error. Throughout my professional life i've refused to capitalize and it hasn't hurt my career.)
It's still in very early beta, you could consider it a very very essential MVP. I'd be interested to know your opinion!
It's a web app, [anita-app.com](https://anita-app.com).
Also, for what its worth I'm not sure about the 'i' thing or why u felt the need for a throwaway in this case, but it would be interesting to hear what tools you do use after trial and error.
I currently use Notepad++ for programming related todos/notes with a file/tab per project, partly because i'm always at a PC, so it's quick and convenient, no extra clicks, the active/undone stuff stays at the top, and i scroll down or search for historical references, split up by each date as a markdown header.
My personal todos, routines, lists, and the family's grocery shopping and the like are managed by my own app that works ok for our current needs, but not quite ready for MVP. Perhaps i'll post a ShowHN someday ;)
It's not so much that they ignore it, but that everyone has a different understanding on what is important and what is the goal. The major problem of this area is that all apps and systems are their own walled garden. They all play for themselves, with barely to none interaction with anyone else. There is a reason why hyperflexible ecosystems like Microsoft Office are so successful, because while they are also walled, the garden is so big and open that it's actually a park where everyone can build their own small garden, where everyone can interact which each other.
What we need is a solid backend, which is topped by a flexible frontend, so everyone can build their own individual optimized workspace-garden. But what we have so far is people reinventing the same patterns again and again in their preferred flavors.