Web Development Company in Doha

A Doha web number depends chiefly on whether the site transacts and on who regulates it. A scoped Doha marketing site runs eight to twelve weeks for a bilingual Arabic RTL and English Next.js or Nuxt build on a headless CMS, hosted on Azure Qatar Central. Transactional sites add NaPS-aware checkout, member portals, and QPDPL-aligned data handling. Enterprise platforms (Qatar Airways-style booking flows, QNB online banking portals, Tasmu Smart Qatar citizen services, QatarEnergy supplier and investor relations stacks) extend the scope further. Rates sit below Doha agency benchmarks because delivery runs from Edmonton and Chandigarh, and above offshore-only firms because we hold a Doha-based delivery lead and synchronous AST overlap. Proposals are fixed-fee.

Arabic RTL is the default starting point, not a translation pass. We design logical layout primitives in Tailwind, Radix, and shadcn so direction flips cleanly between Arabic and English, mirror icons, chevrons, and progress steppers, and tune Arabic typography with IBM Plex Sans Arabic, Noto Naskh Arabic, or GE SS Two type families against the brand. The information architecture is built bidirectionally, so Arabic-first navigation, breadcrumbs, ARIA landmarks, and form labels are correct in both modes. Numerals follow the locale preference (Hindi-Arabic numerals for Arabic content where the brand allows, Western Arabic for English) and dates render Hijri or Gregorian based on context. URL structure uses /ar/ and /en/ paths with hreflang annotations and a language switcher that respects user preference cookies. Bilingual QA runs in parallel rather than as a post-launch fix.

Yes. Hijri calendar integration is a hard requirement for government-adjacent portals (MoCI, Ministry of Interior, Qatar Tourism), banking sites that publish branch hours during Ramadan, sports and event platforms tied to Aspire Zone or Qatar Sports for All, and any site that schedules services around Friday prayer windows. We render dual Hijri and Gregorian dates using validated calendar libraries (Umm al-Qura calendar for the Saudi-aligned definition where required, the Tabular Islamic calendar for general purposes, and the Qatar-specific moon sighting committee calendar where the client publishes against it). Date pickers, event schedulers, and email templates support both calendars side by side. Ramadan-aware UX (adjusted business hours, Iftar timing surfacing, prayer time integration via the Islamic Society of North America or local Qatar Awqaf and Islamic Affairs feeds) ships with the standard calendar module.

Tasmu Smart Qatar is the national smart city programme led by the Ministry of Communications and Information Technology and covers transport, logistics, environment, healthcare, and sports verticals under Qatar National Vision 2030. Web platforms that touch citizen services or government-adjacent infrastructure align to a Tasmu domain blueprint, which dictates service-pattern conventions (a service catalogue grouping rather than feature-driven navigation), open data standards, and integration paths into government shared services. Our public sector engagements produce a Tasmu-aligned service design document, a QPDPL impact assessment, and accessibility evidence against WCAG 2.2 AA tested in Arabic and English. We coordinate with MEEZA-hosted government landing zones where the workload requires sovereign hosting and keep page templates compatible with the Hayya and Metrash2 visual language users already trust.

Yes. Qatar Airways and Discover Qatar set the Doha booking-flow bar, and the build is more demanding than the visible UI suggests. We integrate Sabre and Amadeus GDS for inventory and pricing, ARC/IATA settlement flows where applicable, NDC content where the carrier has published it, multi-currency display with QAR as the home currency and USD, GBP, EUR, AED, INR shadow pricing, NaPS plus Network International plus Dibsy plus Apple Pay plus Alipay+ for the China traveller segment, and a fare rules engine that survives the bilingual Arabic and English presentation expectations. Loyalty portals (Privilege Club style) handle tier status, miles balance, redemption against partner inventory, and family pooling. The frontend ships on Next.js 14 with edge caching tuned to GDS response patterns and a graceful degradation path for slow 3G connections common in regional roaming.

Checkout flows touch two Qatar regimes. QPDPL Law No 13 of 2016 governs personal data handling and the Compliance and Data Protection Department under MoCI enforces it. The Qatar Central Bank Cybersecurity Framework governs payments and online banking, with NaPS routing under QCB sponsor bank flows. Our discovery phase produces a QPDPL data flow record covering checkout inputs, classifies sensitive categories that require explicit consent, and maps data subject rights. Payment surface areas are PCI-DSS 4.0 SAQ A or A-EP scoped, with tokenisation handled by Network International or Dibsy so the merchant CDE stays as narrow as possible. Biometric step-up (Face ID, BiometricPrompt) is configured under QCB guidance for high-value transactions. Breach notification playbooks reference both MoCI and, for QCB-supervised entities, the Q-CERT reporting channel run by NCSA. For QFC-licensed entities we layer the QFC Data Protection Regulations 2021 on top.

A typical bilingual Doha enterprise web build (banking online portal, government-adjacent service portal, university prospectus and application platform) takes sixteen to twenty-four weeks from kickoff to launch. Week 1 to 3 is discovery, regulator and Tasmu blueprint mapping, content architecture in Arabic and English, and accessibility baseline. Week 4 to 14 is design and build with bilingual QA running in parallel rather than after the fact. Week 15 to 18 is integration testing against NaPS, Sabre, SAP Ariba, or Cerner depending on the workload, and an NCSA-aligned security review. Week 19 to 22 is QCB sponsor bank UAT for banking workloads, MoCI submission for citizen-facing portals, and a Core Web Vitals certification across 3G connections common in labour-housing and construction-site usage. Week 23 to 24 is launch with a controlled rollout and post-launch monitoring. QFC-licensed launches and Shariah-governed Islamic finance sites add two to four weeks.

Yes. Bilingual accessibility against WCAG 2.2 AA is the default scope. We test screen reader behaviour with VoiceOver, NVDA, JAWS, and TalkBack in both Arabic and English, since RTL document direction, Arabic ligature shaping, and Hindi-Arabic numeral handling all create accessibility regressions that pure-English testing misses. Keyboard navigation is verified end-to-end with the document direction flipped between sessions. Performance budgets target a Largest Contentful Paint under 2.5 seconds on a Qatar 3G connection (representative of construction sites, labour housing, and rural Al-Khor or Mesaieed coverage), with Arabic fonts subsetted aggressively, image delivery on AVIF and WebP via Cloudflare or Azure Front Door, and JavaScript shipped under 150KB per route via Next.js Server Components or Nuxt 3 islands. Lighthouse and WebPageTest evidence ships with the launch package.