Product
A Payment App That Works in India Can Flop in Malaysia
I moved from India to Malaysia assuming good app design travels. Then I opened the local apps and asked how anyone uses them. The answers were mostly cultural.
app design Malaysiasuper app designcultural differences in app design
When I opened my first Malaysian and Chinese apps after moving from India, my honest reaction was: how do people even use these? I had spent years with US and Indian apps, and I assumed good fintech UX was a portable skill.
It is not, or at least not as portable as I believed. A payment flow that feels clean and obvious in one country can feel thin in another. Below is what I found out when I stopped judging and started asking. I should say up front that I am not claiming a specific payment app of mine failed. This is about how I changed what I look for, based on research and conversations with local users and native product people.
Why did Malaysian apps look so crowded to me?
Because I was reading them with a Western eye. The apps I knew leaned minimalist: think of the clean lines of a famous search page, or the uncluttered interface of an American banking app. Simplicity and ease of use come first.
Malaysian and Chinese apps, like many across Asia, tend toward a maximalist look. They pack in features, icons and information, which produces a visually rich, busy experience. To me it looked like clutter. To the people using it, my understanding is that it reads as normal, because the design grows out of cultural preferences and expectations.
What is a super app, and why does it change payments?
A super app is one platform that offers many services. WeChat in China and Grab in Southeast Asia are the examples I keep coming back to. Messaging, social networking, payments, e-commerce and even ride-hailing sit in one place.
For payments this is a big shift. In my old frame, a payment app was its own thing and had its own screen. Here, payments are one tab among many, and users are already inside the app for other reasons. My read is that this suits collectivist cultures like Malaysia, where community and interconnectedness matter, and where one app that handles daily tasks can feel indispensable. That reading comes from my research and conversations, so treat it as informed opinion and not a measured result.
Which cultural differences actually drive the design?
Three pairs came up repeatedly in what I read and heard:
| Asian tendency | Western tendency | What it does to the app |
|---|---|---|
| Big-picture: interconnected elements, the bigger picture | Individualistic: independence, autonomy | Many features and information at once, against one task at a time |
| Polychronic: several tasks and activities at once | Monochronic: one task at a time | Lots of options for multitaskers, against fewer distractions |
| High-context: implicit cues, shared understanding | Low-context: explicit, direct information | Assumes you know the symbols and conventions, against explaining everything |
The last row interests me most as a PM. If you design for low-context users, you add labels, steps and explanations. If your users are high-context, that same help can feel slow or even a bit patronising, while a screen assuming shared knowledge feels efficient. I would not have guessed that before this move.
Is it only culture, or also technology?
Both. Many Asian countries went mobile first and skipped the desktop era, which pushed designers toward phone experiences with more functionality packed into smaller screens. That is part of why density looks normal there.
I do not know how to split the credit between culture and infrastructure. My guess is they reinforce each other, and I would be suspicious of anyone who gives you a clean percentage.
So can you copy a winning design into a new market?
Not safely. It is tempting to take a flow that tested well in India or the US and ship it unchanged. Success in one market tells you what worked for those users with that context. It does not tell you what will work for people with different expectations about density, tasks and how much the app should assume.
Culturally informed design might mean embracing the maximalist feel of a super app. It might mean using symbols and metaphors that are familiar locally. Either way, it starts with understanding the people before you touch the interface.
What would I do before localising a payment app?
- Use the top local apps for a week before forming opinions. Notice your own first reaction, then question it.
- Talk to local users and native product people. They will tell you what you are misreading.
- Check whether payments live inside a bigger app in that market, and what that does to your entry point.
- Decide where you should assume context and where you should explain, instead of copying your home market’s default.
- Keep your first reaction as data. “Cluttered” tells you what you are used to.
I am still early in this. The move happened recently when I wrote the original version of this, and I have more to learn about how culture and technology shape what people expect from an app. What I know for now is that my first assumption was wrong, and I would rather find that out by asking than by launching.