Lightweight Shopping List (Grid, Reusable Items)

[iCaotix]

First Check

• I used the GitHub search to find a similar requests and didn't find it.
• Checked the tasks tagged issues and verified my feature is not covered

Please provide a concise description of the problem that would be addressed by this feature.

I recently started using Mealie as my main recipe storage. I still use other apps for shopping lists because of two main reasons: The reusability and something I would call "parse time".

The thing the other app I use is doing different is the following:

• The layout is a grid with pictograms above the items which match (on a best effort basis) the piece I want to buy (parse time)
• If I tick off an item it goes to a "recents" section from where I can add it again to the list by another click. (reusability)
• Often times ingredients are not bought in the exact amount they are required by the recipe or not everything is fully planned for a week. So most of the time shopping is done "by piece" instead of "by weight" or whatever the recipe needs. e.g. if a plan a breakfast for my friends I don't need 200g of jam but just a jar no matter how big.
• If I need a specific amount I would write that into a separate field below the item I want to buy (currently this would also be possible by mealie if I include it in the note but this would create separate entries for "1 milk" "2 milk", etc.)

Please provide a concise description of the feature that would resolve your issue.

The idea comes from my SO who refuses to use the app because "Adding stuff to the list is so tedious"
As an impression on how this feature would look like I provide two screenshots from other apps which kinda have this functionality. And I personally also want to get rid of the multiple apps.

Kitchen Owl (https://github.com/TomBursch/kitchenowl)	Bring (https://www.getbring.com/en/home)

Note: unfortunately I couldn't find screenshots with english text but they idea should become clear anyways.

Please consider and list out some caveats or tradeoffs made in your design decision

My idea would be to leave the existing lists as they are but since we anyway can have multiple lists we just add a "type" to it like "Simple" and "Standard". Then the behavior differs that such a list may not support adding to it via the recipe page or any other automatic actions. Still the categories and the ordering for how stuff is ordered is still nice to have.

What would also cool would be to have a simple API endpoint for something like a Voice Assistant (Like Alexa or Google Home) to add a thing to the list by just calling it out: "Add butter to the shopping list". Or any other integration one could built themselves.

Additional Information

• If this is accepted I'm willing to submit a PR to provide this feature
• If this is accepted I'm willing to help maintain this feature
• I'm willing to sponsor/pay a developer to do this work

[djlombar89]

While I love the app and use the shopping list extensively, the UI needs a revamp. My wife describes it as "designed by an engineer." As a fellow developer, I get it.