Service
UI/UX Product Design
Product design is not a set of attractive screens. It is deciding what a user is trying to complete, how many steps that honestly needs, what belongs on each screen, and what the interface does when things go wrong. I design websites, platforms, dashboards, booking systems, SaaS products and learning platforms in Figma, as a system a developer can build from without guessing. And because I also build front-end in React and Next.js, nothing I hand over is unbuildable in practice.
Who this is for
- Platforms and service products where the journey, not the visual style, is the unsolved problem
- Dashboards, admin panels and internal tools with data-heavy screens that need a real hierarchy
- Booking and reservation systems where steps, pricing clarity and availability drive the whole experience
- SaaS products that need an interface users understand without training
- Learning platforms with course, lesson, progress and enrolment states to design properly
- Teams with their own developers who need a professional, complete design to build from
What the engagement includes
- Discovery: users, goals, constraints, existing systems, and what the product must not break
- User flows: the screens that exist and the exact order users move through them
- Sitemap and information architecture, agreed before any visual design begins
- Wireframes that solve structure and hierarchy while changes are still cheap
- Responsive interface design for the breakpoints the product actually needs
- A design system: components, typography, spacing, and consistent interaction patterns
- Empty, loading, error and success states, designed rather than left to the developer
- Developer handoff: an organized Figma file with the annotation a build actually requires
The states most design files never include
A design that only shows the happy path is half a design. Real products spend a lot of their life in other states: a dashboard with no data yet, a search with no results, a booking that failed at payment, a slow API, a form rejected by validation, a success screen that has to tell the user what happens next. These are the moments where users decide whether a product is trustworthy, and they are the ones handed over undesigned most often. They are part of the standard scope here, not an extra.
Designed by someone who also builds the front-end
The usual failure in a design-only project is not an ugly file, it is a beautiful file that loses spacing, states and detail as a developer reinterprets it, or that turns out to be impractical once real content arrives. Because I build production front-end in React and Next.js, I design within what can be built, annotate the parts that need explanation, and can take the same design through to a live product with no handoff at all.
Multilingual products are designed in both directions
If the product serves Arabic and English users, both directions are designed, not one mirrored. Direction affects navigation order, icon meaning, form and input behaviour, number and date handling, typography, and line height. Designing RTL properly at this stage costs a fraction of what retrofitting it costs after the front-end exists.
How to start
Describe the product and the main journey users need to complete. You get an honest read on scope, whether design alone is enough or design plus front-end makes more sense, and a starting range.
Frequently asked questions
How much does UI/UX product design cost?
Product design engagements typically start from $1,500. The final scope depends on the number of user journeys, screens and states, whether a design system is being created from scratch, and how many languages the product supports. Confirmed in writing after discovery.
What do I receive at the end?
An organized Figma file containing the user flows, information architecture, wireframes, final responsive interface designs, a component-based design system, and the empty, loading, error and success states, prepared for developer handoff. You own the file.
Can you also build what you design?
Yes. Many projects continue directly into front-end implementation with React or Next.js, which removes handoff loss entirely. That combined path is the Design-to-Launch engagement.
Do you work with our existing developers?
Yes. The handoff is prepared for a team that is not me: organized layers, named components, documented states, and annotation where behaviour is not obvious from the visuals.
Do I need product design, or just a website?
If you need a straightforward service website, the interface design is part of that build rather than a separate engagement. A dedicated product design engagement makes sense when the product itself is unsolved: platforms, dashboards, booking systems, SaaS and learning products, where starting development first means redesigning mid-build.
Which design tool do you use?
Figma, for everything: flows, wireframes, interface design, components, design systems and prototypes. You get full access to the file and own it.
Have a product whose journey is not solved yet?
Describe the product and the main thing users need to complete. You get a scope, an engagement type, and a starting range.