Loading and delivery request management
The solution comprises three web portals and two mobile apps for both managerial staff and drivers. They provide a full-scale support of the cargo transportation process — from request generation to freight forwarding and order billing.
The client needed an Uber-like system for loading operations and delivery. The goal for the first release was to capture a 3% share of the cargo transportation services market across Texas.
The solution is a B2B system for cargo delivery businesses seeking to outsource transportation services to third party companies. It is accessible via web and mobile helping delivery businesses connect with each other to handle transportation procedures. The app employs Google Maps and facilitates shipping and accounting operations.
The system consists of 5 major parts:
All the freight related administrative procedures take place in the load portal.It enables system administrators to register shipping service providers, manage transportation stages, and generate bills.
Designed for shipping service providers enabling them to process customer orders.
Customer Portal and Customer App
Intended for delivery businesses to generate transportation requests.
Designed for truck drivers. It allows handling delivery orders.
Simplifying code and reducing runtime errors
Softeq implemented business logic using Kotlin, a statically-typed programming language. The team opted for the Clean Architecture principles to divide the software into separate layers. The division approach enabled to further reuse, update, and modify code sections without affecting the rest of the code.
Handling asynchronous operations
To handle the scenarios of sending or responding to delivery requests, or message exchange, Softeq employed RXjava2. The team chose reactive programming paradigm to improve user experience by increasing app’s runtime and responsiveness.
To secure communication between the server and web parts of the solution, Softeq employed token based authentication and SSL cryptographic protocol.
The web part has been rolled out to the client right on time. It fully corresponds to the customer technical requirements. The customer plans to engage Softeq in the support phase, which implies regular software updates or new feature implementation.