How sotirissapak/gym-management-system-application works
Project type and purpose
• This is an Android full‑stack mobile project comprised of two separate applications (modules) targeting gym management:
• Admin App (module “app”)
• Client App (module “client version/app”)
• Purpose: Admins can digitally manage receipts, messages, and opening hours via Firebase Firestore; clients can register/login, view receipts, messages, and gym schedule.
File structure
• Top‑level modules
• app/… → admin version
• client version/app/… → client version
• Each module follows a standard Android Gradle layout:
• src/main/java: Activities, Fragments, Objects (models), Utils, Adapters
• src/main/res: layouts, drawables, menus, values, anim
• src/androidTest, src/test: instrumentation and unit tests
• Configuration files
• build.gradle (module and root)
• google‑services.json (Firebase config)
• proguard‑rules.pro
• settings.gradle including both modules
README for additional insights
• Confirms two separate Android apps (admin & client)
• Backend: Firebase Firestore online DB with collections: Users, Receipts, Messages, OpeningHours
• Basic Firebase schema provided
Components
a. Main components
– Admin Android App
– Client Android App
– Firebase Authentication (login/register)
– Firebase Firestore (collections: Users, Receipts, Messages, OpeningHours)
– (Optional) Local handlers: AppDataHandler/MemoryHandler for caching
– (Optional) NetworkConnection/InternetConnection utility
b. Relationships/interactions
1. User opens Admin or Client App → prompts Firebase Auth
2. On successful login: app reads/writes Firestore collections
• Admin App: CRUD on Receipts, Messages, OpeningHours, Users
• Client App: Read Receipts, Messages, OpeningHours
3. Firestore sends real‑time updates (listeners in Utils/Others) to apps
4. Local cache via MemoryHandler/AppDataHandler for offline view
c. Architectural patterns/design principles
– MVC/MVVM‑like separation:
• View: Activities & Fragments
• Model: Objects (User, Receipt, Message, ToUserMessageDocument, etc.)
• Controller: Utils (network, data handling), Adapters (RecyclerViews, ViewPager)
– Modular Gradle setup with two Android modules
– Dependency injection via static Utils methods (singleton pattern)
d. Key technologies/frameworks
– Android SDK
– Firebase: Auth, Firestore real‑time DB
– Google Services plugin (google‑services.json)
– Gradle build system
– AndroidX libraries (RecyclerView, ViewPager, Fragments)
Detailed call‑outs
– Under Admin App: highlight Activities (HomeActivity, LoginActivity, PreferencesActivity), Fragments (DashboardFragment, MessagesFragment), Utils (AppDataHandler, NetworkConnection)
– Under Client App: highlight MainActivity & its Fragments, Adapters (RecyclerViewMessagesAdapter), Utils (InternetConnection, MemoryHandler)