Create a plan and designs for a user-friendly lists system

[teolemon]

What

• Create a plan and designs for a user-friendly lists system
  • Examine if/what we can reuse from the previous system
  • Agree on the data structure (potentially including a non-used quantity field to make it future proof)
  • Create a product page widget to list which lists the product belongs to
    • 
  • Create a "Add/Remove from list" widget and use it in a modal that can be invoked from the product page
    • 
  • Create a "Create List" widget and use it in a modal that can be invoked from the "Add/Remove from list" modal and from the main Lists view
    • 
  • Create a "list of existing lists" view
    • 
  • Create a layout to handle lists
    • 
    • 
  • Create a layout to handle empty lists
    • 
  • Create a layout to list (and act on) products present in a list
    • 
    • 
    • 

Part of

• 🎯 What can I work on ? #525

Early mockups for discussion

Mockups on Figma

[teolemon]

@monsieurtanuki @stephanegigandet @g123k @M123-dev after several UX iterations, here's the plan for lists.

[monsieurtanuki]

@teolemon My main concern is that one: where do you go to the "All the Lists" page from?

Other more minor comments:

1. Side-effect - I suggest an "Add to a list" button when the product does not belong to any user list
2. When you say "Shopping lists" or "Kitchen", we're talking about lists that the user created and named that way, right? Those are not list subtypes, right?
3. Your list buttons have different colors in your mock-ups - where do those colors come from?
4. There are 3 list types: "app history" (history and scan history), "search" ("keyword search", "category search") and to-be-created "user" (unlimited number of user-defined lists), right?
5. Your "import" and "export" icons are both wrong - besides, I would add a "clear" button, and I would put those actions at the "list" level, not at the "listS" level (actually in the "list" page I can already see those actions)
6. Agreed that from a database point of view, a list of products is an ordered list of barcodes, and in option data attached to some barcodes (for the moment no data, but perhaps one day quantity, perhaps one day best before date)

[M123-dev]

Just out of curiosity and not to start a big discussion about if, if so probably better in a own dedicated issue but what db are we going for, back to a SQLLite solution or are we sticking with hive for the lists?
@monsieurtanuki @teolemon

[monsieurtanuki]

@M123-dev There's no obvious reason to go back to SQFlite because of lists. Lists only contain barcodes. Products are bigger: if we had to move back to SQFlite it would probably be because of products. Unless users get very fond of lists. The reward for success! Let's stick to hive for the moment.

[g123k]

@M123-dev There's no obvious reason to go back to SQFlite because of lists. Lists only contain barcodes. Products are bigger: if we had to move back to SQFlite it would probably be because of products. Unless users get very fond of lists. The reward for success! Let's stick to hive for the moment.

+1
Also if Hive is too limited, the creator of the library has created a new one with extended query features: https://github.com/isar/isar

[teolemon]

@M123-dev related to the Delete Button on History
https://user-images.githubusercontent.com/1689815/163598606-0c465dc6-e322-42f2-974c-34418b98c78c.png

[monsieurtanuki]

@teolemon Still this question: from where should we get to the "list of existing lists" page?
In the meanwhile, working on the "export/import" feature.

[teolemon]

Fixed 👍