✍️
Team FitBob
  • Introduction and Foreword
  • Motivation
  • Features
  • Tech Stack
  • Software Engineering Practices
    • Requirements
    • Software Design Patterns
      • Model View Controller (MVC)
      • Abstraction Occurrence Pattern
  • Deployments
    • Trying Our App
  • Activity diagram
  • Frontend
    • Login
    • User Registration
    • Client Screens
      • Client Dashboard
      • Client Profile
      • Eating History
      • Meals
    • Personal Trainer screens
      • Personal Trainer Profile
      • Personal Trainer Dashboard
        • Clients
        • Meal plans
        • Meals
    • Recipe screens
    • Search screen
    • Searching for Restaurants
    • Notes on BeautifulSoup and Flask
    • Request/Success/Failure Cycle
  • Backend
    • Notes on Django
    • API
    • Entity relationship diagram
  • Testing
    • User Testing
    • Backend
  • Project Limitations and Constraints
  • Closing Thoughts.
  • Project log
  • Poster
Powered by GitBook
On this page
  • React Native
  • Django
  • BeautifulSoup and Flask

Was this helpful?

Tech Stack

What we used to build Freshie!

React Native

To build the user-interface for our application, we chose to go with React Native as it seemed to be a reasonably mature framework with many well-supported packages available.

Some notable ones include:

  • React Navigation

    • used to direct users between screens

  • Redux

    • used to handle the state of global-variables

  • Axios

    • making API-calls to the backend

Django

We used Django to create the backend-framework necessary to handle user authentication and store the data for our app!

BeautifulSoup and Flask

We made a little application using BeautifulSoup and Flask to fetch the prices of ingredients from NTUC and Cold Storage!

PreviousFeaturesNextSoftware Engineering Practices

Last updated 3 years ago

Was this helpful?