Arabic-First AI: Why Dialects, Datasets, and Deployment Matter
Arabic-First AI: Why Dialects, Datasets, and Deployment Matter Companion models: MasryGPT-Chat-1.5B · datasets · portfolio Arabic is spoken by ~400 million people across 20+ countries, yet most "Arabic" AI is really Modern Standard Arabic (MSA) — the language of news, academia, and religion. Nobody

Companion models: MasryGPT-Chat-1.5B · datasets · portfolio
Arabic is spoken by ~400 million people across 20+ countries, yet most "Arabic" AI is really Modern Standard Arabic (MSA) — the language of news, academia, and religion. Nobody texts in MSA. Egyptians say "ازيك؟", not "كيف حالك؟". Moroccans say "labas", not "كيفك". The gap between the Arabic that models are trained on and the Arabic that people actually speak is one of the largest unaddressed problems in applied NLP.
This essay argues that Arabic-first AI requires three things: dialect-aware models, dialect-rich datasets, and deployment paths that fit local infrastructure. I write from the perspective of a full-stack developer who has built and shipped both the models and the products around them.
Most Arabic LLMs (Qwen, Jais, AceGPT, ALLaM) are trained and evaluated on MSA-heavy corpora. The result:
In my own MasryGPT evaluation, base Qwen scored 4.7/5 MSA fluency but only 3.1/5 Egyptian fluency. After one epoch of dialect fine-tuning, Egyptian fluency rose to 4.6/5 — at the cost of a small MSA regression (−10%). That tradeoff is real and worth naming honestly.
Dialect data is scarce, noisy, and legally messy:
The 3M-row dialect dataset is the backbone; the MasryGPT training set (80k) is a curated subset focused on Cairo speech.
Key takeaways from fine-tuning Qwen2.5-1.5B-Instruct on 80k Egyptian examples:
A second, less discussed problem: Arabic as an instruction language for code generation. Most code LLMs are trained on English prompts. An Arabic-speaking developer who thinks in Arabic must mentally translate before prompting — friction that slows adoption.
My arabic-to-code-8-langs-3m dataset targets this directly: Arabic instructions mapped to code in 8 programming languages. Combined with a dialect model, this enables a fully Arabic developer experience: think in Masry, get code.
Arabic-first AI must run where Arabic speakers are:
Arabic-first AI is not a translation problem. It is a culture problem, and culture lives in dialects. The models that win will be the ones that sound like the people they serve.
Author: Islam Al-Nashar — Full-Stack Developer & AI builder. GitHub · Hugging Face · Portfolio