Journal

Coach Meeting #12 (Apr 24, 2023)

• Finished backend / API
• Finished final presentation slides

Client Meeting #9 (Apr 24, 2023)

• Presented slides and app progress udpates

Team Meeting #11 (Apr 20, 2023)

• Split up remaining work (final presentation, backend, edit form, etc.)

Coach Meeting #11 (Apr 17, 2023)

• Presented updates on work

Client Meeting #8 (Apr 17, 2023)

• Presented updates to code
• Discussed hand-off plan

Team Meeting #10 (Apr 13, 2023)

• Split up remaining work
• Set up Monday 4/17 goals:
  • Finish DB (Claire)
  • Finish home page filter/sort (Edward)
  • Different detailed activity view (Will)

Team Meeting #9 (Apr 11, 2023)

• Completed the Hand-off Plan
• Further alterations to the Tech Talk slides

Coach Meeting #10 (Apr 10, 2023)

• Talked about the Documentation Plan
• Presented updates to the codebase

Client Meeting #7 (Apr 10, 2023)

• Presented the updated code and features to the client

Team Meeting #8 (Mar 29, 2023)

• Completed the Documentation Plan

Coach Meeting #9 (Mar 28, 2023)

• changes to test plan
  • add specific end points for API to test
• changes to tech talk
  • duplicate functionality slide and have figures to explain declarative approach and component based architecture
  • add final codesandbox link to last slide + on the website
• updates to demo
  • add categories
  • add filter and sort for time
• documentation plan

Team Meeting #7 (Mar 28, 2023)

• Completed test plan
• Completed tech talk slides

Coach Meeting #8 (Mar 27, 2023)

• TODO
  • make test plan
  • work on documentation plan
  • some changes to the tech talk presentation
    • Tell the audience what we will be building from the start
    • Show people what the end result will be at the start
  • polish the proof of concept

Client Meeting #6 (Mar 27, 2023)

• Showed him progress on home page UI (hosted locally)
• He mentioned that he’d like an advanced search/filter option for duration of activity

Team Meeting #6 (Mar 21, 2023)

• Completed APPLES Reflection 1
• Emailed Stotts with tech talk topic (React.js) and time slot (Monday, April 17)
• Worked on tech talk presentation

Coach Meeting #7 (Mar 20, 2023)

• TODO
  • Email Stotts with tech talk topic & time slot
  • Work on tech talk presentation
  • APPLES Reflection 1

Coach Meeting #6 (Mar 6, 2023)

• TODO
  • Decide on a tech talk topic
  • Put time into coding

Team Meeting #5 (Feb 28, 2023)

• Completed Ethics Assignment
• Made Github Repo: https://github.com/willmao1/Flash-Card-UI

Coach Meeting #5 (Feb 27, 2023)

• TODO
  • Ethics Assignment
  • Start Github repository

Client Meeting #5 (Feb 27, 2023)

• Showed him the UI mock-ups
• Showed him the architecture diagram + explained the tech stack in further detail

Team Meeting #4 (Feb 21, 2023)

• Completed Midterm Presentation (see Deliverables)
• Completed UI mock-ups for Micromoment App & Edit Form
  • Made in Figma
• Completed Architecture Diagram (see Deliverables)

Coach Meeting #4 (Feb 20, 2023)

• TODO
  • Midterm presentation
  • Ethics assignment
  • Architecture diagram (D2)
  • Start coding!
• Ethics assignment suggestions
  • Take a look at open source licenses
    • It has the ethic constraints listed 
  • Main weapon AI
    • Detect Enemies on the battle field
  • Autonomous AI
    • Self driving cars. 
    • Who is liable for accidents
  • Bias of age, race, physical attractiveness, gender, and sexual orientation
    • In regards of employment
  • Requesting funds to support an application 
    • Core-JS (https://github.com/zloirock/core-js)

Client Meeting #4 (Feb 20, 2023)

• Client cancelled meeting due to schedule conflict
• Sending email update instead:
  • functional, non-functional requirements
  • Info about MERN tech stack
  • Interfaces

Team Meeting #3 (Feb 7, 2023)

• Completed functional requirements
• Completed non-functional requirements
• Complete interfaces
• Discussed tech talk ideas
  • Intro to the MERN stack
  • How to deploy a MERN stack with Heroku + Netlify
    • https://dev.to/stlnick/how-to-deploy-a-full-stack-mern-app-with-heroku-netlify-ncb

Coach Meeting #3 (Feb 6, 2023)

• Chosen tech stack: MERN stack
• No coach meeting next week b/c of wellbeing day
• TODO:
  • Functional specs: prioritize user stories
  • Ethics Assignment
  • Possible Proof of Concepts

Client Meeting #3 (Feb 6, 2023)

• Talked to client about tech stack choices
• MERN
  • https://www.mongodb.com/mern-stack
  • https://www.groovyweb.co/blog/mean-vs-mern-vs-mevn-stacks/ 
  • front-end display tier (React.js), application tier (Express.js and Node.js), and database tier (MongoDB)
  • MongoDB works extremely well with Node.js
  • We have experience with elements of this stack, especially React.js
  • Pros:
    • React offers a good experience to the user; Dropbox, Facebook, and Airbnb all use React to make great UI
    • Covers both iOS and Android as a mobile website – meets client needs
  • Cons:
    • Not recommended for development of large-scale web apps
• MEAN
  • https://www.mongodb.com/mean-stack
  • MongoDB, Express, Angular, and Node
  • Pros:
    • Easy to design and test apps hosted on the cloud
    • Covers both iOS and Android as a mobile website – meets client needs
  • Cons:
    • Maintenance is difficult due to many libraries and frameworks, and frequent updates are required
    • App sustainability may be a problem
• Swift
  • https://www.javatpoint.com/swift-vs-objective-c
  • https://www.sam-solutions.com/blog/objective-c-vs-swift-whats-the-difference/
  • Pros:
    • Simplicity (faster learning curve)
    • Advanced, modern functionality make the language safer (less prone to errors) – generics, optional, type inference
  • Cons:
    • No experience among the group
    • No support for versions of iOS before iOS 14
    • Language still in development – could require continual migrations down the line to newer versions of Swift
    • iOS only – doesn’t cover our bases on Android
• Objective-C
  • https://www.javatpoint.com/swift-vs-objective-c
  • https://www.sam-solutions.com/blog/objective-c-vs-swift-whats-the-difference/
  • Pros:
    • Stable, well-tested language (no future migration issues)
    • High C and C++ compatibility
    • Supports all versions of iOS
  • Cons:
    • No experience among the group
      • Steep learning curve, complex syntax
    • Limited functionality due to old age
    • Security issues
    • iOS only – doesn’t cover our bases on Android
• Kotlin
  • https://www.openxcell.com/blog/how-to-choose-technology-stack-for-app-development/
  • https://mindmajix.com/kotlin-vs-java
  • Pros:
    • Easier to have cleaner code
    • Saves on a lot of code space compared to other languages 
    • Completely compatible with JVM so its possible to also use java frameworks at the same time 
  • Cons:
    • Slower compilation time than Java
    • Has a steeper learning curve
    • Has a smaller community and therefore less resources to find solutions
• Java
  • https://www.openxcell.com/blog/how-to-choose-technology-stack-for-app-development/
  • https://mindmajix.com/kotlin-vs-java
  • Pros:
    • Widely used by many large companies and therefore is well supported with greate scalability
    • Many open source libraries and tools to choose from
  • Cons:
    • Can cause problems with android API design
    • An incredibly verbose language which may slow down development
    • Also requires a great amount of memory space

Team Meeting #2 (Jan 31, 2023)

• Deliverables for the week are completed:
  • Project concept completed (seen on Project Introduction page)
  • Deliverables page created
  • User Stories completed

Coach Meeting #2 (Jan 30, 2023)

• Add Louie to Trello or Github when we set that up
  • Github: @mlouielu
  • Trello: louielu@cs.unc.edu
  • https://github.com/mlouielu/COMP523-S23-WebTracking/tree/main/data – tool Louie uses to check our progress on wordpress website updates
• Update website journal with client meeting notes
• Project concept + user stories due at next coach meeting
  • Project concept is done
  • User stories (+ functional requirements)
    • Take a look at previous teams’ examples
  • Add a deliverables tab to the website
• Decide on a more solid tech stack
• Try to implement proof of concept ASAP to share with client and start iterating on it

Client Meeting #1 (Jan 30, 2023)

• Wants to decide between a web app or mobile app that can be used on both iOS or android -> probably should just make a web app 
• Need a backend where all the card data is stored with some way for teachers to add more cards in the future
• Wants it to interact with a database (google or sql)
• Regularly give him testing code (every 2 weeks)
• Make sure the code is organized and well documented
• Implement a Filter function (via tags, class time, )
• Give feedback (can be google forms/allow the client to be able to access it)
  • Names but no need to create users 
• Have the engineering unleashed logo and the grant somewhere (doesn’t need to be prominent tho maybe put in about page)
• Theme can be whatever we want, we can copy the style of the master list but it is up to us

Team Meeting #1 (Jan 24, 2023)

• Going forward, team meetings are on Tuesdays at 12:20
• Updated website with actual project information (Project Introduction, Related Links pages)
• Emailed client to introduce ourselves + ask for his availability
• Updated Journal with team meeting notes
• Brainstormed questions for client
  • Due to the time/resource constraint, we may not be able to develop the app for both iOS and Android. What platform would you prefer we focus on?
  • Are there any specific technologies or languages that you prefer we use?
  • Is there a typo on the website related to question frenzy being repeated so often?
  • Ask more specific details about Curiosity, Connections, Creating Value. What distinguishes them from each other?
  • When users are searching for activities, what will they be able to filter the search based on? (theme, time, name?)
  • Specific Style Guide. UI preferences. Font. Colors. Also will he provide the logo file in some diff formats (svg, png, etc)?

Coach Meeting #1 (Jan 23, 2023)

• Action items:
  • Update website with actual project information
  • Schedule meeting with client
  • Update Journal for team meeting #1
  • Brainstorm questions for client
  • Work on next week’s deliverables (spec, user stories)
• Advice:
  • Take a look at Trello
  • Try to use kanban