I'm Syed Mudaseer, a UI/UX and product designer looking for my next full-time role. For three years I've been the only designer on 12 freelance client projects, from SaaS dashboards to e-commerce and marketing sites, owning research, user flows, hi-fi UI in Figma, design systems and developer handoff. I'm open to relocating and to remote teams.
Suminagashi — move your cursor to stir the ink · click to drop a ring
Three case studies I designed and built end to end: my own reading app and two client projects, a store and a gym app. Behind them, three years of freelance client work, most of it under NDA.
Scan a page you read and the app turns it into a summary, a word game and spaced flashcards — so the idea survives past the highlight.
A reading-retention app for people who highlight everything and remember nothing. I designed the capture → insight → recall loop, then rebuilt it as a working app and tested it on the same people I'd interviewed.
A black, premium storefront for an Indian embroidered-tee label, where picking a colour spreads over the shirt like a symbiote.
Designed around one signature interaction and a product card where every tap answers back. Shipped as a working store, reviewed by a second AI system and tested in a real browser before handover.
A gym app where members show one QR pass at the door and the owner sees who's in and who's paid, from the same phone.
Two apps in one: a member side for the pass and UPI payments, and a hidden owner side for check-ins, approvals and the monthly money. Designed around zero running fees, then built in Flutter for iOS and Android from one codebase.
Client work (2023–2026). Twelve freelance projects across SaaS dashboards, e-commerce and marketing sites — most protected by NDAs, so they don't live on a public page. I'm happy to walk your team through more of my work on a call: just ask.
Daily Recall scans a page from a book and turns it into a summary, a word game and spaced flashcards — closing the gap between highlighting something and actually remembering it.
It started the way a lot of usable products do — with a problem I was living. My reading habit was leaking; I'd finish a book and keep almost none of it. Before designing anything, I checked whether the pain was mine alone.
Those view counts weren't opinions — they were a crowd quietly raising their hands. The same question, asked by millions, across unrelated creators. My private frustration was a widespread, under-served need. That was the green light.
One question — "how do I remember what I read?" — pulling 17M+ combined views across unrelated channels.
Someone had tried to solve this — I found Readwise and genuinely wanted it to be the answer. The value was there in theory, but the experience cost more than it returned. Rather than trust my own reaction, I interviewed nine people from the target audience.
The complaints clustered: a flow that felt heavier than the payoff justified. I stopped guessing and documented every friction point users hit as they moved through it. That list became my brief.
Instead of handing over a static mockup and waiting, I designed the app and then rebuilt it as a functioning one — not a mockup pretending to work, but something I could put in a hand and watch get used.
That changed my feedback loop entirely. People stopped imagining how a flow would feel and started tapping through it — failing and succeeding at the exact friction points I'd catalogued.
I re-interviewed, redesigned, re-interviewed and redesigned again — two complete cycles, each grounded in watching real behaviour rather than my own taste. The capture flow got simpler; the recall surface got tuned until reviewing felt lighter than the reading it came from.
The final design wasn't my first idea. It was what was left after the weak ones got tested out.
The design file stayed the source of truth and I stayed the design authority — AI was just a faster brush. The real job was noticing a genuine pain, proving the demand behind it, refusing a tool that didn't deserve its users, and iterating against real reactions until the product fit. That's the same loop I run on client work — and the one I'd bring to your team.
T Vastra makes embroidered, oversized tees and sells them through Instagram. They wanted a black, premium online store with good type and micro-animations on the product cards. I directed and designed it, then built it as a working store with AI as the brush: Claude Code for the build, OpenAI Codex as an independent reviewer. The venom idea, the critique and every keep-or-cut call were mine.
The ask was a black, premium store with good fonts and micro-animations on the shopping cards, built on placeholder data so the real catalogue could drop in later.
One constraint shaped everything: the client didn't like their own logo's colours, so the palette couldn't come from it. I built it from the product instead: near-black, a warm bone white, and a single red taken from the thread already in their spider designs.
Most stores just replace the photo when you pick a colour. I wanted the change itself to feel like the brand, so I designed what I called the venom effect: a black, tendril-edged layer bleeds out across the shirt, the new colour chases it, and the embroidery re-threads itself halfway through.
That decided how it was built. Photos can't do this, so every tee is drawn as live SVG: the colour is its own layer and the tendrils come from a noise-distorted mask. Twelve designs, sixteen colourways, one renderer. Anyone who has reduced motion turned on gets an instant swap instead.
The product card is where people decide, so every action has its own feedback. The colour name slides to the new one, Front / Back flips the shirt in 3D, and Add to bag runs a spinner into a hand-drawn check while a dot in the shirt's colour flies into the bag and the bag icon bounces. The heart bursts when you save a tee.
The error state is designed too. Tap Add without a size and the sizes shake while the button itself turns red and says "Pick a size first". That version exists because the first one, a floating label, overlapped the colour swatches. I caught it while taking these screenshots and fixed it before publishing.
After the first build I judged parts of it generic, with too many familiar moves. So I explored a quieter, logo-led direction: a Roman serif matched to the wordmark, square corners, no intro, a centred hero.
Side by side, the bold original sold the product better; the quiet version made the tees feel smaller. I rolled it back but kept what the second pass got right: the client's logo, cut cleanly out of the flat JPG they sent, now in the nav, the intro and the footer and stitched onto a tee in thread colour, plus the emblem as a faint backdrop behind the hero shirt.
It works end to end: the bag survives a page reload, quantities update with a running subtotal, and a bar fills toward free shipping. Before handing it over I put the code through an independent review by a second AI system (OpenAI Codex) and scripted real-browser tests. The first review found four issues and the second found four more. All eight are fixed and the final review came back clean.
Honesty was part of QA too. The placeholder reviews are labelled as samples, and product specs I couldn't verify are flagged for the client to confirm before launch. A demo that pretends to be real is a liability, not a deliverable.
Found by Codex across two review rounds, fixed, then re-checked in a scripted Chrome session.
Tone Zone Fitness, a gym, needed two things from one app: members who can get in and pay without queueing at the desk, and an owner who can see who's inside, who's paid and who's waiting for approval without a notebook. I designed the dark Tone Zone design system and every screen on both sides, then built it in Flutter with AI as the brush.
The gym's flowchart split into two people: a member who needs a pass and a way to pay, and an owner who needs to check people in, approve new members and chase unpaid fees.
I made ₹0 running fees a design rule, not an afterthought. Login is email and Google, so there are no SMS costs or DLT registration. Payment is direct UPI to the gym's own QR, so there are no gateway fees. Cash payers aren't forgotten either: the owner can mark them paid in one tap.
Each member gets a signed QR pass that rotates every 30 days. When the owner scans it, a card slides up with the member's name, ID, payment status, validity and last visit, topped by one big answer: Allow entry or not.
A pass can be screenshotted, so the card is built for the owner to check the person against the name rather than pretending the QR alone is proof, with a slot for a member photo. The QR carries no personal data, just a reference the server signs.
There is no "admin" button for members to find. The owner's tools only appear when the owner logs in: approve or reject sign-ups, freeze a membership, record a cash payment, or let someone in on a trial with an override.
The dashboard answers the questions an owner actually asks at the end of the month: how much came in, how many have paid, and exactly who hasn't.
Three years as the only designer on paying client projects: I've owned every stage, kept to real deadlines and explained my decisions to the people paying for them.
Research, user flows, hi-fi UI, design systems and developer handoff. On 12 client projects I owned every stage, so I'm used to making design decisions and defending them, not waiting for a spec.
Every client project shipped on time against scopes and dates agreed up front. I break work into milestones, share progress early and flag risks before they become surprises.
I design around the return visit as much as the first: clear journeys, saved state and account pages people actually use. The same goes for my own work: 80% of my clients came back or referred me.
A B.Tech in AI & Data Science means I talk constraints with developers, prototype in working code when it helps, and hand off files a team can build without guessing.
I've spent three years working with clients online: written updates, recorded decisions, calls across schedules and handoffs that don't need me in the room. I'm just as happy joining a team on-site.
I'm an Indian citizen based in Hyderabad, open to relocating for a full-time role and available to start immediately. For roles outside India I'll need employer visa sponsorship.
What I'm looking for: a UI/UX or product design role on a team that ships, tests with real users and sweats the details.
I don't design a screen until I can name the specific friction it removes. If I can't, it doesn't earn its place in the build.
My taste is a hypothesis, not a verdict. I put flows in front of real users early and let what they do — not what they say — settle the argument.
An engineering background means I think in constraints. I'd rather ship a feasible v1 this sprint than a perfect v3 that never leaves the file.
I hand off annotated Figma files and specs, and when it helps I prototype in working code with AI-assisted tools, so developers can see exactly how an interaction should feel before they build it.
I'm a UI/UX and product designer looking for a full-time role. I took my first paid project in 2023 and have freelanced alongside my B.Tech ever since. For three years I've been the only designer on every project, which means the whole job: research and user flows, hi-fi UI in Figma, marketing creatives, and the design system that keeps all of it consistent.
That range shipped twelve client projects — SaaS dashboards, e-commerce flows, marketing sites — plus Daily Recall, my own app, taken from nine user interviews through two iteration cycles to a working, user-tested build, and Tone Zone Fitness, a client's gym app designed and built for iOS and Android.
My technical foundation is a B.Tech in Artificial Intelligence & Data Science. It isn't a costume — it's why I'm comfortable in the messy middle where design meets what's actually buildable, and why I design for how real users browse: on budget phones, on patchy connections, in a hurry.
What I'd bring to your team: end-to-end ownership, research-backed decisions and work that ships on time.
I reply within a day. Send me the role and a little about your team, and I'll come back with whatever helps: my résumé, a live walkthrough of a case study, or times for a call.
My résumé. One page, with the 12 client projects, the three case studies above, my B.Tech and certifications, including the Google UX Design Professional Certificate. Download the PDF.