If you've ever used a Sri Lankan government service, a local bank app, or a telco's mobile client — you've probably felt it. That friction. That confusion. That moment where you tap a button and nothing happens, or worse, something happens but not what you expected.
I've been fascinated by this problem for years. As someone who builds and designs digital products, I see these failures not as bugs, but as symptoms of something deeper.
The Problem Isn't Technical
Sri Lankan developers are talented. Our engineering talent is genuinely world-class — we build products for Fortune 500 companies, contribute to open source, and run startups that get acquired globally.
The problem is culture, process, and priority.
Most local apps are built by teams who treat UI/UX as a finishing step — something you do after the backend is done. Design is often handed off to a junior developer as a ticket: "Make it look nice." There's no user research. No usability testing. No iteration.
"Good design is not about making something look beautiful. It's about making it work beautifully."
The 5 Most Common Failures
1. Information Overload on First Screen
Open most local banking apps, and you're greeted with 12 different options, 3 promotional banners, a news ticker, and a floating support button — all on one screen. The visual hierarchy is nonexistent.
Users don't know where to look. They get overwhelmed and either call the help desk or give up.
Fix: Apply progressive disclosure. Show the user what they need right now. Hide everything else behind a clear navigation pattern.
2. No Error State Design
Type the wrong password in most local apps and you get: a red border. Maybe. Sometimes nothing. Rarely do you get a clear, human-readable message explaining what went wrong and what to do next.
Error states are the most neglected part of UI design, yet they're often the most critical moment in a user's journey.
Fix: Design every error state. Explain what happened in plain language. Provide a clear recovery path.
3. Broken Mobile Responsiveness
Many apps were designed on a 375px iPhone frame in Figma, then handed to a developer who built it for desktop-first and "adapted" it for mobile. The result: misaligned buttons, overflowing text, touch targets that are 20px wide.
Fix: Design mobile-first. Ensure minimum 44×44px touch targets. Test on real devices.
4. Using Technical Language in UI Copy
"ERR_AUTH_TOKEN_INVALID" is not a message for users. Neither is "Please ensure the form data adheres to the required validation schema."
Copy matters. Users read text. When copy is written by engineers, it reads like error logs.
Fix: Hire a UX writer, or at minimum, have a non-technical team member read every error message and UI label aloud.
5. Ignoring Accessibility Entirely
I've worked with apps that have white text on light grey backgrounds (1.5:1 contrast ratio), no keyboard navigation support, and images with no alt text. Accessibility isn't a nice-to-have — it's a legal requirement in many markets and a moral imperative everywhere.
Fix: Use tools like Stark or the built-in accessibility audit in Chrome DevTools. Aim for WCAG AA compliance as a baseline.
Why Does This Happen?
Several systemic reasons:
- No dedicated UX budget. Design is not valued as a discipline — it's seen as decoration.
- No user research. Teams build what stakeholders want, not what users need.
- Short timelines. UX work is cut first when deadlines loom.
- No feedback loops. Apps ship and disappear into maintenance mode without any data on how users actually use them.
What Can We Do?
If you're a designer in Sri Lanka, fight for the user. Document your research. Make the business case for usability — show how poor UX costs money in support calls, churn, and lost revenue.
If you're a developer, read about UX. Study apps you love. Ask why they feel good. Apply those principles.
If you're a product manager or founder, invest in UX before launch. A ₹50,000 Figma audit before development saves ₹500,000 in rework after.
The Sri Lankan tech ecosystem is growing fast. We're building more products, for more users, across more sectors than ever before. Now is the time to raise the bar.
Have thoughts on this? I'd love to hear from designers and developers working on local products.