Website and web platform development

The default stack is Next.js and TypeScript in strict mode, rendered on the server or at build time. A crawler receives finished HTML, not an empty container a script fills two seconds later — the gap between a page being indexed and one heading being indexed sits right there.

Everything runs through Git from day one: branches, review, CI, a preview deployment per task. You click through a live address, not a screenshot, and any release rolls back with one command.

• Next.js and TypeScript with strict on; types and ESLint gate the build
• Git, code review, CI and a preview deployment per branch
• Canonical, hreflang, sitemap, robots and JSON-LD in the first release

Uzbekistan reads in three writing systems at once: Russian Cyrillic, Uzbek Latin and English — which means reciprocal hreflang across ru, uz and en with x-default and a distinct URL per version. One consequence shows in the address bar: because the country writes in Latin script, Russian words get typed in Latin letters here — "veb razrabotka", "sayt razrabotka". Search engines do not transliterate across alphabets; they match the literal string, and the slug is where it belongs.

Uzbek Latin hides a second trap: "oʻ" and "gʻ" use the modifier characters U+02BB and U+02BC, yet people type a plain apostrophe, a typographic quote, or nothing. Three different characters across the database, the URLs and the on-site search, and the catalogue stops being findable.

Two search engines matter here, not one: Google takes about three quarters of the country's queries, Yandex the rest.

• Reciprocal hreflang across ru / uz / en with x-default
• oʻ and gʻ normalised, so products are found however the apostrophe is typed
• Search Console and Webmaster, Analytics and Metrica, IndexNow from day one

A website rarely lives alone: the catalogue and stock come out of 1C, payment goes to Click, Payme or Uzum, cards are Uzcard and Humo, enquiries land in a CRM and the sales team's Telegram. Integrations are their own layer with a queue and retries — if 1C is unreachable for ten minutes, an order is neither lost nor duplicated.

Then comes the part almost nobody in Tashkent offers on one contract: NetPOS tills, access control and CCTV are installed by us, not by a subcontractor's subcontractor. When stock on the site, at the till and in the warehouse has to be one number, having no boundary between network engineers and developers removes the "whose bug is it" conversation.

• 1C:Enterprise — catalogue, stock, pricing, documents
• Click, Payme, Uzum; Uzcard and Humo cards
• amoCRM and Bitrix24, Telegram notifications, SMS gateways
• NetPOS tills, access control and CCTV on the same contract

Google treats a page as fast at an LCP under 2.5 seconds, an INP under 200 milliseconds and a CLS no higher than 0.1 — measured at the 75th percentile of real visitors, not on a developer's laptop. Those thresholds go into the brief as a checkable acceptance condition.

Holding them is weight discipline: fonts subset by alphabet, Cyrillic and Latin as separate files, because one file carrying every glyph weighs several times more than the page needs; images as AVIF and WebP with dimensions declared.

An honest caveat — what ruins speed is rarely our kilobytes and usually someone else's. A live chat, three ad pixels and a reviews widget can push INP past 200 ms on a mid-range phone in one evening. We price each in milliseconds and leave the decision to you.

The repository is created inside your organisation, not ours. Domain, hosting, DNS, payment keys, analytics and CI sit on your accounts from day one; we work as invited collaborators.

We do not tie clients to a bespoke panel nobody but us can open. Schema, environment variables and deployment steps are handed over in writing, so an outside developer can stand the project up by following them — which is the best test of the documentation.

If the job is three pages, an enquiry form and no integrations, you do not need a Next.js build: a site builder will cover it for less, and we will say so on the first call.

Custom development pays for itself where there is a catalogue, a customer account, pricing logic, roles or a 1C exchange — and even there, lifting one bottleneck into its own service usually beats rewriting a working site wholesale.