UI/UX Design
UI/UX Design
We do not treat UI as decoration or UX as a persona document. User tasks, business objectives, information architecture, interaction states and development constraints need to resolve inside one product system.
Search Intent
Quick Answer
UI/UX design turns user needs and business goals into task flows, information architecture, interactions, visual hierarchy and reusable component systems.
What is this service?
01UI/UX design turns user needs and business goals into task flows, information architecture, interactions, visual hierarchy and reusable component systems.
Who is it for?
02It suits teams building a new web/app product, facing usability or drop-off issues, or consolidating fragmented interfaces into a design system.
What do we manage?
03Scope can include discovery, user/task research, IA, user flows, wireframes, prototypes, UI systems, responsive states, accessibility, usability testing, handoff and post-launch feedback.
Primary outcome
04The goal is not more screens, but a system that helps users complete tasks with less ambiguity, preserves brand character and remains implementable by development teams.
When Do You Need It?
The interface looks good but the next action is unclear
Visual polish without task hierarchy and next-step clarity creates aesthetics without usability.
Every feature creates a new pattern
Without component and interaction standards, growth creates consistency, QA and development debt.
Mobile is treated as a late shrink-down
Simply shrinking a desktop hierarchy can create touch-target, keyboard, navigation and content-priority problems.
UX decisions are driven by opinion
Without analytics, user feedback, usability or task-success evidence, stakeholder preference can replace user behavior.
Operational Scope
UI/UX quality is managed through research → task flow → information architecture → interaction states → system → validation.
Discovery & Task Research
Primary user jobs, friction, terminology and existing behavior are studied alongside product and business context.
Information Architecture
Content, navigation, hierarchy and object relationships are structured around the user's mental model.
Flows & Wireframes
Happy paths are designed alongside empty, error, loading, permission and exception states.
UI & Design System
Typography, spacing, components, tokens and interaction patterns are built into a reusable system.
Prototype & Usability
Critical tasks are tested through prototypes before or during high-fidelity work so major mistakes surface early.
Developer Handoff & QA
Responsive behavior, component states, specs and acceptance criteria are handed off to development, with post-build design QA where needed.
How We Work
Problem Framing
Business objective, user task and measurable success are aligned in one problem statement.
Structure Before Styling
High-fidelity styling does not begin before IA and flows are coherent.
Prototype & Validate
Risky interactions and critical journeys are validated through prototypes and feedback.
Systemize
Approved patterns are systemized into components, variants, tokens and content rules.
Build QA & Learn
Implementation is checked for visual/interaction parity and launch data informs the next iteration.
Relevant Experience
We show expertise through the operation's real decision logic, control points and working context—not generic claims.
Fizyohol, TIIB & Argeron
Sellf's portfolio contains web-interface design work for Fizyohol, Turkish International Investment Bank and Argeron, demonstrating real design practice without inventing operation-level performance claims.
States are first-class design
Loading, empty, error, validation and permission states are treated as product experience, not edge-case cleanup.
Design meets implementation
Handoff is more than a Figma link; responsive behavior, component states and development constraints are part of the design decision.
Before You Decide
Research first, or straight to UI?
It depends on risk and uncertainty. Strong existing evidence may justify lightweight research; uncertain products can create expensive rework if they jump straight to high-fidelity UI.
When do we need a design system?
A heavy system may be unnecessary for a small one-off page. It becomes valuable with multiple product surfaces, teams or repeated components.
Does UI/UX guarantee conversion gains?
No. We can improve usability and clarity, but conversion also depends on offer, demand, pricing, trust and technical performance. Material changes should be tested where feasible.
Frequently Asked Questions
Do you work in Figma?
Figma can be used for design, prototypes and component documentation; the key deliverable is implementation-ready specification rather than a specific file format.
Do you design mobile-app UX?
Yes. Native/mobile-web patterns, gestures, keyboards, permissions, offline/loading and device constraints can be designed according to scope.
Is accessibility considered?
Yes. Depending on scope, WCAG 2.2 is used as a reference for semantic hierarchy, contrast, keyboard/focus behavior, keeping focus visible and unobscured, touch targets, errors/validation and component states during design and handoff. This does not automatically imply formal accessibility certification; the target and testing scope are defined for the project.
Can you redesign an existing product?
Yes. Existing analytics, user feedback and task flows are reviewed first; working interactions are not changed simply for novelty.
Can Sellf also build the product?
Yes. UI/UX, web/app development and custom software can be delivered within one handoff and QA system.
Which states must be designed in UI/UX work?
The happy path is not enough. Loading, empty, error, validation, permission, disabled, success and responsive/keyboard states should be designed for critical flows; where accessibility is in scope, WCAG 2.2-oriented focus, target-size and semantic behavior also belong in acceptance criteria.
UI/UX Design
Clarify the task before polishing the interface.
Review the highest-impact UX issues across user flows, information architecture and component systems.