Android application
Kotlin Driver/Admin Mobile App
A Kotlin logistics application with separate driver and administrator workflows, Firebase-backed task state, authentication, maps, and location-aware experiments.
- My role
- Android developer
- Context
- Academic software project
- Reading time
- 5 min read
01
Two roles sharing one task system
Drivers and administrators needed different views of the same work. Administrators create and inspect tasks, while drivers need a focused queue and a clear way to update progress from the field.
The app used role-aware navigation and Firebase authentication to keep those paths separate. The role model affected the data each screen loaded and the actions available after sign-in.
02
Keeping task state current
Firebase provided shared task data and authentication. Changes could appear without each device maintaining its own disconnected copy of the work queue.
The useful engineering work was around state transitions and interface feedback: showing the current task, updating its status, handling missing or delayed data, and keeping administrator views consistent with driver actions.
03
Location-aware experiments
The project code also explored maps, a foreground location service, and geofencing behavior. These features connected a driver's mobile context with task workflows while respecting Android's lifecycle and permission model.
Location work is easy to demonstrate once and harder to make dependable. Background execution, permission changes, service restarts, and stale coordinates all have to be treated as normal states.
04
What the project added to my mobile work
The app brought authentication, cloud state, role-based interfaces, Material Design, and device services into one Android project. It was a useful step beyond isolated activities and static screens.
It remained an academic application rather than a public logistics deployment. I use it as evidence of Android architecture and Firebase integration, not as a claim about a production fleet.
Outcomes
- 01Separate driver and administrator interfaces backed by shared task data.
- 02Firebase authentication and synchronized task workflows.
- 03Maps, foreground location service, and geofencing experiments in Kotlin.
What I learned
- 01Role separation belongs in data access and navigation, not only in visual labels.
- 02Real-time interfaces still need clear loading, failure, and stale-data states.
- 03Android background location features require lifecycle and permission handling from the start.