Study.IO

Contributers

• Phi Truong
• Teresa Nguyen
• Edwin Baranov
• Khristian Lopez
• Erik Dan Tran
• Rufus Jin
• Brian Lowther
• Taite Jernigan
• Matthew Nguyen

Introduction

Study.io is an application used to connect users who share similar learning objectives. A user can chose from a variety of topics and either navigate to a pre-existing room or create a new one. Once in a room, the user is able to chat with other room members, asking or giving help, drop learning materials into a group stroage for all other members to access, or even set up events or goals.

Technologies

Front-End

• Node.js
• Express
• React
• React Router (for a multiple page app)
• Google Authentication (user login)
• Firebase File Storage (if we have time) = MUI (a React component library)
• Normalize.css (css normalizer)
• Webpack
• Babel
• Cors
• Axios
• Eslint (customize settings)

Testing Libraries:

• React testing library
• Jest
• Msw (mocking / catching requests)

Back-End

• Node.js
• Express
• PostgreSQL
• Cors
• pg

Testing Libraries:

• Jest
• Supertest
• Deployment
• AWS EC2 instances
• Docker or AMI (AWS)
• AWS Load Balancers
• AWS Auto Scaling Groups

Technical Challenges and research that you anticipated

Google Auth

• Why, what was the plan to overcome those challenges?
• What did you learn?
• What research was required?

File Sharing

• Why, what was the plan to overcome those challenges?
• What did you learn?
• What research was required?

Real Time Chat

• Why, what was the plan to overcome those challenges?
• What did you learn?
• What research was required?

Video Streaming

• Why, what was the plan to overcome those challenges?
• What did you learn?
• What research was required?

Challenges that were unexpected

• Why was it a challenge
• What did you learn?

Video Demo / Screen shot walkthrough of the app

• What were the user stories / what was MVP (mention Minimal Viable Product)

How does the app work?

• What happens behind the scenes when the user interacts with it?
• OR What are all the places the data travels? What happens to that data?
• Optionally include a diagram
• How does the tech stack come together?

Workflow and Key lessons

specifically those related to: Agile, CI/CD, testing, working with external stakeholders, ticketing, and user stories.

• Your git workflow, style guides, commit guides, etc
• What did you learn from the process
• What were key takeaways from stand ups, code reviews, etc
• Writing tests
• Link to your trello board, discuss completed tickets

Performance Optimizations

What additional features do you plan to add, how do you plan to implement those features?

• Future refactoring?
• Additional dev ops considerations?
• UI/UX additions?