Fleet Tracking & Management Platform
Budget: $250 – $750 USD
The core of this build is a real-time vehicle tracking platform that receives GPS and telemetry data from an existing third-party system via its API, stores it securely, and presents it in an intuitive interface. I need a single code-base (or tightly coupled pair) that serves both a responsive web portal and companion mobile apps for iOS and Android, keeping feature parity across devices.
Key functional areas
• Client management – multi-tenant structure where each client can be provisioned with its own dashboard, branding, and role-based user hierarchy (admin, sub-user, read-only, etc.).
• Vehicle hub – add, edit, or archive vehicles; view current status, last contact time, odometer, and any custom fields we map from the API.
• Live map – plot every active unit with auto-refresh, clustering, basic history replay, and drill-down to trip details. Google Maps, Mapbox, or OSM tiles are fine as long as licensing is respected.
• Reports – mileage, stoppage, utilization, and any other analytics you can generate from the raw feed; exportable to CSV/PDF.
• Expense management – log fuel, service, tolls, and miscellaneous costs; tie each expense to a vehicle and surface totals in dashboards.
• Notifications – email / push alerts for geofence breaches, prolonged idling, or data outages.
• Settings & integrations – manage API credentials, set default map layers, and configure scheduled report emails.
Dashboard and very attactive design.
The benchmark application will be shared and need to copy all the features from there.
Data flow & integration
1. Pull: authenticate against the source system and fetch position/telemetry JSON on a configurable interval.
2. Store: normalize and persist in a relational DB with proper indexing for fast map queries.
3. Serve: expose our own REST endpoints (and optional WebSocket) so the web/mobile front ends receive updates in near real time.
Deliverables
• Source code for back-end, web front-end, and mobile apps (Android & iOS).
• Database schema and migration scripts.
• Deployment instructions (Docker or similar) and minimal cloud architecture diagram.
• Basic unit tests and a short user guide.
Acceptance criteria
– Vehicles appear on the live map within 10 seconds of data arrival.
– Role permissions restrict data visibility exactly as configured.
– Reports match raw API figures within ±1%.
– Mobile apps pass App Store / Play Store review.
Timeline
I’m aiming for a “reasonable time” window: a clear phased schedule with milestones is welcome, but quality and stability take priority over sheer speed.
Let me know any clarifications you need about the existing API, preferred tech stack, or deployment environment; I’m happy to provide full documentation once we agree on scope.
Key functional areas
• Client management – multi-tenant structure where each client can be provisioned with its own dashboard, branding, and role-based user hierarchy (admin, sub-user, read-only, etc.).
• Vehicle hub – add, edit, or archive vehicles; view current status, last contact time, odometer, and any custom fields we map from the API.
• Live map – plot every active unit with auto-refresh, clustering, basic history replay, and drill-down to trip details. Google Maps, Mapbox, or OSM tiles are fine as long as licensing is respected.
• Reports – mileage, stoppage, utilization, and any other analytics you can generate from the raw feed; exportable to CSV/PDF.
• Expense management – log fuel, service, tolls, and miscellaneous costs; tie each expense to a vehicle and surface totals in dashboards.
• Notifications – email / push alerts for geofence breaches, prolonged idling, or data outages.
• Settings & integrations – manage API credentials, set default map layers, and configure scheduled report emails.
Dashboard and very attactive design.
The benchmark application will be shared and need to copy all the features from there.
Data flow & integration
1. Pull: authenticate against the source system and fetch position/telemetry JSON on a configurable interval.
2. Store: normalize and persist in a relational DB with proper indexing for fast map queries.
3. Serve: expose our own REST endpoints (and optional WebSocket) so the web/mobile front ends receive updates in near real time.
Deliverables
• Source code for back-end, web front-end, and mobile apps (Android & iOS).
• Database schema and migration scripts.
• Deployment instructions (Docker or similar) and minimal cloud architecture diagram.
• Basic unit tests and a short user guide.
Acceptance criteria
– Vehicles appear on the live map within 10 seconds of data arrival.
– Role permissions restrict data visibility exactly as configured.
– Reports match raw API figures within ±1%.
– Mobile apps pass App Store / Play Store review.
Timeline
I’m aiming for a “reasonable time” window: a clear phased schedule with milestones is welcome, but quality and stability take priority over sheer speed.
Let me know any clarifications you need about the existing API, preferred tech stack, or deployment environment; I’m happy to provide full documentation once we agree on scope.