Projects · 2026

Atura

A Flutter app for warehouse staff that counts, receives and moves stock, and keeps working when the Wi-Fi drops.

  • Flutter
  • Riverpod
  • Drift
  • GoRouter
  • Local queue
test files in the app
62
feature areas, from stock counts to sales orders
11
data modes: sample data or a live server, chosen at build time
2
  • Atura's home screen for a supervisor, with quick actions for stock counts, receiving, tasks and reports
  • Atura's alerts: a low-stock warning, a new task and a count waiting for review
  • Atura's welcome screen, a staff badge on a lanyard showing the time and the afternoon shift

What it does

Atura is a phone app for the people on a warehouse floor. Workers count stock, receive purchase orders and pick up tasks; supervisors assign the work and review counts before they are accepted. Every change is written to the phone first, in a local Drift database, and a queue sends it to the server when the connection allows, so a dead spot between the racks never loses a count.

The app runs in two modes from the same code. Built normally it uses sample data, which is how the screens here were captured. Built with a server address it talks to a real API.

What I learned

  • Write locally, sync later. Treating the phone’s database as the source of truth made offline work the normal case instead of an error path.
  • Keep both modes alive. Sample data kept design work fast long after the server existed, as long as every screen was built against the same repository interfaces.
  • Motion needs a release build. Debug builds on an emulator drop whole animations, so every motion change was checked on a release build.