UX/UI Design (Web App)

In scope. This service designs a web application of up to 15 screens with a UI kit — ideal for an MVP, an internal tool or one module of a larger system. Product Design is the full cycle: 30 screens, a complete design system and a month of support. If you are unsure which format fits, we will work it out at the brief and tell you honestly.

A website convinces a visitor and leads to an enquiry; an application is a tool people work in every day. The priorities differ: speed of action beats visual impact, information density is higher, and interface states — errors, empty lists, loading — matter as much as a “beautiful” screen.

Up to 15 unique screens. A screen is a distinct view of the interface: a dashboard, a list of records, a record card, settings. Modals and panels inside a screen are not counted separately. For a bigger application, screens are added in blocks of 5.

Yes, and that is a matter of principle: every screen is designed with its working states — loading, error, empty list, restricted access. Missing states are the most common reason a “finished” design stalls development in its first week.

An understanding of what the application should do and who works in it. The ideal input is a prototype, a technical specification or a defined MVP scope; without them we fix the flows at the brief. Access to the current system or its analogues also helps.

Yes, that is a common task: redesigning one module, adding a new section, or tidying an interface that grew chaotically. We work within the existing logic and styling or lay down new ones — it depends on the state of the product, and we settle it at the brief.

A UI kit is its lighter version: components, styles and rules sufficient for consistent development at this scale. A full design system with documentation and tokens is for large products with several teams — it comes with Product Design.

Web applications are designed desktop-first — that is how they are used. Responsive behaviour of the key screens is built into the UI kit; full mobile layouts for every screen are scoped separately at the brief if needed.

The Figma file is structured for dev mode: specifications, spacing and styles read without extra documents. For 14 days after delivery we answer the teams questions and check the built screens against the layouts.

Two rounds per stage within 7 days of its delivery. A round is one consolidated list of comments that we work through in full. An extra cycle costs $300 and adds 3 business days.