What the Figma-to-code step actually includes
This step sits between the designer and the back-end developer. A front-end developer takes the design and builds pages in HTML, CSS and JavaScript, or components for a chosen platform such as Next.js, WordPress, Tilda with custom code or Laravel. The technology you pick decides who can edit texts and add sections later.
It helps to know the limits. Copywriting, ad setup and SEO strategy are not part of it, although a well-built front end lays the groundwork for them: proper headings, light images and a clear page structure. If you need a complete website, this is one part of a larger job.
How to prepare the Figma file so the build goes smoothly
Most delays don't come from the developer. They come from the input: a design assembled by eye, where every detail needs a clarifying question. Before handing it over, check the following.
- Shared styles: colours, fonts and text sizes are set up as styles, not painted by hand in every block.
- Components: buttons, cards and form fields are reusable elements with states such as hover, pressed and error.
- Grid and spacing: one logic is used throughout, not random values on each screen.
- Mobile layout: drawn separately rather than left to the developer's judgement.
- Real copy: actual headlines and descriptions in the required languages instead of placeholder text.
- Assets: icons as vectors, photos at sensible sizes, the logo in several versions.
What is specific to the Uzbek market
The first point is bilingual content. Russian and Uzbek texts take up different amounts of space, and Uzbek often runs longer. A button that looks neat in the Russian layout can wrap onto two lines in Uzbek. Test the design in both languages before the build, not after.
The second is the customer's path. Many people open a site on a smartphone from an Instagram link, a Telegram post or an OLX listing, sometimes on mobile internet that can be unstable outside the capital. So the mobile version is the main one, and heavy animations and large photos need to be optimised.
The third is familiar contact and payment habits. A “Message us on Telegram” button, tap-to-call, a form that notifies a manager and payment through Click or Payme are what your customers really use. Plan them into the design rather than bolting them on at the last minute.
How the work runs, from design to launch
A typical flow looks like this. The developer reviews the design and raises questions about unclear parts, agrees the technology, builds pages block by block and shows progress on a test link. Then forms, analytics and the language switcher are connected, and only after that does testing begin.
Don't demand a pixel-perfect match at any cost. A reasonable goal is a site that looks like the design on the main screen sizes and reflows cleanly in between. Chasing exactness on every device adds time and budget, and your customer will hardly notice the difference.
What the price depends on
There is no fixed rate, and an honest estimate is always tied to the design file. The cost depends on the number and complexity of pages, how many unique blocks there are, animations, adaptation to different screen sizes, the number of languages, the platform and integrations such as forms, CRM, payments and Telegram notifications.
Count the work around the build as well: connecting a domain and hosting, setting up analytics and support after launch. Ask for an itemised quote, because that makes offers from freelancers, studios and agencies much easier to compare.
How to review the result before you accept it
Review against a checklist. Open the site on different phones and browsers, check both languages, send a test enquiry and confirm it reaches your manager. See how the page loads on a slow connection and make sure analytics goals fire.
If the site is meant for advertising, do this before the campaign starts. A good-looking page without working counters and forms turns an ad budget into spending with no clear outcome.
When it makes sense to bring in a team
If the design doesn't exist yet or was drawn without development in mind, it is easier to run design and build together: fewer revisions and fewer misunderstandings. At markdev we build websites end to end, from structure and layout to launch, analytics and form integrations. If you want to discuss your project in Tashkent or the regions, send us a request and we will suggest where to start.
FAQ
How is front-end build different from full website development?
The front-end build turns a design into pages visible in the browser. Full development is wider and covers the server side, an admin panel, payment and CRM integrations and data storage.
Can a site be built if the design isn't in Figma?
Yes. Figma is convenient because the developer sees sizes, spacing and styles inside the file and can export graphics directly. Designs from other tools are accepted too, but they usually need more clarification.
Do I need a separate mobile design?
Ideally yes. Without it the developer decides how blocks rearrange, and the result may not match your expectations. This matters most when customers arrive from Instagram and Telegram.
How can I tell the build quality is good?
Compare the site with the design on a phone and a computer, then check both languages, forms, loading speed and analytics counters. If everything works without manual fixes, the build is clean.
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.