Would be nice to import and export ingredients separate from dogs data. This way you might easily load and unload barf shops data. This may also solve the issue of content localization. Ingredients should not be translated inside of the app. But you might load data from your preferred shop in your preferred language.

There is the idea of having a stash that knows which ingredients you have at home, together with a automatic meals plan based on whats available.

Not sure whether or not this is really helpful.

Therefore we need one columns element per content in one column, which forces the MealsWeekDay to split into 4 components that can be used separately in 4 columns per day.

Currently this makes the navbar tabs ugly - color is broken and also the horizontal alignment of icons and nav label.

Currently only the creation of the first dog is covered.

When entering edit mode for a weekday in meals page for a day that has allocated meat and stomach the below ingredients list should list under all only those ingredients. Next to all only the allocated categories are displayed in the panel tabs.

This behaviour should be activatable via settings - by default it is active

This way is has a consistent size.

Make the pagination optional through settings.

In settings there should be the possibility to enable automatic rounding of all amounts by used defined number. Defaults: enabled & 25.

This setting should apply to all amounts:

• category amounts per week & day
• meals
• stash

Currently you can add one category, e.g. meat twice to one day. This might result in strange behaviour. Needs investigation and proper solution.

Approaches:

• Do not allow used categories in options.
• Automatically merge them on commit.

Sometimes the app needs to ask questions - e.g. after an upgrade the user needs to be notified about what happend - maybe additional decisions need to be made. Although this can be used in the meals history to ask whether or not something took place and it is also a good place to create a getting started introduction into the app itself.

It needs to be decided if this should be a seperate page or something included in the main template.

There should not be a clear local data link and it should not warn regarding data loss - instead link to the issue tracker in case someone encounters bugs.

They are already stored in the localStorage. Should be easy to make them customizable in the settings. Maybe with some predefined color packs?

It includes some new features and has a slightly changed API - to minimize the overall bundle size I'll should give the explicit approach a shot - looks quite nice.

If the base value is e.g. 109, browser increase switches to 125 and button to 134.

Suggestions: Remove the buttons, or change their behaviour respectively.

On hold, until rounding feature has arrived.

In case of upgrades the state data of barf might change. Provide a nice way to detect those changes and apply them to already present data in localStore.

There is already the version number present in the state.

Need something like migrations from version to another

Need to dig into sauce labs. Travis CI docs on the topic

This framework looks promising. Should try to integrate it.

Currently the wizard decides a lot of things based on randomness.
It would be more useable, when you can specify more parameters, like:

• portion size (per subcategory?)
• amount of allocations per subcategory

Sane default values for fields should be automatically generated and provided.
Maybe some of the settings are hidden, but can easily be accessed.

HI!
I'm courious about the status of that platform!
Looks cool but seems untouched in the last year, is there any plan to continue his development?

Thanks for the answer,

Mario

Currently there are addivites in the defaultStore - but they are nowhere in user interface. They should be represented in plan mode and also be available in meals and ingredient creation form.

When you add a new category to a day in plan view, the amout is always 100 and the first not used category is picked - would be nice, of it relies on still missing things for the week instead.

Based on the available ingredients it should be possible to create a meals plan for a day or even the whole week automatically. Somehow like the wizard in plan page.

When in Ingredients page, you can open an ingredient, but nothing shows up.

You can decide whether or not you'll want the meals plan to be recorded. There is an additional page which allows you to edit if when you did not follow your meals for whatever reasons.

Maybe use vis.js timeline or bulma timeline extension.

Use case: You made a plan, already finished - manually setting up many allocation.

Now you decide, that your dog is more active, or should have a higher weight. If you adjust it, the allocations do no longer fit and need new manual adjustments.

The user might now use the wizard to reallocate, but if the own configuration is not wizard based this does not make much sense.

There should not be more than one tab open at once for this case.

Already tried to solve this but without success - maybe chartjs provides some mechanisms to solved this with something else than responsiveness and/or width, height.

Currently the menu stays open, after one clicks on a menu item - this should change.

The store should be covered with tests completely.

Ideas:

• Automatically select light or dark based on category color.
• Make it selectable, too...

The underlying data should stay in gram as it is easier to calculate with.

This is not nice... :)