What Figma to HTML actually covers
A Figma file is a collection of frames, fonts, colours and spacing. Turning it into HTML and CSS, plus scripts where needed, is front-end work. It is not the same as building a whole website. A front-end developer delivers the visible layer, while an admin panel, a product catalogue, payments through Click or Payme and lead delivery into a CRM are separate jobs that should appear separately in the estimate.
Clients often blur the two and are then surprised that a page that was coded from the design does not take orders. So the first question to ask a contractor is simple: what exactly will I receive? Static pages, a site on a CMS, a template for a builder, or a complete system with forms and payments? The answer shapes both the timeline and the budget.
How to prepare a design so development goes smoothly
Most arguments and rework start in the design file, not in the code. Before you hand it over, check the following.
- A mobile version exists, not only a desktop one. Many customers arriving from Instagram or Telegram are on a smartphone.
- Buttons, cards and forms are built as consistent components rather than redrawn on every page.
- Fonts support Cyrillic and Uzbek Latin, including the o‘ and g‘ characters.
- Element states are shown: hover, form error, empty list, loading.
- Text in the design has realistic length in every language. Uzbek phrases are often longer than Russian or English ones, and a button sized for one short word will break.
- Images and icons are supplied as source files or marked for export.
What separates good front-end work from poor work
Matching the design on the developer’s laptop is only the starting point. Real visitors open your site on budget Android phones, in Safari on an iPhone, on unstable connections in transit or inside a shopping centre. Good work shows in a few ways.
- Responsiveness: the page reads equally well on a narrow phone, a tablet and a wide monitor, with nothing overflowing or cropped.
- Speed: compressed images, a modest number of fonts and no unnecessary scripts. A visitor on weak mobile data will either wait for the page or close the tab.
- Semantic markup: one H1, a logical H2 and H3 structure, alt text for images. This is the foundation of SEO and hard to bolt on later.
- Working forms: a request lands in Telegram, your CRM or email, and your manager receives every field.
- Analytics in place: counters and goals configured before launch, not “later”.
- Testing in several browsers and on real devices, not only in an emulator.
What drives the price and timeline
Quoting numbers without seeing your project would be dishonest, but the logic of pricing is much the same everywhere. Cost depends less on the number of pages and more on the number of unique templates. Twenty similar product cards are one template, while a single complex landing page with animation can take more effort than an entire catalogue.
Beyond that, the level of interactivity, the number of language versions, CMS integration, the quality of the design file and the number of revision rounds all matter. A freelancer, a small team and an agency offer different levels of guarantee and support. Very cheap work that was never tested on devices often turns into paid fixes after launch, so compare what is included, not just the total.
How to accept the finished work
Ask to see the result at a test address and go through it yourself. Open it on your own phone, fill in every form and confirm the request arrives. Switch languages, scroll through pages on a slow connection and compare the key screens with the design.
In the contract, state what you receive at the end: source code, hosting and domain access, and instructions for updating content. Agree separately on the number of free revisions. The code and the domain should stay with you, not with the contractor.
Good code does not sell on its own
A website is not an end in itself. Traffic will come from Meta Ads and Google Ads, Instagram posts and links in Telegram channels. If the first screen does not make your offer clear, or the form is buried three screens down, you pay for clicks that never become enquiries.
So agree on a metric before you start: cost per lead, the share of visitors who leave contact details, search positions for the queries that matter. Without basic analytics you cannot tell whether the site pays back or the budget is simply being spent.
At markdev we build websites end to end, from the design and front-end through to forms, analytics and payment integration. If you already have a Figma file, or only an idea, describe the task and we will suggest the working format that fits.
FAQ
How is converting Figma to HTML different from website development?
Conversion turns the design into page code: HTML, CSS and interface scripts. Website development is broader and includes the admin panel, database, payment integrations, CRM connections and other functions. Many projects need both.
Do I need a separate mobile version of the design?
Yes, it is better to draw it in advance. If the developer has to invent the mobile layout alone, the result may differ from what you expect, and the corrections will add time.
Can the site be built in two languages from the start?
Yes, but plan for it in the design. Russian and Uzbek texts differ in length, and the font must support every character you need. Discuss the structure of the language versions before work begins.
How can I tell the front-end work is good quality?
Open the site on your phone, on a weak connection and in different browsers, submit a test request and check that it arrives. Good work looks equally tidy on every screen and loads quickly.
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.