English
العربية
Deutsch
EspañolNext.js in Dubai
Next.js development for Dubai companies
A Next.js development company working with Dubai teams. One hour of time difference, a Monday-to-Friday week, and an entity question that decides more than it looks.
- Working day overlap
- Nearly complete. Dubai is one hour ahead of Ankara, and both weeks run Monday to Friday
- Who buys here
- Retail groups, logistics, property platforms, and the holding companies above them
- What that changes
- Arabic is a layout direction rather than a translation layer, and it is decided before the first component
- Local specifics
- Free zone or mainland changes who you contract with and where the invoice goes
Dubai is an hour ahead of us and keeps the same working week. For a remote engagement that is close to the best case, and it is worth saying plainly because most buyers here have been offered development from time zones where it is not true.
Five working days overlapping almost completely means a question is answered in the hour it is asked. The projects that go badly remotely are usually the ones where every exchange costs a day, and that is a scheduling fact rather than a skill one.
Arabic is a direction, not a file
The thing that genuinely changes a build here is bidirectionality, and it is decided long before anyone writes Arabic copy.
A layout written in logical properties - margin-inline-start rather than margin-left, start-4 rather than left-4 - mirrors for free. A layout written in physical properties does not mirror at all, and retrofitting it is not a translation task, it is a pass over every component.
Then the parts a stylesheet cannot solve. Icons that imply direction flip; icons that do not, must not, and a mirrored play button looks wrong to everyone. Numbers and Latin product names inside Arabic text need bidi isolation, or the full stop at the end of a company name lands at the wrong end of the sentence - we hit exactly that on our own site and only saw it by rendering the Arabic page, which is the only way anyone sees it.
And the font. A Latin face has no Arabic glyphs, so the browser falls back to whatever the device has, and the page looks unset next to its English version. A face with Arabic coverage, scoped by unicode range so Latin readers never download it, is the whole fix.
Free zone or mainland
This is the city-level fact that catches people, because it is an entity question rather than a country one.
Whether your company sits in a free zone or on the mainland changes your procurement path, your own invoicing obligations and sometimes who inside your group signs. It does not change our side - the invoice comes from Codefacture Yazılım A.Ş. in Türkiye in US dollars - but it does change how long approval takes, and that belongs in the plan rather than in a surprise.
Worth settling in the first conversation: which entity contracts, and whether that entity's finance team has handled a foreign supplier before.
What gets built here
Retail groups, logistics platforms, property portals. Often bilingual from day one, often with a physical business behind them that already has systems - which means the interesting work is rarely the front end alone.
The front end is where it shows, though: a catalogue that has to be static and fast on a mobile network, a logged-in area that cannot be, and the two sharing a layout. Which route renders which way is the first design decision and the one that is expensive to revisit.
The country-level ground - e-invoicing through an accredited provider, the data questions, what the regulator expects - is on the UAE market page rather than repeated here.