Architecture

MrFit will be a native Android app built in Kotlin and use the Gradle package manager, using a mix of Android Studio's Layout Editor and Jetpack Compose for UI design. This app will be using Firebase Cloud for storing cloud data, Firebase User Authentication for managing user accounts, and Firebase Firestore to enable user searches.

Esam:

Nicole:

Lauren:

Nik:

The .apk will be compiled with Android Studio and released here on Github

We are using the emulator built-in to Android Studio for development and prototyping, which will also allow us to test functionality on a number of different android devices.

/* TODO: All of this */ 3. The Models for your app. These could be UML class diagrams, or just models with attributes (with type) and descriptions (in English).

/* TODO: All of this */ 4. How will your app maintain state? in memory? or database? or both? Note this in your Model Classes.

/* TODO: Database schema */ 5. If you are using a db-backend (say firebase) then include the Database schema: set of tables/documents with list of attributes and their types. Documentation for our db-backend can be found here: https://firebase.google.com/docs/firestore

/* TODO: Other queries, how are tags tracked */ 6. List of common queries you expect will be needed. Do any of then need to join tables? Common queries we expect are for the names of an Exercise object, or for the "tags" associated with an exercise, which will be tracked with [BLANK]. To allow for users to search for Workout Templates by tags, we will need a join table with a Workout Template and the Exercises contained within.

/* TODO: All of this */ 7. The Views of your app: name, describe. Embed the images from your Design Milestone. Typically, one page in the app is composed of multiple View elements.