Meeting Minutes

Feb. 9, 2023

Major points from meeting
- Initial UI mockups and storyboards should not be very professional (keep it simple and straightforward)
- Stay committed to assigned tasks; try not to exchange tasks
- Use Firestore as our database
- If there are questions on technical requirements, bring it up with the TA
- If there are questions on super specific details, bring it up with the professor (use forums)
- Make sure to review each other's code
- Create pull requests when trying to merge branches to main/master
- For pinpointing locations, we can register with google using a student account to get $500 in credit to use their service
- Look into RISK Levels (expected importance of a task) and Story Points (expected duration of a task)
Libraries we can use:
- GLIDE for image handling
- LOTTIE for animation
- MATERIAL DESIGN for UI
- ZXING / GOOGLE for camera scanning
To do for this week:
- Finalize on user stories
- Delegate tasks
- Do not implement anything until next meeting
- Start thinking of a UI and how to implement it
- Start asking questions like "do we need a database for this?"

We should have 1-2 people start working on UI (Jvon & Abrar)
- UI is very important and easier to deal with
We should create a skeleton outline of features before implementing them with code
- Create basic screens for everything we want to do (should be able to navigate between them)
- Plan and Sketch UI
- Create all the classes (they can be empty for now)
GIT setup
- Set up branches
  - Each member should have their own branch
  - After that, there should be a stage/staging branch used for testing/intermediate code, etc.
  - After that, there should be a master branch used for final deployment of features
Task delegation (with respect to requirements, issues, and user stories):
- 2 people working on map-related tasks (map UI & integration, geolocation, etc.) -> Carl & Jaskirat
- 3 people working on QR codes and profile-related tasks (database stuff, code hashing/scoring, profile UI, etc.) -> Jvon, Abrar, & Yuri
- 1 person working on camera/scanner tasks (camera/scanner UI & integration, etc.) -> Daniel

N/A

For project part 3 deliverables, follow instructions closely
Double check if we can follow through with our half-way point project requirements

TA mentioned we could potentially use a Singleton data class as a centralized sink of data instead of the user class that we previously implemented
We need to send a short video to the TA that demos what we have completed thus far (for feedback)
- People who worked on a specific section should speak about that section in the video

We have a 7-minute window to demo to the prof (1 min for setup, 4 min presentation, 1-2 mins for questions)
- Do not need to demo Firebase to the prof
- Demo with prof will be in person/live
- Need to make sure there's no crashes with the final demo
We should finish user stories first and then worry about UI after
- Having a dedicated UI person right now is okay, but leaving UI until end is recommended
- We need a polished UI for the final submission
We should let the TA know beforehand if we want to meet in person for anything

Presentation will be on April 5th or 6th during a lab session
Demo itself will be 4 minutes, in person
- We will be stopped if we go above time
Do everything and practice beforehand
- We should set up our laptop for the presentation beforehand
- Have a video/screen shots ready before hand as a backup
If we use real devices, we should have a tool to mirror the phone (so people can see it on a projector)
Suggestion from TA: Focus on the app as a product (like we are selling it) instead of a list of user stories
- Form it like a story

For the demo, we need to start with a general overview of the app (~30 seconds)
- Note that the prof is very strict with the time
Have everything ready before the presentation
Don't have to show every single detail (e.g. don't show the process of adding comments, just show that there are comments)
Grab stuff off internet and reference it if we do not have time to implement stuff ourselves