DietLAH! is a diet tracking app that is meant to allow users to easily track and maintain their meals so that they are able to maintain their ideal weight and body shape.
While the app has a GUI, inputs and feedback are primarily given via a command-line interface. This allows users to work on the app quickly and efficiently as they get used to the inputs.
The app currently consists of three main components:
FoodIntakes can take on duplicate entries for practical reasons. For example, when a user has the same meal two times in the day, they should be allowed to enter the same food intake with the same name without problem.
However, the current implementation may lead to difficulties when the user wishes to delete a food intake or update the food intake, since there are multiple food intakes with the same name.
Multiple similar food items can be added in a day and it is reflected as individual items in the food intake list repetitively. Should we aggregate them as a unique item identified by a multiplier at the back?
There might be some inaccuracies in the calculation of macronutrients for the diet plan. We will need to re-look at the formulas and make sure they are accurate.
... track your meals so that you will be able to maintain their ideal body weight. The use of "their" is incorrect unless the product is providing user with an ideal weight, but I don't see that functionality.
After keying plan_recommend, scrolling down in UG said that we can plan_set p/1 but does not give the "Balanced Plan" as indexed from page before plan_set p/1 command was used.
after plan_set p/1 (expected to set plan as balanced plan)
Recommended course of action: change functionality in plan_set to take in any plans that are on current view list or state that ID can only be seen and chosen from after plan_list
Currently, some of the recording is being duplicated for FoodList and FoodIntakeList. Let us try to refactor and clean this up a bit to remove confusion.
"When you first launch DietLAH!, you will be prompted to enter your particulars." did not happen. Tried to key in bmi g/M a/43 h/170 w/70 i/80 straight but was met with error.