Replies: 2 comments 6 replies
-
|
I ran into this, too, a few times, when adding subtasks in the extended edit view, for example. |
Beta Was this translation helpful? Give feedback.
-
|
I am thinking about a bigger change here, I am thinking to merge the detail and edit view of one entry. To make the entry point for a new journal/note/task always the quick add functionality, the new combined view&edit screen would then always save any changes immediately. As this would solve the problem out of this discussion, I wanted to ask what you think about it? |
Beta Was this translation helpful? Give feedback.
-
|
So basically the Quick Add would then create the new record (with title, description and categories), and after that everything else would be saved whenever I leave any field, so there wouldn't be any need for a save button at all anymore? So in the Overview the Floating Action button would open the Quick Add popup, and Save & Edit would go to the Details screen. That would solve this issue, and part of me likes the idea because it makes the UX much more consistent. The differences between the Edit and View screens have confused me a couple of times, as the View screen actually allows some editing, for example adding notes and said subtasks. On the other hand, I very much like the fact that I can see the whole task on one scrollable screen and mark subtasks as done. While I can do that in the Tasks Overview even for the first level of subtasks, for nested subtasks I think I'd sorely miss that list on the main page. I'm pretty torn to be honest. Maybe remove the Add a Subtask line from the View screen to make the distinction more obvious? It would still solve the issue because the Edit screen would never be in "New" (i.e. record doesn't exist) state... A small observation: the Quick Add button's tooltip says Quick ToDo where it should say Quick Task. I don't want to make this a separate issue because we're discussing the whole functionality here anyway... |
Beta Was this translation helpful? Give feedback.
-
No please keep that, it is super useful for me to quickly add subtasks without going into the deep edit activity and switch to the subtasks tab... |
Beta Was this translation helpful? Give feedback.
-
|
I fully agree that it's useful to add subtasks from the View screen's subtasks list. But it makes the UI more complex and less intuitive, raising the learning curve for all users. And making matters worse, it affects maintainability too - feature changes always have to be made in multiple places instead of just once. From a developer's point of view, that translates to higher support volume and higher development cost/effort, which is bad for the app and thus bad for the users. That's why I think removing the View screen is a good idea, even if personally I'd like to keep the subtasks list on it, as well as the summary view it provides. It will be controversial with existing users, but I've seen devs throw in the towel on best-in-kind apps for exactly this reason - too many features, too much complexity, too much support volume. And the better jtx becomes, the more users it will get, and the higher the support volume will be anyway. If anything has top priority on my wishlist for jtx, it's avoiding that. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your feedback! :-) |
Beta Was this translation helpful? Give feedback.
-
|
agree that currently too easy to lose an entry. Both @kleinarne and @devvv4ever have good points. Really not sure what the way to go is Really good UI is hard to figure out, especially balancing new user, power user, and maintainability. And on mobile... Maybe some mockups to look at would help? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I will provide some drafts when it's ready, but it will take some time... I'll also be on vacation soon ;-) |
Beta Was this translation helpful? Give feedback.
-
When I navigate back on a task (presumably journal or note too), I lose any unsaved changes without warning.
Especially when working with lists of subtasks or extensive descriptions, this can mean losing a lot of data with one wring tap.
A warning about discarding unsaved changes would help prevent that.
Beta Was this translation helpful? Give feedback.
All reactions