Ta7t Eltalab

The brief

An on-demand services platform: a customer describes what they need, a provider accepts it, and the job is tracked to completion. Three parties, one of whom is moving, and a state machine that has to survive a phone losing signal in the middle of it.

My part

Flutter development on the customer-facing application: request creation, provider matching, live tracking on a map, and the completion and rating flow.

Decisions

Request state lives on the server, not in the app. The app renders what the backend says the request is. Anything else means two devices can disagree about whether a job was accepted, and the customer and the provider each believe their own screen.

The map is a view, not the model. Tracking is a stream of positions rendered onto Google Maps; the request does not become invalid because the map failed to load.