Delivery on the field operator's phone

Lyzer Deliver is the Lyzer suite's application for routes, field operation and proof of delivery. It connects with a logistics operation that also includes order management and preparation. While Collect supports preparation, Deliver follows the stage when an order travels to its destination and execution needs to be recorded by the operator.

I worked on Flutter engineering for the suite's Android and iOS operational flows. Work on Deliver connects with the experience of using the application during an operation, representing delivery state and integrating with product services. The interface and data need to make sense throughout a sequence of actions, beyond any individual screen.

Engine and design system shared across the apps

Deliver and Collect share two private Flutter packages: engine and design_system, consumed as Git dependencies from their own repositories. I worked on building and evolving flows within this structure, connecting the interface with data and delivery-operation rules.

The proprietary engine is based on GetX and brings together state management, controllers, navigation, services and reusable capabilities. The design system provides themes and visual components organized using Atomic Design. This division keeps infrastructure and visual language shared while each application implements its own operational journey.

Working across both products provided a view of the path from preparation to delivery and of how information moves between applications and services. That experience involves developing flows on a common foundation, considering how shared conventions affect the suite's consistency and maintainability.

Operational continuity with offline data

Field operations include situations where connectivity is unavailable. Work on offline flows and synchronization accounts for that reality: the application needs to handle data on the device and its integration with services. In Deliver, this context belongs to the product's route, execution and proof-of-delivery experience.

The challenge includes making the operation's state understandable to the person using the phone. The action performed in the application and the information reaching other systems belong to the same process. This relationship between the mobile experience and data was one dimension of my work on the suite's flows.

Service integration and logistics tracking

My Lyzer experience also included a .NET Backend for Frontend. That layer received Android/mobile application requests, queried microservices through GraphQL and HTTP, and assembled the data into a response. Centralizing composition in the backend helped keep this logic outside the mobile client.

In related backoffice work, I developed reusable components, responsive interfaces and refactoring for performance and maintainability. The backoffice supported order management, preparation and delivery tracking. This work complemented my Flutter experience and broadened my view of the relationships between the application, services and operational tracking.

Maintenance supported by investigation and review

To support Deliver and Collect development, I used Flutter Agent Skills and Claude with Sentry access through MCP in investigation workflows. The experience included scheduled investigations and preparing Jira cards and pull requests with explanations, sources and tests for review. The aim was to turn information about problems into engineering work the team could examine.

Deliver has public Android and iOS versions accessible through the official links above. The screenshots show the product and distinguish it from Collect. Download evidence is the snapshot checked in July 2026; this page explains my development and maintenance contribution within a collective effort.