Allow user to add notes to habits #56
-
Currently, habits have titles and questions for the reminders. It would be nice to have a general "notes" field to allow the user to store whatever other information they would like about the habit, such as the reasons. These notes would be optional, and displayed only on the top of the statistics page. |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 4 replies
-
I think it would be also nice to additionally store an annotation for each specific occurrence of the habit (with the default, of course, being no annotation). This way you could say: "Yes, I've jogged!" "... but for some minutes less than my target is, because I was interrupted", or, for instance, I'm thinking of the way glucose meters that diabetics use work, which allow you to mark each reading with a "pre-prandial", "post-prandial" or "see diary for notes" icon. As to the UI side of this, I use short taps for ticking, so in my use case, it would be natural for long tap to cause the annotation requester to show up. Not sure how to deal with it when long tap is the default. |
Beta Was this translation helpful? Give feedback.
-
I second that idea for the following reason: Sometimes, there are things that you are quit "proud of" after finishing. This could be "first 5 miles run", "cracked the 150lbs mark" or, in my case, "finished book XYZ". It would be a great psychological benefit to not only see that you continued your struggle, but that you had a specific success at a specific day. I hate seeing those things as a set-in-stone pre-defined mile-stone that you either reach or fail to reach and would rather keep this flexibel like an "annotation" to your usual habit-development. |
Beta Was this translation helpful? Give feedback.
-
Why not just make the questions field a more general notes field and add markdown support? |
Beta Was this translation helpful? Give feedback.
-
I don't see this as hard to implement, and would make it a program I could recommend to others. |
Beta Was this translation helpful? Give feedback.
-
@iSoron I am interested in implementing this feature as you have described it (i.e.: an optional "notes" field) as a way for me to familiarize myself with the app's code. Feel free to assign it to me and I'll work on it this week. |
Beta Was this translation helpful? Give feedback.
-
I wholeheartedly support LuccoJ's request. In fact, at this point the I feel this is the only advantage that Habit Bull has over Loop Habits. Thanks! -Adrian
|
Beta Was this translation helpful? Give feedback.
-
@iSoron. Thinking this one through.... Honestly I think this could be marked as closed. Right now the "question" field is only known as question as the hint in the xml, and the default values you present are in question form. Other than that... it's referred to as "description" in the rest of the code, including the sql column. I think you could make it even more generic by simply:
And that's it. Like I said, it is pretty much already a notes/description. |
Beta Was this translation helpful? Give feedback.
-
@recheej I think we should create a new "question" field in the database, move the current description there, then add some interface elements to allow the user to see/edit the actual description. Having one field to store two different pieces of information (question+notes) is a bit confusing, and may restrict our options in the future (for example, if we want to present the question in some other way). |
Beta Was this translation helpful? Give feedback.
-
This feature has been implemented and will become available in Loop 2.0. |
Beta Was this translation helpful? Give feedback.
-
May I add something to this issue? I'm super unsure, how much effort it will be to support this notes field to be in Markdown. (like habitica is allowing it in notes in tasks). The editor itself does not do any Markdown Syntax Highlighting during editing mode. It could be difficult to render e.g. bullet lists without breaking the UI or design of Loop. I'm just typing my thoughts here. What do you think? |
Beta Was this translation helpful? Give feedback.
This feature has been implemented and will become available in Loop 2.0.