Why designers build website layouts in Figma
Figma runs in the browser and as a desktop app, and every file is shared by link. You don't install anything or pass archives around in Telegram: open the link, scroll through the pages and leave a comment on the exact block you want changed. The designer, the marketer and the developer all look at the same version, which removes many arguments about what was agreed.
The second advantage is components. Buttons, product cards, forms and the site header are built once and reused on every page. If you decide to change the colour of the request button, it updates everywhere at once. On a site with a dozen pages that saves hours and prevents small inconsistencies.
What the work consists of
Good web design in Figma starts with structure, not with pretty pictures. First the team agrees which pages are needed and what action a visitor should take: call, message you on Telegram, place an order. Then a rough wireframe without colours or photos is drawn to test the logic of the screens.
Only after that does the visual layer appear. The work usually breaks down into clear stages:
- Page structure and a rough wireframe.
- A design system: fonts, colours, buttons, spacing.
- Desktop layouts for the home page and key pages.
- Adaptation for phones and often tablets.
- A clickable prototype to test user scenarios.
- Handoff to developers with sizes, states and graphics.
What to consider when designing for Uzbekistan
A large share of visitors arrive on a phone, coming from Instagram, Telegram channels, OLX or search. That is why the mobile layout should be drawn as the main version, not as a shrunken copy of the desktop one. The phone number and messenger button should be within reach, and the request form should be short.
Many sites run in both Russian and Uzbek, and the same sentence can have very different lengths in each. If a button is sized for a short Russian word, the Uzbek label may not fit. Ask your designer to test both languages with real copy rather than placeholders.
For online shops, payment through Click and Payme, the choice of delivery city and the product page deserve separate attention. Connections in the regions can be unstable, so heavy animation and oversized photos are worth discussing early: a beautiful layout is no help if the page takes forever to open.
What to check in a layout before development
Approving a layout on the basis of "I like it" or "I don't" is not enough. Ask questions from the business point of view:
- Can a visitor understand within seconds what you do and where to click?
- Is the request button visible on every phone screen?
- Are there real texts and photos instead of lorem ipsum?
- Are states drawn: form errors, an empty cart, a 404 page?
- Does the style match your brand book, logo and Instagram profile?
- Are the pages ready for future SEO: headings, FAQ blocks, contacts?
What drives the cost of web design
The price depends on scope and complexity, not on the software. The number of unique pages, whether a brand book already exists, the number of languages, the amount of interaction and the rounds of revisions all matter. A landing page and a catalogue with a personal account are tasks of different scale, so an honest contractor clarifies the brief first and names a figure afterwards.
Ask separately whether mobile adaptation and file preparation for developers are included. Those two items are where extra charges most often appear later.
Common mistakes
The first mistake is drawing a design before defining what the site is for. The layout is then judged on taste, not on whether it helps generate enquiries. The second is separating the designer from the developer: the layout looks impressive, but some decisions are hard or expensive to build. The third is leaving analytics out: without goals and counters you cannot tell which version of a page performs better.
If you want a site where design, development and analytics work as one process, the markdev team can review your task and suggest a suitable format. Tell us about your business and we will talk through where to start.
FAQ
Does the client need to know how to use Figma?
No. Opening the link in a browser and leaving comments on specific blocks is enough. You do not have to edit the layout yourself.
How is a Figma layout different from a finished website?
A layout is an image and a prototype: it shows the look and the user scenarios but has no working code, forms or integrations. The website is built from it during development.
Can I order only the design, without development?
Yes, but make sure the files are prepared for handoff, with components, states and a mobile version. Otherwise a lot will have to be redrawn during development.
How many revision rounds are usually needed?
It depends on how clear the brief is. The clearer the goal and the materials, the fewer revisions you need. Agree on the number of rounds before work starts.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.