UX/UI Design for Websites and Apps

We design user-friendly interfaces: websites, online stores, personal accounts, and mobile apps. Design starts with structure and user scenarios, not with a color palette.

What's Involved in the Design Process

Analysis and Structure

We figure out who your users are and what they’re here to do. This forms the basis for the page structure and list of screens—even before anything is designed.

Prototype

Black-and-white wireframes: what goes where and in what order it’s read. At this stage, revisions cost nothing; after the design phase, they’re noticeably more expensive.

Visual component

A style tailored to your brand: typography, colors, grid, and button and form states. Separate desktop and mobile versions—responsive design isn’t just “the same thing, only narrower.”

UI kit and handoff

We're compiling the components into a library so that new pages are added in the same style. We send the mockups to Figma with all the layers—that way, any developer can work with them, not just us.

Redesign of the existing website

If a website already exists but isn’t working, we start with the data, not the design: we look at analytics, mobile user behavior, speed, and the path to a lead. Often, it turns out that the problem isn’t with the design—and we can save half the budget.

We've broken down the typical places where applications get lost in this article "Why Isn't the Website Generating Leads?".

Design that takes development into account

A beautiful layout that takes too long to load is a bad layout. We make it clear right from the start:

• the importance of graphics and image formats;
• text and buttons that are easy to read and easy to tap with a finger;
• states: hover, click, error, empty list, loading;
• contrast sufficient for reading in sunlight and for people with poor eyesight.

Forms of Cooperation

• Design + Development — full-cycle service; we take full responsibility for the result.
• Design Only — We’ll provide the mockups and UI kit; your team will handle the implementation.
• Further Work — individual screens or modules for an existing website, designed to match its style.

Timelines and Cost

The home page costs more than the internal pages: it sets the tone for the entire project. Beyond that, the price depends on the number of unique layouts. Calculate the project — three steps.

You can view the completed interfaces at portfolio.

How the Work Is Done

1. Initial briefing — 1–2 days

Business objectives, target audience, competitors, brand constraints. Here, we’ll also agree on some reference points: three to five examples, along with an explanation of exactly what you like about them.

2. Structure and Scenarios — 2–5 days

A list of screens and the user's path to the desired action. Without this step, design becomes nothing more than a collection of pretty pictures that don't come together to form a product.

3. Prototypes — 3–7 days

Black-and-white diagrams: block layout, hierarchy, draft texts. Let’s finalize everything right here—edits are the least expensive at this stage.

4. Visual Design — 1–3 weeks

The home page comes first, followed by the internal pages, with 1–2 days per layout. Two rounds of revisions are included in the price.

5. UI kit and handoff — 2–4 days

Component library, element states, grid, and typography. We’ll send you the Figma file with layers—any developer can work with it.

What You Get in the End

• mockups of the desktop and mobile versions of all approved screens;
• UI kit: buttons, forms, cards, states, icons, grid;
• a Figma source file with usage rights;
• developer specifications: indents, fonts, element behavior;
• Recommendations regarding the schedule and download speed.

When Design Doesn't Solve the Problem

We’re upfront about this right from the start during the briefing. If there are few submissions due to slow loading times, a broken form, or a lack of traffic—a redesign won’t help, and it’ll just be a waste of money. In such cases, we start by conducting an audit: we look at speed, the process for submitting a request and the technical condition of the website—and only then do we decide whether a redesign is necessary.

Questions and Answers

Let's discuss the project

Describe the project—let’s see what’s actually needed: a new design, a redesign, or an audit of the existing website first.