iFixIt Ticketing App
The application supports role-based request handling, real-time communication, offline drafts, feedback, and operational dashboard views.
Role and Contribution
Team lead and Flutter/Firebase contributor across workflow design, application behavior, and mobile implementation.
Problem and Context
The app was designed around service-ticketing needs: customers submit requests, technicians manage work, and administrators need visibility into request status and operational activity.
Solution Overview
The product uses Flutter for the mobile interface and Firebase services for authentication, Firestore-backed data, real-time communication, offline drafts, feedback, and Cloud Function-backed prediction behavior.
Architecture View
Engineering Decisions
- Use role-based routing so customer, technician, and admin users see workflows relevant to their responsibilities.
- Use Firebase Authentication and Firestore to support real-time app behavior without adding a custom backend for the project.
- Include offline drafts and priority escalation so ticket creation and triage remain practical under imperfect conditions.
Technical Challenges
- Coordinating team delivery across multiple user roles and feature areas.
- Balancing real-time chat, offline behavior, feedback, analytics, and prediction features without losing the core ticket workflow.
Outcome and Current Status
Completed application work. The original repository is private, so the portfolio presents the case study without exposing private source code.
Lessons and Next Steps
- Add approved screenshots if private project details are cleared for public use.
- Document more implementation details when they can be shared without exposing private source.