Overview
What this challenge is about.
Build a Flutter prototype against a mock API serving work orders, asset history, and a parts catalog. Implement: local-first storage with Drift (or Isar) for relational data and a file store for photos, an outbox pattern for mutations, a last-write-wins + manual-conflict-resolution policy for the 3 fields most likely to clash, and an explicit per-record sync state in the UI. Simulate connectivity drops with an in-app network throttle for testing. Deliver: working app build (iOS + Android), 12-page sync architecture doc covering schema, conflict policy, and outbox semantics, and a 6-page pilot plan for 20 technicians over 4 weeks.
The Brief
What you'll do, and what you'll demonstrate.
Build an offline-first Flutter field-service prototype with a defensible sync architecture that reconciles cleanly after multi-hour connectivity gaps.
Earning criteria — what you'll demonstrate
- Design an offline-first mobile data model with explicit sync state
- Implement an outbox pattern for reliable mutation replay
- Define a conflict-resolution policy that survives field reality
- Communicate sync trade-offs to a non-technical operations VP
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.