UI / UX design

Screens your users get through without effort

We test the solution with research, user flows and a clickable prototype before any code is written. Web, mobile and panel screens are designed with WCAG 2.2 AA in mind.

  • Non-binding
  • Mobile first
  • Design and code, one team
  • 1 business dayto hear back on your quote
  • WCAG 2.2 AAcriteria considered from the first draft
  • 44 pxminimum touch target
  • 4.5:1minimum target contrast for body text
Why UI / UX?

A hard-to-use screen loses customers

Visitors leave when they cannot find what they need or get stuck on a form. A good interface lets them complete the step that matters to you without effort.

Design based on assumptions compared with design based on research and prototypes
Designing on assumptions With ADK YazılımResearch and prototypes
Decisions Guesswork and personal taste Interview, analytics and test data
Changes After coding, and costly In the prototype, quick and economical
Screens Only the ideal state Empty, loading, error and success states
Consistency Different buttons and forms on each screen A documented design system
Accessibility An afterthought Considered from the first wireframe

Not every project needs every research method. We choose together the ones that will tell us the most for your project’s stage and budget.

  • Grounded in research

    We find problems through interviews, analytics and usability tests, and base design decisions on what we learn.

  • Tested before coding

    Your team and real users try a clickable Figma prototype before a single line of code is written.

  • Design that can be built

    Designers and developers work together, so the screen you approve keeps its intent during development.

What we design

From research to developer handoff

For websites, iOS and Android apps, admin panels and CRM screens.

  • Stakeholder and user interviews, UX audit
  • Information architecture, sitemap and user flows
  • Wireframes and a clickable Figma prototype
  • Interface design for phone, tablet and desktop
  • Design system and component library
  • Form, checkout and onboarding flows
  • Layouts ready for many languages and right-to-left
  • Developer handoff with specs and accessibility notes
How we work

Approved screens in four steps

  1. 01

    Goals and scope

    We listen to your goals and users, then set out screens, stages and feedback rounds in the proposal.

  2. 02

    Structure and flows

    We map the page structure and key flows, then agree layout and content priority with you through wireframes.

  3. 03

    Prototype and testing

    We try the clickable prototype with you and, where possible, with real users, and refine it based on the findings.

  4. 04

    Design and handoff

    We turn the approved structure into screens and components, prepare the handoff pack and check the build.

FAQ

Questions you may have

Can’t find what you’re looking for? Our team will be happy to help.

Ask us
What is the difference between UI and UX?

UX (user experience) covers the route someone takes through a product and how that feels, including flows, information architecture and usability. UI (user interface) is the visual design of the screens. For a good result, the two are handled together.

Can you redesign our existing website or app?

Yes. We first review your current product through heuristic evaluation and analytics to find where users struggle. Based on those findings, we decide with you whether a full redesign or step-by-step improvement makes more sense.

Why is a prototype stage necessary?

A prototype lets you see whether the journeys actually work before development begins. Changes made at this stage are far quicker and cheaper than changes made once the code has been written.

Are your designs WCAG 2.2 AA compliant?

We design with the WCAG 2.2 AA success criteria in mind: colour contrast, keyboard use, visible focus, alt text, form labels and target sizes are considered from the first stage. Full conformance also depends on the code and content, and we do not issue accessibility certificates.

How are we involved in the design process?

We share the work with you at each stage, from goals and wireframes to the prototype and visual design, and move on once you approve. The number and format of feedback rounds are set out in writing in the proposal.

Do you design mobile apps and admin panels too?

Yes. Alongside websites, we design iOS and Android apps as well as data-heavy admin panels and CRM screens. We build a shared design language while respecting the conventions of each platform.

How do you measure the results of a design?

We tie design goals to measurable steps such as completed forms, sign-ups or purchases. After launch we track those steps with Google Analytics 4 and behaviour analytics tools and recommend improvements based on the data.

How are the cost and timeline of UI / UX design worked out?

Both depend on the number of screens, the platforms involved, the complexity of the flows, the scope of research and testing, and the breadth of the design system. After an introductory call and initial analysis, we set out both in a written proposal.

Tell us about your project and get a design quote

A few sentences about what you want designed are enough. We will review your needs and send you the scope, timeline and price in writing.

  • Reply within 1 business day
  • Free and non-binding
  • Your details stay confidential

Reply within 1 business day

Get a quick quote

Fill in the form and we will get back to you shortly.

UI / UX Design

Your details stay confidential · Free and non-binding

Full design scope and detailsResearch methods, accessibility criteria, tools, deliverables and process.

UI / UX design shapes both how a website, mobile app or admin panel looks and how it is used. UX (user experience) is about the route people take to reach their goal and how much effort it costs them. UI (user interface) is about how that route appears on screen. Good interface design helps visitors find what they need quickly and complete the step that matters to you, whether that is filling in a form, making a purchase or booking an appointment, without friction.

At ADK Yazılım, our UI / UX design services start with research rather than assumptions. We find the problems through stakeholder and user interviews, analytics and usability testing, then test the solution with information architecture, user flows, wireframes and interactive prototypes before any code is written. The approved structure becomes a visual design that fits your brand and a reusable design system.

Because the people who design and the people who build work in the same team, screens are prepared from the start to be practical to implement, fast and accessible. The result is clean, consistent interfaces that work comfortably on a phone and are designed with the WCAG 2.2 AA success criteria in mind.

Who are our UI / UX design services for?

  • Teams building a new digital product: Start-ups and companies that want to test a web or app idea with users on a prototype before investing in development.
  • Sites that lose visitors: Corporate websites and online shops that have traffic but lose people at the enquiry form, sign-up or checkout.
  • Complex admin panels: Businesses whose staff struggle with CRM, ERP or internal screens that need long training and invite mistakes.
  • Organisations refreshing their brand: Firms with a new corporate identity that want a consistent look across web, mobile and dashboard screens.
  • Growing product teams: Teams that need a design system so that different designers and developers speak the same language.
  • Organisations that take accessibility seriously: Institutions that want to offer an equal experience to people with visual, motor or cognitive differences.

What do our UI / UX design services include?

Research and discovery

We start by understanding your business goals, your users and the problems you face today. Interviews, analytics, customer feedback and support tickets show us what people do, on which devices and for what purpose. From this we draw up personas and usage scenarios, and base design decisions on them.

Information architecture

We organise navigation, page hierarchy, content groups and labelling in the order users expect. Where useful, a card sorting exercise shows us how people group content in their own minds. The output is a sitemap that shows where every page sits and how pages connect.

User flows

We map critical journeys such as sign-up, purchase, booking or requesting a quote step by step. For each step we define what the user sees, which decision they make and what happens when something goes wrong. Unnecessary steps and unclear decision points are removed at this stage.

Wireframes

Before colour and imagery, we settle layout and content priority with greyscale drafts. Wireframes make it easy to discuss what goes where on the screen and which information should be read first. Changes made at this stage are quick and inexpensive.

Interactive prototypes

We build clickable prototypes in Figma. Your team and real users can try the journey on a phone or computer without a single line of code being written. A prototype speeds up decisions and gives everyone the same screen to talk about.

Visual interface design

Approved flows become on-brand screens with consistent typography, colour, spacing and icons. Empty, loading, error and success states, along with small transitions that serve a purpose, are part of the design. We prepare layouts considered separately for desktop, tablet and phone.

Design systems and component libraries

We define colour, type, spacing and corner values as design tokens. Components such as buttons, form fields, cards, tables, tabs and notifications are documented with all their states and usage rules. New screens can then be produced faster and in the same visual language.

Developer handoff

We pass screens to the development team with measurements, spacing, states and interaction notes. Images are exported as SVG and WebP, and accessibility notes are included. During development we compare the built screens with the design, log any differences and follow them through until they are fixed.

Which UX research methods do we use?

Not every project needs every method. We choose together the ones that will tell us the most for the project’s stage and budget.

MethodWhen it is usedWhat we learn
Stakeholder interviewsAt the start of the projectBusiness goals, constraints, success measures and internal processes
User interviewsFor new products and major redesignsUsers’ needs, habits, the words they use and the problems they run into
Analytics reviewWhen a site or app already existsWhere users come from, which devices they use and at which step they leave
Heatmaps and session recordingsOn pages that look problematic in analyticsClick and scroll behaviour, repeated clicks and areas where people get stuck
Heuristic evaluationWhen a quick UX audit is neededScreens that break established usability principles, and inconsistencies
Usability testingAt prototype stage and before launchWhether users can complete real tasks, and where and why they get stuck

Findings become an improvement list ranked by how many users are affected and the impact on your business. In session recording tools we mask form fields and personal data, and we take account of the transparency and consent requirements of UK GDPR, EU GDPR and KVKK.

Accessible design: how do we apply WCAG 2.2 AA?

Accessibility is not a check bolted on at the end; it is a design principle we follow from the first wireframe. We apply the WCAG 2.2 AA success criteria in these areas:

  • Colour contrast: We aim for at least 4.5:1 for normal text and at least 3:1 for large text and interface components, and we never rely on colour alone to convey information.
  • Keyboard use: Menus, forms, dialogs and every interactive element can be used without a mouse, in a logical order.
  • Visible focus: Keyboard focus is clearly visible on every element, and sticky headers or cookie banners never hide the focused item.
  • Alt text: We write descriptive alternative text for meaningful images and hide decorative ones from screen readers.
  • Form labels and errors: Every field has a visible label, and error messages explain in words what went wrong and how to fix it.
  • Target size: We meet the WCAG 2.2 minimum target size criterion, and as our own standard we design touch targets at 44 pixels or larger.
  • Dragging and motion: We offer a single-tap alternative to drag-and-drop and respect the device’s reduced motion setting.
  • No redundant entry, easier sign-in: We do not ask for the same information twice in a journey, and we never block pasting or password managers in password fields.

Worth knowing: An accessible design is the first step; full conformance comes from the design, the code and the content together. That is why we hand our accessibility notes to the development team and check them before launch. We do not issue accessibility certificates or formal conformance statements.

Mobile-first, conversion-focused interface design

Mobile first

We design screens for the phone first, then expand them for tablet and desktop. A small screen makes it obvious which information is truly needed. Primary actions sit within easy reach of the thumb, and text stays readable without zooming.

Forms

We ask only for the fields that are needed and group them logically. The right keyboard type, autofill, inline validation and clear error messages make forms easier to complete. Required and optional fields are clearly marked.

Checkout

Guest checkout, a progress indicator, a total that shows delivery and taxes up front, and well-placed express options such as Apple Pay and Google Pay all help reduce basket abandonment. Reassuring information sits close to the payment button.

Onboarding

We want new users to see the value of your app within their first few minutes. Instead of long intro carousels, we use contextual hints, step-by-step set-up and meaningful empty states. Permission requests, such as notifications or location, are asked at the moment they are needed and with a reason.

Which design and analytics tools do we use?

Tool names describe our working capabilities and do not imply a partnership or official endorsement from the companies concerned. Analytics tools run in your own accounts, with the access you choose to grant.

Design, prototyping and testing

We create screens, the component library and prototypes in one place, and run workshops and remote usability tests with these tools.

  • Figma
  • FigJam
  • Figma Dev Mode
  • Maze

Behaviour and analytics

These tools show us how people move through a page, where they get stuck and at which step they leave.

  • Hotjar
  • Microsoft Clarity
  • Google Analytics 4
  • Google Tag Manager

Our design principles and quality standards

  • Simplicity: Every screen has one main purpose; distracting decoration and crowded layouts are removed.
  • Consistency: The same action looks and behaves the same everywhere, so users never have to relearn it on another screen.
  • Every state designed: Not just the ideal screen, but empty, loading, error, success and no-permission states as well.
  • Performance: Visual choices take page speed into account; lightweight solutions are preferred over heavy images and animation.
  • Multilingual layouts: Layouts adapt to text of different lengths and to right-to-left languages such as Arabic and Persian.
  • Measurability: Design goals are tied to concrete steps such as completed forms, sign-ups or purchases, and tracked after launch.

What do you receive from a UI / UX design project?

  • Research report: Interview, analytics and testing findings with prioritised recommendations.
  • Information architecture: Sitemap, navigation structure and content groups.
  • User flows: Step-by-step diagrams of critical tasks.
  • Wireframes: Layout drafts for the key screens.
  • Interactive prototype: A shareable, clickable Figma prototype.
  • Interface designs: Approved screens and state screens for phone, tablet and desktop.
  • Design system: Design tokens, components and usage guidelines.
  • Developer handoff pack: Measurements, interaction and accessibility notes, plus SVG and WebP assets.

The extent to which Figma files and prototypes are shared with you is set out in writing in the proposal.

How does the UI / UX design process work?

  1. Introduction and goals: We listen to your business goals, audience and current problems, and agree how success will be measured.
  2. Research and scope: We review users, data and content, and confirm the screens, stages and feedback rounds in the proposal.
  3. Information architecture and flows: We map the page structure and critical journeys and agree them with you.
  4. Wireframes and prototype: We settle the layout in drafts, then test the clickable prototype with you and, where possible, with real users.
  5. Visual design and design system: We turn the approved structure into detailed screens and reusable components.
  6. Handoff and build review: We prepare the handoff pack and check during development that the design is implemented correctly.
  7. Post-launch improvement: We follow user behaviour in the data and recommend improvements.

How is UI / UX design priced?

  • Number of screens and templates: How many unique screens and states need designing.
  • Platforms: Whether the work covers web only, or iOS, Android and an admin panel as well.
  • Flow complexity: The number of user roles, business rules and decision points.
  • Research and testing scope: The number of interviews and test sessions, and participant recruitment.
  • Design system scope: Whether a core component set is enough or a fully documented library is needed.
  • Languages and brand: The number of languages, any right-to-left requirement and whether a brand identity already exists.

Timeline and price are confirmed in a written proposal after an introductory call and initial analysis.

Why choose ADK Yazılım for UI / UX design?

Design and development in one team

The people who design the interface work alongside those who build it. Design decisions are made with technical constraints in view, so the screen you approve keeps its intent all the way through development.

User-centred and accessible

Clean, accessible and fast interfaces sit at the heart of our values. In every project we put ease of use and clarity ahead of showiness.

Multilingual interface experience

Our platforms support 19 languages, so we design interfaces that cope with text of different lengths and with right-to-left scripts.

  • Stakeholder and user interviews, analytics review and UX audits
  • Information architecture, sitemaps and user flows
  • Wireframes and clickable interactive prototypes in Figma
  • Accessible interface design following WCAG 2.2 AA criteria
  • Interface design for websites, mobile apps and admin panels
  • Design systems, design tokens and component libraries
  • Mobile-first layouts that adapt to every screen size
  • Usability testing with a prioritised improvement list
  • Quick UX audits through heuristic evaluation
  • Conversion-focused design for forms, checkout and onboarding
  • Empty, loading, error and success state design
  • Multilingual interfaces that support right-to-left languages
  • Developer handoff with measurements, states and accessibility notes
  • Design review during development to check correct implementation