User research
Short online interviews with the people who will use the product and, where possible, watching their current workflow over screen share. The output is a brief findings note built on observation rather than assumption.
Service · Websites and web applications
UI/UX design
A screen can be attractive and still fail at its job. Picture a Konya maker of agricultural machinery commissioning a fault-reporting app for service technicians at its dealers. The design looks sleek on a desktop monitor and becomes unusable on a tablet held in gloved hands in a sunny field: tiny buttons, weak contrast, six screens to reach the serial number field. Every one of those issues would have surfaced in a half-hour test with two technicians before a line of code was written. UI/UX design turns that test, and the questions before it, into a method. Who will use this, where, under what conditions, and to finish which task?
User interviews
held with real users before design starts
Figma prototype
clickable with no code written
Five-person test rounds
enough to uncover most problems
Design system
colour, type and components in one source
What the work covers in practice
Design does not stop at screens. Everything is documented so developers never have to make the same decisions twice.
User flows
The five to ten most important tasks mapped step by step: sign-up, ordering, fault reporting, approval. Unnecessary steps are cut here, before any screen is drawn.
Clickable prototype
Built in Figma with real content at real screen sizes, and testable on a phone. Genuine product names and figures replace lorem ipsum.
Usability testing
Remote sessions with five users, each asked to complete a task while we note where they get stuck. Findings are prioritised and fed back into the prototype.
Accessibility
Contrast, touch target size, keyboard use and screen reader labels are checked against WCAG 2.1 AA while still in design.
Design system and handover
A component library covering colour, typography, spacing, buttons, form elements and error messages. Developers read measurements and states directly from Figma.
How we approach the job, from first call to handover
We test early and in small rounds. A flaw found in a prototype costs an hour; the same flaw found in a live product costs weeks.
01
Discovery
A workshop on business goals, user groups and the current system, then five or six user interviews. This phase generally takes one to two weeks.
02
Flows and sketches
Flows for the core tasks and low-fidelity screen sketches. Colour and imagery are left aside; only order and content are discussed.
03
Prototype and test
A high-fidelity prototype is built, tested with five users and revised. A second round follows if needed.
04
Design system and build support
The component library is finalised and handed to the development team. During development we answer questions and compare the built screens with the design.
A test with five users tells you more than a meeting of fifty people. In a meeting, everyone judges the screen through their own habits, and the most senior opinion tends to win. In a test, a real user attempts a real task, and the point where they stumble leaves little room for debate. When a design disagreement arises, we suggest settling it with a small test rather than an argument.
Frequently asked questions
Yes. Figma files, the component library and flow documents are delivered so your developers can use them directly. Advice and design review during development can continue on an hourly basis.
In most B2B projects the users are your customers, dealers or staff, and reaching a few of them is easy. For consumer products we agree on suitable participants together. Everyone gives explicit consent, and recordings are stored and deleted in line with KVKK.
Yes, usually starting with a usability review of the current product. Most problems come from surplus steps in the flows rather than the visual style, so we suggest fixing those first and the look afterwards.
No. We focus on screen and interaction design. If you have no brand identity yet, we suggest working with a branding agency and then adapt their output to the digital product.
Neighbouring services that often go with this one
Service
WordPress websites
Your own block theme, a lean set of extensions, licences owned by the business
Service
Shopify, ikas and other platforms
ikas, IdeaSoft, T-Soft, Ticimax, Shopify or WooCommerce, picked on evidence
Service
Brochure site and product catalogue
A compact site with a catalogue that collects quote requests instead of payments
Service
Corporate website
Clear, separate paths for customers, candidates, suppliers and journalists
Tell us about the product
Explain what the product does, who uses it and what stage it has reached. Within one working day we propose a discovery session.
Availability
Weekdays 09:00-18:00 Turkey time (GMT+3); an answer follows by the next working day
Weekdays 09:00-18:00 Turkey time (GMT+3); an answer follows by the next working day
Calls
By video, over Microsoft Teams or Google Meet
By video, over Microsoft Teams or Google Meet
We have your enquiry
A reply will reach you by the next working day at the latest. If your message says work has come to a halt, it goes to the top of the pile.
- Filling the gaps. If we need more information to judge the job, we send questions by email or propose a quick Teams or Google Meet call.
- A written quote. It lists the scope, a euro price excluding VAT and a realistic start date. No hidden clauses, no items that appear later.
- Your decision. The quote arrives by email. Take whatever time you need, raise questions on any line, and decide when you are ready.