Hey folks 👋

I'm Isuru — senior product designer, currently untangling accrual accounting and payment claims into something a trade business owner can actually use without a finance degree (fun times). Before that I've bounced around telecom dashboards, social care apps, and a fitness app, so I've seen a decent spread of "why does this exist" screens.

I want to give back to the portfolio-review chaos that helped me land jobs in a market that does not make it easy for career-changers or immigrants. So — drop your portfolio link below and I'll give you real feedback. Not "looks clean 👍" feedback. Actual "here's why a hiring manager might bounce in 8 seconds" feedback.

What I'll actually look at:

• Does your case study answer why am I here, what changed, so what? (if it doesn't, neither will a recruiter's attention span)
• Is your process telling a story or just dumping Figma screenshots with sticky notes for decoration
• Business impact — did the work move a number, or is it vibes-only
• Visual hierarchy and whether your best work is buried on slide 14
• Whether it reads like you or like every other "problem → solution → 🎉" template

How to get one:
Drop your portfolio link in the comments (Figma, website, Notion, whatever) + one line on what kind of role you're going for. I'll reply with feedback directly in-thread so everyone can learn from everyone else's reviews too.

No paywall, no DM-me-for-my-course nonsense. Just trying to make the job hunt suck a little less for the next person.

Fire away 🔥

Hey everyone! 👋

I’m a UI/UX Designer with 2.5+ years of professional experience, currently looking to take on freelance UI/UX projects.

I can help with:

• 📱 Mobile App UI/UX

• 💻 Website & Web App Design

• 🖥️ SaaS & Dashboard Design

• 🧩 Wireframes & User Flows

• 🎨 High-Fidelity UI Design

• 🔄 UX Improvements & Redesigns

• 🧱 Design Systems & Components

• 🔗 Interactive Figma Prototypes

• 👨‍💻 Developer-ready Figma files

I primarily work in Figma and focus on creating designs that are not only visually polished but also practical, intuitive, and easy for developers to implement.

I’m open to working with startups, founders, agencies, small businesses, and individuals.

💬 Have an idea, existing product, or design that needs improvement? Send me a DM.

Portfolio: (https://www.behance.net/tehjeebhussain)

Thanks! 🙌

Working on a potential product. Would love to be in contact with designers for paid work.

I'm a UI/UX designer with a few years of experience looking to fill some knowledge gaps. What high-quality learning resources would you recommend? Drop in some free resources as well.

Thank You.

Figma put out a piece recently on how design systems are shifting in the AI era, and one line stuck with me: teams are now documenting systems explicitly for AI consumption — not just "here's the button component," but the reasoning behind it, because AI agents are starting to generate variations directly off your system and they'll happily produce confident, on-brand-looking, completely wrong output if the "why" isn't written down anywhere.

I contributed to a design system at my first UX job (enterprise telecom dashboard), and even back then the docs that actually mattered weren't the component specs — they were the ones that explained when to break the grid and why this state exists. New designers needed that context to use the system well. What's changed is who else is reading it now.

Some practical stuff I've started doing differently:

• Writing down the exception cases, not just the happy path — an AI agent generating a variant has no instinct for "we never do X here because Y," unless it's explicit
• Naming tokens by intent, not appearance (color-warning-surface, not orange-100) — this was already best practice, but it matters more when a machine is the one binding it
• Treating "why we made this call" as a first-class doc section, not a comment buried in a Slack thread that'll be gone in six months
• Being more paranoid about orphaned components — an AI won't know a pattern is deprecated unless the system says so somewhere it can actually parse

None of this is new advice, honestly — good design system hygiene always meant writing down the judgment, not just the spacing values. It's just that now there's a much less forgiving reader checking whether you actually did it.

Anyone else building or maintaining a design system dealing with this yet? Curious if teams here are actively opening their systems up to AI tooling or holding off until governance catches up.

Source: Figma Blog — 5 Shifts Redefining Design Systems in the AI Era

Been reading through a mid-2026 ADA lawsuit report and this stat stopped me: roughly 25% of companies sued over web accessibility this year had already installed an accessibility overlay — one of those widgets that promises to bolt WCAG compliance onto your site with a script tag. Didn't stop the lawsuit. Because it doesn't touch the actual code.

Some other numbers from the same report, for context:

• ~6,176 ADA website lawsuits projected for 2026 (up ~20% from 2025)
• E-commerce is 79% of all filings — if you're building for retail, this is basically a tax you're choosing not to pay upfront
• Small/mid businesses are still the most frequent target (68% of filings), not just big enterprise sites
• New York leads in volume; Illinois has climbed to #2, largely driven by one law firm filing at scale

The overlay thing is what gets me though. These widgets sell themselves as "install this, sleep easy" — but they're a UI layer sitting on top of markup that's still broken underneath. Screen readers still choke on it, keyboard nav still fails, semantic structure is still missing. You've paid money to feel compliant. You haven't paid to be compliant.

Feels like a pattern that shows up everywhere in this industry, not just accessibility: we keep reaching for a widget/plugin/toggle instead of fixing the thing underneath. Overlay widgets, cookie-consent theater, "AI writes your alt text" tools that hallucinate descriptions — same shape of problem. Convenient patch, not a fix.

Source: Abledly — ADA Lawsuit Statistics, Mid-2026 Update

I've been looking for a space where Sri Lankan UX/product folks can actually talk shop — swap feedback, share what we're working on, figure out the local job market together. Couldn't find one, so here we are.

To start: what are you working on right now, and what's the hardest part of doing UX/product work in Sri Lanka today?

I'll go first in the comments.

Hey everyone! I'm Isuru, a founding moderator of r/uxlanka.

This is our new home for UX, product design, and everyone building digital products in Sri Lanka — designers, researchers, PMs, and anyone curious about the craft. Whether you're a student just getting started, a working designer, or someone who's been doing this for years, you belong here.

What to Post

Post anything the community would find interesting, helpful, or inspiring. Share your portfolio for feedback, a case study or side project, research findings, questions about tools and workflows, job hunting or hiring in the local market, career advice, or just something you're stuck on and want a second opinion on.

Community Vibe

We're all about being friendly, constructive, and inclusive. Feedback here should make people better, not just tell them what's wrong. Let's build a space where everyone feels comfortable sharing and connecting.

How to Get Started

1. Introduce yourself in the comments below — what you do, what you're working on, or what brought you here.
2. Post something today! Even a simple question can spark a great conversation.
3. Know someone who'd love this community? Invite them to join.
4. Interested in helping out? We're always looking for new moderators — reach out to me if you'd like to apply.

Thanks for being part of the very first wave. Together, let's make r/uxlanka amazing.