How comanalex33/quickfix works
QuickFix connects an Android app for students and handymen and a React administration app to a .NET API. The main workflow is submitting a repair request, making it available to handymen, then updating its status and visit time; the mobile app also retrieves user, building, and category data. Administrators manage users and buildings through the web app. The graph reflects documented capabilities and sampled controller/API behavior; web-page API calls and some server notification wiring were not sampled, so those links are limited to documented interactions.
Main entry points: ApiService.kt Mobile API contract · MainActivity.kt Android app · App.js Admin web app · AppDbContext.cs Application database
Components 23
Client applications
- Android app
Mobile/app/src/main/java/app/quic/mobile/activities/MainActivity.kt - Mobile login
Mobile/app/src/main/java/app/quic/mobile/activities/LoginActivity.kt - Request form
Mobile/app/src/main/java/app/quic/mobile/fragments/MakeRequestFragment.kt - Request views
Mobile/app/src/main/java/app/quic/mobile/fragments/RequestsFragment.kt - Admin web app
Web/web/src/App.js - User management
Web/web/src/pages/Users.js - Building management
Web/web/src/pages/Buildings.js - Category management
Web/web/src/pages/Category.js - Mobile API contract
Mobile/app/src/main/java/app/quic/mobile/services/ApiService.kt - Mobile notification receiver
Mobile/app/src/main/java/app/quic/mobile/FirebaseMessagingService.kt
Server API
- Authentication
Server/Server/Controllers/AuthController.cs - User operations
Server/Server/Controllers/UserController.cs - Request lifecycle
Server/Server/Controllers/RequestController.cs - Building operations
Server/Server/Controllers/BuildingController.cs - Category operations
Server/Server/Controllers/CategoryController.cs - Notification API
Server/Server/Controllers/ServicesController.cs
Persistence and integrations
- Application database
Server/Server/Models/AppDbContext.cs - Email service
Server/Server/Services/EmailService.cs
Other components
- Student
- Handyman
- Administrator
- SMTP provider
- Push messaging
Connections 29
- Student → Android app: uses
- Handyman → Android app: uses
- Administrator → Admin web app: uses
- Android app → Mobile login: opens
- Android app → Request form: opens
- Android app → Request views: opens
- Mobile login → Mobile API contract: calls
- Request form → Mobile API contract: calls
- Request views → Mobile API contract: calls
- Mobile API contract → Authentication: requests
- Mobile API contract → Request lifecycle: requests
- Mobile API contract → User operations: requests
- Mobile API contract → Building operations: requests
- Mobile API contract → Category operations: requests
- Admin web app → User management: routes
- Admin web app → Building management: routes
- Admin web app → Category management: routes
- User management → User operations: manages users
- Building management → Building operations: manages buildings
- Category management → Category operations: manages categories
- Request lifecycle → Application database: reads and writes
- User operations → Application database: reads and writes
- Building operations → Application database: reads and writes
- Category operations → Application database: reads and writes
- Authentication → Email service: sends verification
- Email service → SMTP provider: delivers email
- Request lifecycle → Notification API: notifies handymen
- Notification API → Push messaging: sends push
- Push messaging → Mobile notification receiver: delivers message