Arabic is an operating language, not a translated interface.

A system can look translated and still fail in Arabic. We design direction, hierarchy, terminology, search, documents, data entry, print, and mixed-script behavior as one complete Arabic operating experience.

Native composition

Arabic receives a real right-to-left composition with mirrored layout logic, purposeful line lengths, Arabic typographic rhythm, and correct emphasis. It is not English content moved to the other side.

  • True RTL layout
  • Alexandria typography
  • Arabic information hierarchy
  • Mixed-script isolation

Operational terminology

Names for roles, policies, documents, fields, approvals, and institutional structures are treated as product decisions. The wording must match how the organization actually works.

  • Reviewed terminology
  • Institution-specific vocabulary
  • Consistent field names
  • Clear approval language

Arabic documents and retrieval

Nasaas accounts for Arabic reading order and reconstruction. Smart Archive builds Arabic-first retrieval. ERP carries Arabic through interface, search, workflow, documents, and print.

  • Reading order
  • Search and normalization
  • Arabic forms and outputs
  • English and Arabic records

English remains complete

English is not removed or reduced. Both languages are built as first-class operating experiences, with additional language needs shaped per deployment.

  • Equivalent routes
  • Localized metadata
  • Language-preserving navigation
  • Deployment-specific language scope

Start with one process.

Start with a document, record, or approval path that should work better. We scope it, build the pilot, and test it against the work itself.

Plan a pilot