EPIC: Lists
Following on from our discussion in https://github.com/dwyl/app/issues/233#issuecomment-553147210, it's my experience that the majority of the apps in this category that are easy/successful to stay ontop of offer some type of list/project.
As mentioned in https://github.com/dwyl/app/issues/233#issuecomment-552978386, this would be in addition to tags which are used for context across lists.
To be discussed in this issue:
- Expectations of usage of lists
- Display in app layout
- Including sorting/filtering
- UX for easy management of these lists
- Proposed public lists suggested by application
- Public vs private lists
I'll type out my thoughts on these in the comments rather than 'pollute' this OP.
As noted in #283, the ability to create separate lists of items 📝
is a high priority for making the App useful. 👍
Once we have lists it will make sharing/colab a lot easier. 🫂
We need to draft wireframes for how to interact with lists.
@iteles do you want to pick this up and do a paper (or Figma) sketch?
or should I try and outline something basic?
In the first instance all items will be added to list.name = "personal"
this will be transparent to the person using the App (MVP),
i.e. they don't even know that the concept of lists exists; we don't surface it in the interface.
Once they have created a few items we can figure out how to manage lists ... 💭
@iteles do you have time (T25m) to (paper) sketch the interface for interacting with lists? ✍️
(it would be a huge help to have a starting point for how you would expect this work ... 🙏)