✍️
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
  • Expo
  • Appetize
  • Heroku

Was this helpful?

Deployments

Where our app lives.

PreviousAbstraction Occurrence PatternNextTrying Our App

Last updated 3 years ago

Was this helpful?

Expo

We deployed our app on Expo's servers for testing purposes.

Appetize

We've also deployed our app on the iPhone simulator hosted on Appetize.

Heroku

Our data is stored on Heroku servers.

In addition, our micro-application for scraping food prices is also deployed on Heroku.

https://food-pricer.herokuapp.com
LogoExpoExpo
LogoDemo
http://freshie-api.herokuapp.comfreshie-api.herokuapp.com