Team Meeting 11 Nov 15

Team Meeting 11 - November 15, 2022

Attendees

• Areeba
• Casper
• Charlotte
• Duc
• Mark
• Purna

Standup Progress/Updates, Difficulties

• Areeba
  • Meal Plan implementation and visuals
  • Working on pulling recipes/ingredients from database to add to a meal plan
• Charlotte
  • Unit tests for MealPlan and DailyPlan
  • Intent tests
    • Issue with missing folder for Intent tests
• Duc
  • Changed UI/UX of app; no blockers
• Purna
  • Working on StorageActivity into Fragment
  • Issue w/Android Studio, running indiv activities/etc
• Mark
  • Finished edit recipe ability
  • Working on add ingredients to recipe (visually!) and add/changing recipe image ability
• Casper
  • Changed to fragment
  • Changed UI to accom new UI/UX changes
  • Some blockers: asking TA for branch management (i.e., addressing specific issue in branch)
    • Found out 1 module/branch is an industry standard, not requirement Other grp: intent test for recipe nav/ingr, layouts for MPs, started shplist e.g. viewsd, lists (blocker)

During meeting

• Pause unit/intent testing to finish all user stories
• Ensure you have your own SnackNTrack account when testing DB
• Branch convention: People can have their own branch per issue, then merge into module branch (e.g. issues/1 and issues/2 merge into recipe) then merge the module branch into develop
• Possible problem statement: Reduce food waste; climate change
• Discussion clarifying MealPlan design
  • Including on how to use existing RecipeListAdapter and StorageAdapter in MealPlan fragment/activity, including the "Add Recipe" and "Add Ingredient" fragments/etc
  • Deleting functionality: deleting Ingredient/Recipe from meal plan would delete only from MP database, not from Storage or RecipeList
  • We can add non-added ingredients/recipes to a meal plan, then add respectively to storage/recipe list
• Javadoc tag convention: just use @author, @param, @return, @c
• Demo to TA for half-way checkpoint (see more below)

Test demo feedback from TA

• only one person spoke
• 50% of app only complete, excluding database integration
  • considering 45% only complete
  • e.g., add ingredients/recipes do not add properly to database, MealPlan and ShoppingList not visible to user
  • To TA, 50% functionality should mean ingredients and recipe is fully finished, or that we partially implemented all 4 options; AND firestore should've been 50% implemented (firebase = base)
• 4 mins only out of 6 mins
• "awful"
• when presenting app, (like apple keynotes), they do not go through an outline, i.e. do not put that
• get client interested and their attention, TA was bored
  • start with huge statements
    • e.g. "Have you had a problem tracking your groceries and recipes in separate apps? We have a solution!"
  • slides aren't required (maybe about the problem statement)
• repetitive
  • do not state the features, then demo it--do it at the same time
• 1 person is presenting, another person is demoing on an emulator

Half-way checkpoint feedback from TA

Note: our mentor TA only marked some aspects of our project

UI

• Start from sign-in activity for each mockup (i.e. start from main activity)
• Add activity/fragment number for reference (e.g. show that after adding ingredient, it goes back to list activity)
• Include swipe, long-press options for delete
• Have more descriptive labels (e.g. "press (+) add button to add ingredient")
  • Assume client is dumb

Tools/Other

• For meeting mins/standup, include what you were assigned and what we have done
• Integration issue: as demonstrated in our demo, we are integrating enough, e.g. some have coded ShoppingList, MealPlan but have not been implemented in app demo

Todos

Get as much done for next lab meet! 12 days left :O

• Areeba
  • Finish meal plan
• Casper
  • Sorting recipes in RecipeList
• Charlotte
  • ShoppingList
• Duc
  • Authentication
• Mark
  • Images, ingredients for recipe
• Purna
  • Fixed UI Wiki and Figma files