Journal

Week of 4/28/24: LWOC!

Client Meeting:

  • No meeting, LWOC

Coach Meeting:

  • No meeting, LWOC

Team Meeting (5/1):

  • Discussed when to meet next week to finalize project and video record the demo
  • Have final updates to project and updates to documentation polished up by end of this week
  • Worked on powerpoint slides for final presentation

Week of 4/21/24

Client Meeting:

  • Asked client if she wanted any additional changes prior to the demo, response was to update the brands shown within the mock rewards page, specifically Nike, Target, Chipotle
  • We are good to go in terms of demoing for the final project otherwise

Coach Meeting (4/24):

  • Discussed what client wants us to prioritize for the rest of the semester
  • Slight roadblock with game creation after implementing said changes
  • Plan for the rest of the semester: handoff plan updates, final changes to app, final project and handoff videos and assigning roles between the team

Team Meeting (4/24):

  • Discussed when to meet next week to finalize project and video record the demo
  • Have final updates to project and updates to documentation polished up by end of this week

Week of 4/14/24

Client Meeting (4/18):

  • Wilson met individually with client, showed client progress on the app
  • Discussed final stretch and priorities

Coach Meeting (4/17):

  • For the handoff plan, could write up a small summary of the actual plan rather than just steps for handing off to local machines, make installation steps more user friendly, update github link at bottom of administrator page
  • Gave updates on making progress with things discussed with client and rewards system should be finished by next week, also working on final video

Team Meeting (4/17):

  • General updates
  • Made progress on leaderboard stuff and stylistic changes, implemented countdown page for next question

Week of 4/7/24

Client Meeting (4/10):

  • N/A; Meeting cancelled

Coach Meeting (4/10):

  • Maybe add a FAQ to the app rather than documentation/user manual pdf, since nobody will read that
  • Shouldn’t be too hard to make a redeemed rewards page, just a collection for each user
  • However more concern is that the specific rewards should be more pleasing in terms of redemption value
  • Updates on documentation plan, tech talk (think about the story we’re trying to tell, focus on the demo and write good comments), and app progress

Team Meeting (4/10):

  • Discussed how to split up doing the handoff plan to be done by end of week
  • Finished tech talk, split up slides and practiced parts
  • Made a few more commits to rewards page

Week of 3/31/24

Client Meeting (4/1):

  • Showed client our current progress, including adding a dropdown menu for team selection, and making it so that corresponding logos render during team creation properly
  • Don’t need to focus too much on the rewards because it focuses a lot on backend, main focus should be to make the app look pretty and have a presentable, demo-able app
  • FanzPlay logo should be on every page, rewards page should include more rewards from sponsors of brands people our age like (Nike, Target, etc.)

Coach Meeting (4/3):

  • Gave updates about the progress we’ve been making on the frontend of the app
  • Discussed plans for switching priorities from rewards to admin/user interface focus
  • Reminder that the semester is ending soon, it’s not as far away as it seems

Team Meeting (4/1):

  • Discussed test plan deliverable and what to include given our current progress, also documentation plan for next week, split up the work and figure out how to manage our team’s time and meetings because we’ll also be busy with the tech talk
  • Will screen record a small demo from both the admin and user sides, and clip them together to show to client
  • Discussed what we were going to do for our web scraping tech talk, maybe build a small app as a demo, maybe use Spotify as a reference

Week of 3/24/24

Client Meeting (3/25):

  • Gave updates about logo and team selection progress
  • Need to see work being done, sooner than the week before we present so that any hiccups can be investigated and solved before the presentation
  • Important to give updates and write writeups for what we work on
  • Set up static meeting time of Mondays at 12:00PM for the rest of the semester

Coach Meeting (3/27):

Team Meeting (3/25):

  • Deciding to make decently sized improvements based on the current codebase, we don’t have too much time to work on larger improvements
  • Tech talk coming up, will spend time working on that
  • We have ideas for how to improve the app but will focus on frontend for now, (for example just adding logos one at a time) may not necessarily have to implement much backend
  • Everyone should play around with the app more to come up with ideas for small improvements
  • Idea to test and implement prettier/more accurate results bar graph after games finish
  • Complete APPLES Reflection 1

Week of 3/17/24

Client Meeting: N/A, didn’t happen

Coach Meeting (3/20):

  • Discussed updates on code and deliverables, and plan moving forward this week
  • Tip to not focus on tech talk over coding for the upcoming weeks

Team Meeting (3/20):

  • To do: APPLES Reflection 1

Week of 3/10/24

(No meetings because of Spring Break)

Week of 3/3/24

Client Meeting: N/A, didn’t happen

Coach Meeting (3/6):

  • Discussed looking at the rewards system and rewards page to familiarize ourselves with the code behind it and figure out how the team wants to update it
  • This week is a point where we should try to get some progress going, even 1 commit to build some momentum

Team Meeting (3/7):

  • Discussed what is able to be worked on in the upcoming week due to Spring Break
  • Worked on making the app scrollable, also making it such that logos for teams can be added in
  • Decided on topic for tech talks starting 3 weeks from now (web scraping, React)

Week of 2/25/24

Client Meeting (2/27):

  • Updated client on the contents of our midterm presentation and steps moving forward; similar to discussion from last week
  • Asked to regain Firebase invitations due to expiring invites and/or issues with Google account authentication

Coach Meeting (2/28):

  • Discussed our goals for what we’re trying to implement in the app with coach
  • Brought up the issue with only being able to test run on one computer (macOS) because it doesn’t open the app after successfully running the build in Windows
  • Coach tried to help us run through deleting node_modules folder from Franklin’s PC to fix issue of React Native not deploying; also generally might have more success running commands via wsl over powershell
  • Discussed plan for the rest of the week: Ethics Assignment, have some kind of blueprint ready by the start of Spring Break hopefully

Team Meeting (2/26):

  • Met up to do a practice run of midterm presentation, actual presentation was on Tuesday
  • Completed Ethics 1 assignment (update after coach meeting: add links to sources)

Week of 2/18/24

Client Meeting (2/23):

  • Demoed app using one admin phone and 2 user phones
  • Discussed implementing an algorithm to balance out the results bar graphs from the user side
  • Discussed potential sponsors using distance to winning school and also including sponsors other than national food brands
  • Rewards page showing the sponsors is the most important page for demoing/showing so it could use some animation and/or a more seamless transition to a “saved rewards” page; basically this is a big focus in the long run because it’s the moneymaker
  • Client wants to link a ticket purchasing/redeeming feature from the app but it’s down the road
  • Can adjust countdown timer length for shorter/longer questions or True/False questions

Coach Meeting (2/21):

  • Reviewed team website thus far
  • Suggestions to reformat requirements doc, could go back to rethink project platforms
  • Potentially improving the infrastructure (such as not having to input 16-character code or getting image URLs for team logos) would improve the frontend as well as UI changes
  • Plan to figure out what we’re going to do architecture diagram-wise and demo-wise for Zoom presentation

Team Meeting (2/22):

  • Demoed the application to where it’s at for client meeting and for testing purposes
  • Realized Firebase access expired for 3 members, planned to meet with client to regain access
  • Discussed issues we want to work on for the application
  • Discussed divvying up of work for the presentation next week

Week of 2/11/24

(No meetings because of Wellness Days)

  • Got through the dependency issues we ran into while trying to run the app, now able to run the app and are now on par with the progress of last semester’s team
  • Completed Requirements deliverable and reformatted website to utilize sub-pages

Week of 2/4/24

Client Meeting (2/5):

  • Received project through Firebase
  • Discussed plans for the week in order to meet deliverables expectation

Coach Meeting (2/7):

  • Showed coach what we have been trying to run and what errors we are running into
  • Decided on spending time to resolve issues and/or contact previous project team for help

Team Meeting (2/7):

  • Decided to split off to have some Jeremy and Winfield work on the Requirements deliverable while Franklin and Wilson work on resolving dependency issues

Week of 1/28/24

Client Meeting (1/29):

  • Introductions
  • Discussed goals for the project

Coach Meeting (1/31):

  • Introductions
  • Went over course website
  • Obtained background information about last semester’s group’s work on this project
  • Went over deliverables due by the end of this week

Team Meeting (1/31):

  • Discussed coming up with potential user stories to add by class time Thursday
  • Updated team website with Journal page
  • Reviewed older repositories for FanzPlay
  • Decided team roles and updated team website