Overview

SwiftDrop is a university team project for parcel delivery and courier management. It brings customer booking and courier operations into a React web workspace and a Flutter mobile application, backed by .NET services.

The codebase is split into backend, frontend, mobile, infrastructure, and documentation repositories. The wider product scope includes Customer, Courier, Merchant, Dispatcher, and Admin roles; those requirements extend beyond the implemented workflows.

Booking and delivery workflows

The current booking implementation collects pickup, destination, recipient, and package details, requests a server fee estimate, and requires explicit confirmation. PostgreSQL persistence keeps a booking and its associated records together, while retry recovery avoids treating an uncertain response as a new booking.

Courier features include a service-day manifest, assigned-parcel details, versioned status updates, failure reasons, and completed-delivery history. Final delivery requires a photo or signature. The proof workflow validates image content, stages private storage, and guards the final state transition.

React and Flutter clients implement these workflows against shared contracts. The web application also includes local and Google sign-in, profile connections, and Admin identity screens using a shared shadcn/ui dashboard system.

Service boundaries

The backend separates Identity, Delivery Operations, Merchant Integration, a YARP gateway, and a notification worker. Implemented delivery writes include ownership and concurrency checks, with atomic status, history, outbox, and replay records.

The proposed integration design adds asynchronous notifications and webhooks around those records. Documentation describes the intended boundaries and contracts; it does not establish that every service integration has shipped.

Current state

The platform is under active development. Delivery and Merchant authentication handoffs, messaging relay, public tracking, GraphQL, SSE, and gRPC handlers remain integration work. Positive Delivery HTTP tests use isolated test-host principals; normal clients require the corresponding authenticated session adapters.

Work continues on connecting the tested booking and courier workflows into a complete authenticated journey across web and mobile.