Website Design in Uzbekistan: How to Brief and Approve

Website design in Uzbekistan often goes off track for a simple reason: the owner cannot put into words what the site should do, so the designer fills the gaps with personal taste. Revisions pile up and nobody is happy. This guide covers how to brief a designer, judge mockups on merit and what to collect at handover.

What to prepare before the design starts

A good brief fits on one or two pages. It says what the company does, who buys, which action you expect from a visitor (a lead form, a call, an order in Telegram, a payment via Click or Payme) and how you differ from competitors. Phrases like "modern and minimal" tell a designer almost nothing. "Lots of white space, two colours, large photos" is a real direction.

Content matters more than most owners expect. If the layout is drawn around placeholder text, a real headline in Russian or Uzbek will turn out longer and the composition will break. Designing around actual copy is more accurate.

  • Vector logo, brand colours and fonts, a brand book if you have one
  • Three to five sites you like, with a note on what exactly: photo style, density, typography
  • One or two sites you dislike, and why
  • Draft copy for at least the main pages
  • Real photos of products, premises and the team
  • A ranked list of actions a visitor should take

Website design in Uzbekistan: the stages that matter

A sound process moves from general to specific, and each stage ends with your approval. Changing the structure after sign-off is expensive because every page has to be redrawn.

Agree the number of revision rounds and how feedback is delivered in the contract, before work begins.

  • Concept: the home page or one key page in one or two style options
  • Approval of the direction
  • Remaining templates: catalogue, product or service page, contacts, blog
  • Mobile and tablet versions
  • UI kit: buttons, fields, cards, element states
  • Files prepared for hand-off to development

How to judge mockups

"Do I like it?" leads to arguments about taste. A short checklist works better.

  • Can a stranger tell in five seconds, from the first screen, what you offer and to whom
  • Is the main action obvious on every page
  • Is the text easy to read: size, contrast, line length
  • Does the site look like your company rather than a generic template
  • How does a page look on a phone with real-length text
  • Are identical elements styled identically across pages

How to give feedback

Collect comments in a single document or directly on the mockup, and name one person responsible. When five people with different tastes review a design, the result is a compromise nobody likes. Show it to a few people from your actual audience: a customer's reaction outweighs a colleague's opinion.

Describe the problem, not the fix. "Nobody notices the phone number" is better than "make the phone red", because the designer can find a solution that does not break the layout. Edits driven by "I just prefer it" with no link to the site's goal are the main reason projects drag on.

Photos, fonts and readability

Design depends on imagery. Stock photos are easy to spot, and real shots may be weaker, so the launched site can look different from the approved one. Plan a shoot of the office, team, products or sites alongside the design and put real images into the mockups as early as you can.

Check that the chosen fonts support Cyrillic and Uzbek Latin, including the letters o‘ and g‘, which sometimes render badly. Look at text contrast, font size on a phone and button size for a thumb. Do not rely on colour alone: a form error should come with a text message.

Animation earns its place when it carries meaning, such as showing a button press or a new block appearing. Effects for their own sake slow reading and make the site heavy on budget phones.

What you should receive at handover

Show the mockups to a developer before approval. They will spot elements that are costly to build or slow to run, so the design does not have to be simplified later during development.

  • Mockups of every approved page for desktop and mobile
  • UI kit and styles: colours, fonts, spacing
  • Exported icons and images
  • Description of animations and states: press, error, empty list
  • Source files (for example Figma) in your company account or shared with it
  • Licence details for fonts and images

Where to start

If you need a turnkey site, it is easier to run design and development together, so mockups stay realistic. To talk through your project, contact markdev: we will go over your brief, help define the scope and suggest where to begin.

FAQ

Do I still need a brief if I already have a logo?

Yes. A logo shows style, not goals. A brief explains who your customers are, what action you want and how you differ from competitors.

How many people should approve the design?

Ideally one responsible person who collects all comments in one place. A large group with opposing tastes turns approval into a compromise.

Can I use stock photos in mockups?

For the concept stage, yes, but plan real photos early and swap them in soon, otherwise the finished site will differ from what you approved.

Which files should I get when the design is done?

Desktop and mobile mockups of all pages, a UI kit with styles, exported icons and images, a description of animations and states, and source files you can access.

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.