-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "create new tag" when tag search for not found #221
Comments
@SimonLab thank you for opening this issue to capture the In the
Longer-term we want to think about all of our UX from first principals to build the simplest most intuitive "No-UI". e.g: a Terminal / CLI App would allow someone to write: dwyl "buy bread from @bakery 12:00 #food" That would create a shopping
But ... for the immediate UI/UX in the As for a set of |
Isn't it what we had before #209 ?: I might need more clarity on the UI to make sure I'm not going to build something unwanted, at the moment I'm not sure what should the end result for the tags feature on the MVP be. Are you thinking of something similar to: I think having the "create tag" feature in the dropdown makes the UI less busy than having another input for creating tags. Or do you have something completely different in mind for the UI? Sorry I'm not sure what you mean with
I like the simplicity of this. I'm not sure if there is a specific issue for this (I'll have a look), we might need to think how to manage duplicates, typos or long list of tags. This might make the item's text bloated. But we can talk/test this later on |
With the introduction of the new-tag-ux-fail.movEven if we have to revert back to the "old" manual entry of comma-separated tags 🔙 |
Create a tag from the select input Feel free to discard this commit/PR see: #221
Seriously, count how many steps there are to create your first dwyl-mvp-first-time-use-3G-throttle.movSteps to Create First
|
I think it's pretty obvious this UI wont work. It's clunky and laborious (and probably unfinished as yet). Even for an MVP, this isn't a testable feature because it's obviously not going to function in an actual app that users enjoy using. I also understand that it's difficult to think through UI without modals because they are everywhere and have the advantage of allowing a user to feel like they can do a little aside task without abandoning the task at hand. I think you were right when you said this above @SimonLab, it's not like you didn't know and ask for help in advance!
Right now the problem we have is that @nelsonic is having to do everything from code review to example code to design to product management, with a preemie newborn and toddler in the house, not much sleep and much less time. It's clear that we can't move forward with any feature without defining the UI, this is what we have to solve for. Thinking cap on |
@SimonLab thanks again for opening this issue to capture the UX of adding tags. 👍 |
On our standup call we looked at https://github.com/Choices-js/Choices |> https://choices-js.github.io/Choices Our first step is to remove the need to dwyl-mvp-cannot-edit-update-tags.movThis is definitely a UX regression. We used to be able to |
I've tried my best to simplify/specify the UI/UX of adding/removing tags in: This will inevitably feel like a "step back" in terms of functionality/features. LMK your thoughts on standup tomorrow. 🙏 |
So ... "Tag search" is not searching from a pre-defined list. Therefore I consider this issue to be a non-issue. 💭 |
@nelsonic On this last comment, are the tags case and space sensitive? Happy to open a new issue if you don't think this belongs here. |
@iteles agree; |
From #217 (comment)
One way to resolve this is to add a "create tag" link similar to the way Github is doing for labels
I think we can avoid having a modal and creates the tag directly by assigning a default colour to it.
Concerning creating default tags for new user, this might be useful, however it might depend on the context where the user uses the application, so I don't have a specific list of tags in mind yet that is general enough to be used by anyone.
The text was updated successfully, but these errors were encountered: