UI / UX design
UI and UX design your engineers can actually build
Research, user flows, wireframes and Figma design systems, made by designers who sit next to the developers, so what gets designed is what gets shipped.
Pretty screens are not a product
Design that stops at a slide deck creates work twice: once to admire it, once to figure out how it behaves on a phone, in Persian, with an empty state, or with a name forty characters long.
We design as part of the engineering team. Every screen has its states, its responsive behaviour and its right-to-left version. Components live in a Figma library that maps one to one onto code, and we review the build against the design until launch.
Who it's for
A good fit when
- You are launching a SaaS, a marketplace, an app or a customer portal and want it to feel effortless.
- Your product works, but users get lost, support tickets repeat, and conversion is lower than it should be.
- You need a brand and a visual identity that carry through the product, the website and the marketing.
Deliverables
What we deliver
User research and journey maps
Interviews, analytics review and competitor teardown, turned into the flows people actually take.
Wireframes and prototypes
Low-fidelity flows to agree the structure, then high-fidelity clickable prototypes in Figma to test before anything is coded.
Design systems in Figma
Tokens, components, variants and documentation that map to the codebase, so new screens stay consistent.
Brand and visual identity
Logo, colour, typography and voice, applied to the product, the website and social from one guide.
Multilingual and right-to-left design
Persian and Arabic layouts designed properly, with mirrored flows and typography that reads well, not a flipped English screen.
Design QA during the build
We review every implemented screen and fix the gaps with the developers, so the shipped product matches the design.
Process
How a design project runs
Figma
Nuxt
Vue
Tailwind- 01
Discover
Goals, users, constraints and existing data. A short document everyone agrees on before drawing anything.
- 02
Structure
Information architecture, user flows and wireframes, reviewed with you and with the engineers who will build them.
- 03
Design
The visual language, then high-fidelity screens for every state, in the Figma library the team will keep using.
- 04
Build together
Hand-off is a conversation, not a file drop. We stay in the build, answer questions and QA the result.
FAQ
Questions we hear
Either. Many clients bring us for design alone and build with their own developers; we hand over a documented Figma library. When we also build, the design and the code are made by the same team, which removes most hand-off problems.
A focused marketing site takes two to three weeks. A SaaS or marketplace with research, flows and a design system usually takes six to ten weeks, running in parallel with backend development.
Yes. We start with a UX audit of the current product and your analytics, prioritize the flows that lose users, and redesign in stages so the product keeps shipping.
Yes, natively. Our designers work in these languages daily: right-to-left grids, mirrored navigation, Persian and Arabic type pairing and numerals are part of the base design, not an afterthought.
A Figma file with the component library, every screen and state, a prototype, exported assets and a short design guide. Plus design QA if we build it.
Want a product people find easy?
Send us what you have: a brief, an app, a sketch. We will come back with a scope and the first steps.