<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=504731893395981&amp;ev=PageView&amp;noscript=1">

Mobile and Web App for Cargo Transportation Companies

Loading and delivery request management

  • Android KitKat+
  • iOS
  • Swift 3
  • ReactiveCocoa 5.0
  • Moya
  • Typescript
  • Angular2+
  • Bootstrap
  • Git
  • AWS
  • Jenkins
  • Visual Studio
  • Android Studio
  • xCode
Solution Mobile and web app for cargo delivery businesses
Industry Transportation
Engagement Model Fixed Price
Methodology Scrum
Team
  • Software Developers
  • QA Engineer
  • QA Lead
  • UX/BA Specialists
  • UI Specialists
  • Project Manager
1
2
3
4
5
6

Customer

Problem

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.

Solution

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:

  • LOAD Web Portal (LOAD Portal)
  • Delivery Service Web Portal (DS Portal)
  • Customer Web Portal (Customer Portal)
  • Customer Mobile Application (Customer App)
  • Driver Mobile Application (Driver App)

LOAD Portal

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.

DS Portal

Designed for shipping service providers enabling them to process customer orders.

Customer Portal and Customer App

Intended for delivery businesses to generate transportation requests.

Driver App

Designed for truck drivers. It allows handling delivery orders.

Challenges

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.

Security

To secure communication between the server and web parts of the solution, Softeq employed token based authentication and SSL cryptographic protocol.

Results

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.