What building a freight marketplace taught us
Lessons from building Tìm Hàng Nhanh, our own app that connects drivers, truck owners and goods owners in Vietnam.
Tìm Hàng Nhanh started from a simple observation: in Vietnam, a lot of freight is still matched through phone calls, chat groups and personal networks. A goods owner needs a truck by tomorrow morning; a driver is heading back from Hanoi with an empty trailer; a truck owner with three vehicles wants them busy every day. All of them are looking for each other, and most of the time they find each other late, or not at all.
We built Tìm Hàng Nhanh as our own product, not as a client project. That meant we carried every decision ourselves: what to build first, what to drop, and how to keep the service running day after day. This post collects what we learned along the way.
A marketplace is two products, not one
The first lesson is that a marketplace has at least two audiences with very different habits. Goods owners want to post a load quickly and get credible offers. Drivers and truck owners want to see relevant loads near their route, without scrolling through noise. In our case there are really three groups, because a truck owner who manages several drivers behaves differently from an independent driver.
Designing one screen that "works for everyone" usually means it works well for no one. We split the core flows early: posting a load, searching and filtering loads, and managing vehicles each got their own path. Shared pieces such as profiles, notifications and messaging stayed common.
Speed matters more than features
Freight is time sensitive. A load posted at 9 p.m. for a 5 a.m. pickup is worthless if the right driver sees it at noon the next day. We learned to measure the product less by how many features it had and more by how quickly a new load reached the people who could take it.
That pushed several technical choices:
- Push notifications filtered by route and vehicle type, so drivers are alerted only about relevant loads.
- A lightweight posting form with sensible defaults, because many users post from a phone in a noisy warehouse.
- Search that tolerates the way people actually write place names, with and without diacritics.
Trust is a feature you build every day
People will not hand over a shipment, or drive four hundred kilometres, for someone they do not trust. Trust in a marketplace is not one feature; it is the sum of many small ones: verified phone numbers, clear profiles, visible history, and a way to report bad behaviour that someone actually reads.
We also learned that trust depends on operations as much as on code. Moderating listings, answering questions and removing spam are ongoing work. When we plan a marketplace for a client today, we always ask who will do this work and how the admin tools will support them.
Mobile first, but not mobile only
Drivers live on their phones, so the mobile apps for iOS and Android come first. Goods owners and dispatchers, however, often work at a desk with several loads to manage. A web version and an admin portal make their work faster and give our own team the tools to keep the platform healthy.
We chose technology that let a small team ship to every platform at once and improve the product week after week, with the apps and the admin tools working as one consistent system.
Keep old app versions working
On a marketplace, not everyone updates their app. Some drivers keep an old version for months. If a new API change breaks that version, they simply stop seeing loads, and they rarely tell you why. We made backward compatibility a rule: any change to an endpoint used by the mobile app must keep every released version working. It slows some changes down a little, and it saves a lot of lost users.
Start narrow, then widen
It is tempting to launch with every vehicle type, every route and every payment option. We found it better to make one core loop excellent: post a load, get it seen, get a call. Once that loop worked reliably, adding features on top became much safer.
What this means for your project
If you are planning a marketplace, a booking platform or any product that connects two sides, the same principles apply: understand each side separately, optimise for speed, invest in trust and operations, and keep your released apps working. We bring that experience to every project we take on. If you are thinking about a product like this, we are happy to talk it through with you.