Cross-platform factory ERP app used daily on-site for stock tracking and task management
We built the full Flutter client and Django REST backend for a production app that workers in a factory use every day. The project rewards reliability and usable flows over launch-page polish.
Problem
Factory workers needed a cross-platform mobile app for daily operations: stock tracking, task assignment, and status updates. Browser-based tools were impractical on a factory floor.
Approach
A full Flutter client covered every required workflow, built for usable flows under real conditions: gloved hands, poor lighting, fast task completion. A Django REST backend served all data through typed API endpoints. We matched the architecture to what the use case needs and stopped there.
Architecture
A Flutter cross-platform client (iOS and Android from a single codebase) talks to a Django REST Framework backend, with PostgreSQL for persistence and token-based authentication. We kept the API contract simple and stable, so the mobile client ships on its own schedule, separate from backend changes.
Outcome
The production app is in daily use by factory workers for stock tracking and task management. We delivered it as a complete system, client and backend, with no dependency on third-party mobile platforms or cloud sync services beyond the client's own infrastructure.
Context
The client ran a manufacturing facility and needed a mobile tool for floor workers to track inventory movements and manage daily tasks. Browser-based tools fall short in a factory environment. Workers needed a native-feeling app they could open between physical tasks, without handling a desktop interface on a shared terminal.
Flutter implementation
We built the client app in Flutter, targeting iOS and Android from a single codebase. The UI centers on operational clarity: large tap targets, shallow navigation, and status feedback that holds up under changing light. We kept state management plain and skipped reactive layers a CRUD-heavy workflow app does not need. Screens covered stock lookup, quantity adjustments, task lists, task status updates, and basic reporting.
Backend
The Django REST Framework backend exposed typed endpoints for each mobile workflow. Authentication used token-based auth, which fit a controlled internal deployment. We designed the API contract to stay stable across mobile app updates, versioned where it had to be and flat where it could be. PostgreSQL handled persistence with plain relational models that matched the factory's existing data concepts (articles, locations, tasks, assignments).
Delivery approach
We delivered the project as a complete system, client and backend together, instead of a frontend handed off to a separate backend team. The mobile screens drove the API design, not a generic REST spec. We measured the work by reliability and usable flows, since a failure on the factory floor costs more than a failure in a consumer app.