Skip to content

Latest commit

 

History

History
76 lines (49 loc) · 2.67 KB

README.md

File metadata and controls

76 lines (49 loc) · 2.67 KB

Squatify

This is an app that tracks your daily squats. At the School of Code, it's a tradition to kick every morning off with a bunch of squats done to a song of choice. As students of the School of Code, we created this app as an nod to this tradition.

See It Live

Click this link to test the app. https://squatify.netlify.app/

Installation

First clone the frontend and backend repositories.

git clone https://github.com/anastasia-starostina/Squatify-App.git
git clone https://github.com/DHawkesford/squatify-backend.git

Within each repo, run this command to install the dependencies.

npm i

If you'd like to connect this app to your own database, follow the steps below (we used Heroku).

Create your own .env file at the root level of your repository and add your database URI in here. Avoid using quotation marks.

DATABASE_URL=<add your database uri>

DATABASE_URL is the variable being called in the connection pool in squatify-backend\db\connection.js

Tech Stack

Client: React, styled components

Server: Node, Express, PostgreSQL

Database Heroku

What We Have Learnt

  • Used styled components for the first time
  • Cemented various React concepts (state, props, useEffect)
  • Figma collaboration (wireframes)

Challenges

  • Infinite loop caused by incorrect use of useEffect hook. We used a piece of boolean state to get around this. See useful links section below.
  • Deployment of backend repository of heroku. Environment variabled needed amending in .env file.
  • Initial rendering of styled components. Read through the docs and overcame this fairly quickly.
  • Media Queries (The App only looked good on a PC screen and didnt respond well on mobiles, so we researched media queries and added a few in to make the app more mobile responsive)

Take Aways

This experience helped us reinforce our learning of working in an Agile environment. We used various project managements tools such as Trello and Figjam. We stuck to Agile principles (ticket backlog, retrospective and standup discussions), and we took on an iterative approach to our workload.

Our ability to work with React and deploy full stack applications has become more natural.

Useful Links

Authors