UI / UX Design
Research, wireframes, design systems, and motion polish.
Design that earns its place in the build, not bolted on after the code is written. User research and journey maps, wireframes through interactive Figma prototypes, a real component-token design system, accessibility-aware visuals, and the motion / microinteraction layer that makes the product feel alive.
What you get
4 pillarsResearch + flows
User interviews, journey maps, problem framing before pixels. Spend cycles on the right screens, not all the screens.
Design system
Token-driven component library tuned to Tailwind + Radix / shadcn so what designers ship lines up 1:1 with what engineers build.
Accessibility-aware visuals
WCAG 2.2 AA reviewed at the design layer — colour contrast, focus order, target sizes, alt-text strategy. Not "we'll do it later".
Motion + microinteractions
Framer Motion / GSAP polish, microinteractions, empty + loading + error states designed, not improvised.
Tools we reach for
Not exhaustiveMore in Web App Development
Core overview →E-commerce
Headless commerce, multi-brand, custom configurators.
Custom Web Applications
SaaS dashboards, portals, kiosks — multi-tenant and role-aware.
Static + Basic Sites
Marketing, landing, brochure, MDX — fast, accessible, SEO-clean.
API Design + Backend Architecture
REST, GraphQL, tRPC — versioned, observable, integration-ready.
Database Architecture
Postgres-first. Migrations, RLS, pgvector, multi-tenant isolation.
Performance + Platform Engineering
Core Web Vitals, edge rendering, caching, observability.
WordPress & WooCommerce
WP sites, WooCommerce stores, custom themes, plugins, headless.
QA + Testing
End-to-end, integration, visual regression, and performance gates.
Security Audit
OWASP review, auth + RLS audit, dependency CVEs, and a light pentest.
Frequently asked
4 questionsDo you build custom design systems?
Yes — design tokens, component library, documentation, and Figma-to-code parity. Built on Tailwind + Radix UI primitives + shadcn/ui patterns so your team gets accessible, themeable components without reinventing every input.
Is accessibility (WCAG 2.2) included?
Yes — WCAG 2.2 AA is the baseline, not a checkbox. Keyboard navigation, screen reader testing, color contrast, focus management, ARIA semantics. Especially important for US clients with ADA exposure on consumer-facing apps.
How does Figma handoff work?
Designs ship as Figma files with tokens, components, and prototype flows. Implementation tracks the design 1:1 with named tokens, not magic numbers. Discrepancies surface in code review against the Figma source of truth.
Mobile-first design?
Yes — designed mobile-first, scaled up to desktop. Touch targets, viewport handling, safe areas, and gestures considered from the start. Performance budgets enforced because slow phones are the median user, not the exception.
Sounds like the bucket you’re in?
Tell me what you’re trying to build. I’ll send a written proposal within 48 hours of our discovery call.