Delivery service / Web & product interface
JaceTrack
A delivery-service interface with clear shipment entry points and separate customer, rider, and administrator workflows.
The project,
in perspective.
A delivery-service project with a static front-end prototype and a Laravel application. The application source separates customer booking, rider work, and administrative shipment management.
Clarity through
composition.
The design challenge
Serve visitors checking a parcel and customers starting a shipment from the same entry page. Deeper in the product, each role needs an interface suited to its part of the delivery process.
Visual direction
The landing prototype uses cyan actions, navy headings, and a white canvas. Poppins and an illustrated delivery identity create a friendly tone. A dedicated tracking strip sits above the larger service message and shipping call to action.
03 / Information architecture
A place for every task.
- 01
Track or ship
- 02
Customer workspace
- 03
Rider workspace
- 04
Administration
Application routes and views include shipment booking, status tracking, proof and payment review, and reporting. These are role-specific areas, rather than a single linear flow.
UI system
- A prominent tracking field gives returning visitors a direct entry point.
- Consistent cyan buttons distinguish primary actions from supporting navigation.
- Separate dashboard views organize customer, rider, and administrator tasks.
Different screens.
One identity.
The prototype includes a compact mobile navigation and responsive content widths. Desktop and mobile captures are shown as they appear in the original interface, providing a record of this earlier stage of the project.
The original interface,
viewed at 390 pixels.
From interface
to experience.
Front-end approach
The initial interface uses HTML, CSS, JavaScript, and Bootstrap. The application repository uses Laravel 12 and PHP 8.2 with separate routes and views for delivery workflows. The screenshots show the static prototype, not a connected parcel-tracking service.
Final experience
The entry page foregrounds the two central actions: track an existing shipment or start a new one. The public application source provides the broader delivery workflow.