IDEA: Routines Page

[angelsix]

From #10 it seems it may be beneficial or useful to have Routines in the program, to allow users to automate other pages for entries like food, exercise and insulin so that they do not have to manually enter the data.

A routine could be to add oaks for breakfast at 10am every morning, without the user needing to do that. They could feely delete the entry on days it was different but then for most days, the data is entered for them and its less to manage.

Thoughts?

[DicksHalfwayInn]

I think that routines would be a good idea. Routines could be made for:

• Exercise
• Food Intake
• Insulin Intake
• Weight reading input There should be a pop-up though at the time the routine event fires, so the user can acknowledge that the routine was followed. The pop-up would not only be used to acknowledge the event but also act as a reminder.

[DicksHalfwayInn]

For food routines, I would add a page for commonly eaten foods. You could even take a picture of the food and attach that to the fooditemviewmodel :)

People are creatures of habit... we basically eat the same food over and over. If we can have an inventory of commonly eaten foods, then the user can click on the food (or a picture of the food) and then enter a portion size.

For example: Username: Dick Dick's Regularly Eaten Food List:

• Dick loves spaghetti. Dick makes a big batch of spaghetti sauce once every couple of months and divides it into bags and freezes it. Once a week, Dick defrosts some spaghetti sauce, cooks some noodles, buys a bag of Caesar salad and cooks some garlic toast. Dick normally eats one bowl of spaghetti sauce and noodles, one bowl of salad and 2 pieces of garlic toast. Sometimes, though, Dick is extra hungry and eats another half bowl of spaghetti and noodles, and eats 3 pieces of garlic toast. Other times, he might not be quite as hungry and not even cook the garlic bread.

Here is an opportunity for the user to add a commonly eaten food to their personal inventory. When they first start using the app, and they add spaghetti dinner to the inventory of foods eaten, they could be prompted to add this food to their "commonly eaten" list. If they choose to, then you can take a picture of the food and we create a foodviewmodel. FoodViewModel could include:

• Name for the commonly eaten meal, in this case... Spaghetti, salad and toast
• Picture of the meal
• Quantity of Carbs in a normal serving? (this would be personalized to Dick's normal serving size)
• Quantity of Protein....
• Quantity of Sodium...
• etc.

the second time that Dick eats spaghetti, he only has to go to his personal food inventory and click on the picture and then adjust the serving size to reflect what he ate compared to what he normally eats. (1.3 spaghetti units if he ate too much, or .8 spaghetti units if he ate a little less than normal)

this brings up another point, quite often if I eat spaghetti for dinner, I will have it in my lunch the next day, so it would be easy to bring it up again and use a smaller serving size for lunch food intake...

other examples of commonly eaten foods in a household might be:

• Roast beef/pork/chicken and gravy, potatoes, veggies, Yorkshire puddings and desert.
• egg mcmuffins and a hashbrown with coffee
• Taco night
• Chicken fajitas

there are many, but I think that amongst one individual or a family, they repeat the same foods over and over...

I know that when I go to a restaurant that I frequent often, I usually order one of only a few on the menu, I know what I like when I go to that restaurant, and usually, that is the reason I am going there in the first place, is because I really enjoy a certain meal(s) that they have on their menu.

The same can be done for exercise. The first time the user enters "Went for a walk with the girls" into their exercise page, they could be asked if they want to add it to their "Commonly performed exercise" list. (maybe add a picture of the girls)… then when they enter the same exercise event in the future, they can choose from the commonly performed exercise list and then enter an adjustment for something above or below their normal baseline.

For example: Jane walks with the girls 4 times a week (Monday to Friday, except on Thursdays because that is her daughters Judo night). When Jane does the normal walk, it is 3 km and the girls walk pretty fast. She figures it is 1 hour of pretty decent cardio (not sure how that is entered in the program), but if Frida joins the girls, then they walk a lot slower and cut it down to 1.5 km... Jane when entering the exercise in the app could still enter the same exercise event from her personal commonly performed exercise list, but could change the valuation from one unit to only .5 units (if that makes any sense at all)

This might be a little cumbersome for a user to understand, but I think, with time, they would understand how to enter things with relevance. They also have the benefit of seeing how the food or exercise affects their body too, so they would be able to correct a 'base unit level' if they felt it wasn't a good reflection of how their body reacts to the food or exercise, compared to other foods or exercises on their personal list.

There could even be a geo-locator tag to the location where the exercise normally occurs where the app would Pop-up with a notification when you get to the walking track, asking you if you are going to go for a walk, and would you like the app to remind you to enter the event after it is done.

I guess that this would also tie in to bringing in data from a personal exercise monitoring device or fitbit, for lack of a better word, this could be associated with the users personal regularly repeated exercise list

[Robert-git-hub]

Routines are great idea and it is also important to be able to identify automatically added routines by adding some distinctive sign or color if we don't ask for approval.

There should also be option for quick edit from the list of most popular entries.

Being able to take pictures of a meal if wanted is vital.