Right-to-left layouts, Hijri dates, and regulatory vocabulary change how software must be built. Treating them as a skin produces the exact failures GCC buyers know too well.
Written for: GCC employers & PMOs
Ask any GCC HR manager about "Arabic versions" of Western software and you will hear the same stories: mirrored buttons with unmirrored logic, forms that break when names contain Arabic particles, reports whose numbers read backwards, and Hijri fields that silently corrupt probation calculations.
If your field technician has to switch to English to complete an inspection, the software has failed the worker — and eventually the audit.
No. Feature parity is absolute; only the language direction and labels change.
Yes, per user account, and field devices can be locked to Arabic-only for simplicity.
Differentiation has been theory for a century because it was operationally impossible. Groups make it five minutes of configuration.
The cohort-vs-self-paced debate assumes a binary. Groups dissolve it: one content library, two delivery models, two price points.
Everything groups can do, configured in one console — with the four patterns worth copying.
