Layout coding versus full website development
A designer draws the mockup, usually in Figma. A front-end developer rebuilds it in HTML, CSS and a little JavaScript so it opens in a browser. This is the visible layer of a site: grid, fonts, spacing, animations and how everything adapts to different screens.
Everything behind the page, such as the admin panel, product database, user accounts, payment processing and Telegram or CRM integrations, is back-end programming. Sometimes the job ends with static pages, sometimes the layout is connected to a CMS. Write that boundary into the contract, otherwise each side assumes the other one understood.
What to prepare before the work starts
The quality of the finished pages depends heavily on the quality of the design file. If the designer drew only the homepage at desktop width, the developer has to invent the mobile menu, the error page and the button states. Those decisions are then argued over later.
- Mockups for every screen width you need, above all for phones
- A consistent style set: colors, fonts, heading sizes, buttons, form fields
- Element states: hover, pressed, form error, empty list
- Fonts that support Cyrillic and Uzbek Latin, including the o‘ and g‘ characters
- Final images and icons as files, not screenshots
- Copy in every site language, or at least realistic line lengths
Responsive layout for real devices in Uzbekistan
Most local websites get the bulk of their traffic from phones, arriving from Instagram, Telegram channels or Meta ads. Many people open links in an app's built-in browser rather than Chrome, where some effects behave differently. Test the site the way your customer will actually see it.
Speed matters too. Mobile internet outside the capital can be unstable, and many phones are not recent models. Heavy background video, dozens of uncompressed photos and unnecessary scripts turn a neat design into a page the visitor closes before it loads.
Languages are another factor. Uzbek words are often longer than their Russian or English equivalents, so a button that looks perfect in one language can break in another. Good design and good coding leave room for that from the start.
What drives the cost
The price of layout work depends less on the number of pages and more on the number of unique blocks and how complex their behavior is. Ten pages built from the same components cost less than three pages with custom animations, a calculator and complicated filters.
The main factors are the number of responsive states, the amount of animation, page speed requirements, CMS integration, multilingual support and revisions after the first handover. Ask for the estimate to be split along these lines. You will see what you are paying for and can cut extras without losing the point of the site.
How to accept the finished work
Compare the result with the design on real phones, not only in a desktop browser window. Open the site on different devices, on a slow connection, in both Russian and Uzbek.
Agree in advance what counts as a defect and what counts as a new request. A mismatch with the mockup is a fix. A new idea after the design was approved is separate work. That rule removes most disputes.
- Spacing, fonts and colors match the design
- Menu, forms, pop-ups and contact buttons work
- Layout holds on narrow screens and with larger system fonts
- The homepage loads quickly on a mobile connection
- Headings, descriptions and alt texts are in place for SEO
- Source files are handed over with notes on how to edit content
Common client mistakes
The first is approving a design with no phone version. The second is sending changes during coding: every new idea shifts the grid and forces rework in neighboring blocks. The third is delaying analytics. Without counters and goals you cannot tell whether the new site brings in leads.
The fourth is choosing a contractor on price alone. Cheap layout often means code that is hard to extend, and the site gets rewritten at the first serious update.
Where to start
Gather the design file, a list of pages and your wishes for functionality, then decide whether you need layout only or a complete website. If you are unsure, the markdev team can review how ready your design is, point out what it lacks before development and suggest a realistic plan. Describe your task and we will discuss it with no obligation.
FAQ
How many pages are included in Figma-to-HTML work?
As many as the estimate states. The number of unique blocks matters more than the page count, because pages assembled from ready components are simpler to build.
Can a site be coded if the design exists only for desktop?
Yes, but the mobile version has to be designed first. It is better to do this in the design file before coding, so you approve the look in advance.
Does layout work include payment and CRM integration?
Usually not, since that is programming. Clarify in the contract whether the job ends with static pages or the site is connected to a CMS, Click, Payme and other services.
How can I tell the layout was done well?
The page matches the design on several phones, opens quickly on mobile internet, displays both languages correctly and comes with clear source files.
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.