06 · Concept · iOS app · 2026

Reis

A concept app for importers: where the shipment is, what is missing from the paperwork and when it arrives — without a single call to the forwarder.

Format Concept: idea, flow, screens
Platform iOS 17+, SwiftUI
Screens Five, one end-to-end flow
For whom Importers moving 5–40 containers a year

The problem

A container from China takes twenty-five to forty days and passes through six to eight organisations. What is known about it lives in the forwarder's inbox and in one manager's head, so the client calls three times a week and still hears about problems last.

The concept answers four questions without a call: where the shipment is, what is happening with the documents, when it arrives and what the next shipment will cost.


What is designed
01

The route as stages

Seven steps from pickup to final delivery. Completed ones carry a date and a place, the current one stands out, the rest stay visible but muted. Instead of "ask your manager" — the whole picture.

02

The document that is missing

A missing document is pushed to the top of the screen and named as the reason the shipment will sit in a warehouse. Learning that the CMR is missing on arrival day is the most expensive news in this business.

03

A rate for the next shipment

Route, weight, volume and three switches: HS code lookup, insurance, customs clearance. An indicative price and transit time before the request is sent, not after.

04

Notifications that reach the lock screen

Cleared customs, document needed, vessel departed. News like that has to reach someone who is driving — email does not.


What would be hard
01

The same event arrives twice

Data comes from the shipping line, the port and the customs broker. There is no single API, and part of it arrives by email and spreadsheet. One event reaches the app through several channels with different dates, and the app has to show one version, not three.

02

An ETA cannot be a single number

Arrival is a range plus an honest "being refined". One precise number that reality disagrees with destroys trust in the entire app.

What comes first

I would build one route for one client: seven stages and notifications, without the calculator or the documents. Those add value, but the route is what closes the real pain.


Similar problem? Tell me in one message.