There's an easy way to design a ride-hailing app.
You sit in an air-conditioned room. You open a whiteboard. You draw a passenger, a driver and an arrow between them. You argue about button colours, write down what you think people need, and ship it.
It's fast. It's comfortable. And in African cities, it's almost always wrong.
Because the person you drew on that whiteboard isn't the student who leaves home at 5:30 to reach a 7:00 class. It isn't the trader carrying three bags of goods to the market, negotiating a price before every single trip. It isn't the parent standing at the roadside with a child, waiting, wondering whether the next motorbike that stops is safe. It isn't the worker who has walked the last kilometre home so many times that it no longer feels like a choice.
None of them live on a whiteboard. They live on the road.
So we made a decision early, and we made it publicly: Twende doesn't want to imagine your journeys from an office. We want to understand what you actually live.
We took our questions to the roadside
We launched a campaign with a simple invitation to the people who know transport best, the ones who live it every day.
Passengers, students, workers, traders and parents: tell us what moving through your city is really like. The long waits. The prices. Safety. Your routes. The small, daily difficulties that nobody writes reports about.
And tell us however you want:
- By text, if writing is how you think.
- By voice note, if speaking is easier, faster, or simply more natural.
- By photo, of the junction where you wait every morning or the road that floods every rainy season.
- By short video, of the moment that frustrates you most.
And when that isn't enough, our teams on the ground come to you and ask their questions face to face, at the bus stop, the market, the moto stage, the campus gate.
It sounds like a small thing. It isn't. Every one of those choices was deliberate, and each one says something about how we intend to build.
Why not just send a survey?
Because a survey only hears the people who are comfortable with surveys.
A form with ten multiple-choice questions assumes your reader writes easily, has time, has data to spare and agrees with the way you framed the question in the first place. In the cities we're building for, plenty of people don't tick all four boxes. Those are often exactly the people whose daily journeys are hardest.
A voice note lowers the barrier to almost nothing. Someone can tell us about their morning commute while they're living it, in their own words and in whichever language comes naturally, without worrying about spelling or a keyboard.
A photo says what words can't. "The pickup point is bad" is an opinion. A picture of a dark, muddy corner with no streetlight is a design requirement.
A field conversation catches what nobody would think to write down. The pause before someone answers a question about safety. The detail they mention almost in passing. The follow-up question that turns a vague complaint into a problem we can actually solve.
We want the full picture, not the tidy one. That means meeting people where they are, in the format that suits them, not the one that suits us.
Listening for problems, not features
There's a trap in asking people what they want. Ask enough people and you'll get a list of features: an app that does this, a button that does that.
That isn't what we're looking for.
We don't ask people to design Twende for us. We ask them to describe their reality, and then it's our job to design for it. People are experts in their own lives. They know exactly where it hurts. Turning that pain into a product is our responsibility, not theirs.
So our field teams don't ask "what feature would you like?" They ask questions like:
- What happened on your last trip?
- How long did you wait, and what did you do while you waited?
- How did you agree on the price?
- When did you last feel unsafe, and why?
- What do you do when you can't find a ride at all?
Answers to questions like these are worth more than any feature request. They reveal the real constraints: cash in your pocket or not, battery on your phone or not, light on the street or not. A feature built on those constraints works on the road. A feature built on assumptions works in a demo.
What listening has already taught us
Many of the principles we've written about in this blog are things passengers had been telling us long before we wrote them down.
People are tired of negotiating every trip. Haggling is exhausting, and it's never quite fair to anyone. That's the heart of why we believe in fixed pricing, where you know what you'll pay before you get on.
Safety isn't a feature. It's the first question. Whether a trip feels safe decides whether people take it at all, especially at night, and especially for women and parents travelling with children. It's why safety runs through everything in Safety first, down to the very practical promise of two helmets per moto.
Not everyone pays the same way. Some people live on mobile money. Some live on cash. Forcing one on everyone shuts people out, which is why we built Twende to let you pay your way.
None of these are clever insights. That's exactly the point. They're obvious to anyone who spends a morning at the roadside, and invisible to anyone who doesn't.
Hand in hand with drivers too
Passengers are only half of every trip.
Drivers spend more time on the road than anyone. They know which streets close when it rains, which neighbourhoods have no signal, where passengers really wait and what a fair day's earnings look like. They carry the costs of fuel, repairs and slow days on their own shoulders.
Building hand in hand means building with them, too. A platform that works for passengers but squeezes drivers isn't a mobility solution. It's just a new way of moving the problem around. When we design how drivers join Twende, how they're paid and how they're treated, we want drivers to be part of that conversation, not just on the receiving end of its decisions.
The honest part: listening is hard
We'd be lying if we said this approach was easy. Building with the people you serve has real costs, and we think it's worth naming them.
- It's slow. Sitting with a trader for twenty minutes takes longer than reading a market report. We think it's worth it, and we accept the time it costs.
- People disagree. One passenger wants the cheapest ride possible. Another will pay more for comfort. A student and a business owner have very different mornings. Listening doesn't give you one answer. It gives you the full range, and you still have to make choices.
- The loudest voice isn't always the most important one. The person who sends five videos isn't necessarily more representative than the person who barely had time to send one voice note. We have to look for patterns, not volume.
- Not everything is an app problem. Some of what we hear is about roads, policing, flooding and fuel prices. We can't fix those with software. But we can understand them, design around them and share what we learn with the people who can.
- Listening creates a debt. When someone takes the time to share their reality with you, you owe them something in return: proof that it mattered.
That last one matters most to us. Asking for feedback and then disappearing is worse than never asking at all. It teaches people that their voice doesn't count. We'd rather ask less often and show what changed than collect stories nobody acts on.
Why this is a strategy, not a campaign
It would be easy to read all this as marketing. A nice campaign, some videos, a hashtag.
For us, it's the opposite. It's the core of how we intend to win.
Global ride-hailing companies arrive in African cities with products designed for somewhere else, then adapt them at the edges. Local competitors often know the streets but don't have the technology to scale. Our advantage has to be that we understand the people better than anyone, and that we build the technology to match.
That understanding can't be bought, copied or downloaded. It's built one conversation at a time, in one neighbourhood and then the next, in every city we enter. It's also why we don't think the Twende we launch in the DRC will be exactly the Twende we launch in Uganda, or later across East and Central Africa. The principles stay the same. The details have to come from the people who live there.
That's what we mean when we say Twende is Africa's answer to safe mobility. Not an answer imported from elsewhere, but one built here, with the people who need it.
Our opinion, stated plainly
- You can't design for a road you've never stood on. The best mobility solutions start at the roadside, not on a whiteboard.
- Meet people in their format, not yours. Voice notes, photos and conversations reach people that surveys never will.
- Ask about reality, not features. People are experts in their own lives. Designing the solution is our job.
- Listen to both sides of the trip. A platform that serves passengers but squeezes drivers isn't a solution.
- Every voice deserves an answer. If you ask people to share their reality, you owe them proof that it changed something.
Go back to that roadside for a moment.
The student is still there at 5:30. The trader still has three bags of goods. The parent is still holding a child's hand, watching the motorbikes go by.
But this time, someone is listening. Someone is asking how long they waited, what they paid, whether they felt safe. Someone is writing it down, and taking it back to a team that will build around it.
That's how we are building Twende, Africa's answer to safe mobility. Not from an office. From the road, hand in hand with the people who live on it.

