Work / Case study

A platform built for the Arabic literary tradition.

We designed and built a multi-platform system for a UAE government cultural authority - a public resource for Arabic poetry that handles meters, prosody, and the technical details of Arabic typography at the scale of a research library.

ClientUAE Government
Cultural Authority
SectorGovernment,
Cultural Heritage
RegionUAE
DomainArabic poetry
& prosody
PlatformsWeb, mobile, API
Classical Arabic calligraphy carved in stone
01 - At a glance

A research-library scale, in a consumer-grade experience.

The platform serves Arabic poetry to scholars, students, and the general public - with the search performance and editorial depth of a research database.

Verses indexed
2M+
Searchable across the full corpus, with morphological matching and diacritics-insensitive lookup.
Poems catalogued
160K+
Structured by author, meter, theme, era, and diwan - navigable and citable.
Surfaces
3
Angular web app, Flutter mobile apps, and a .NET API serving both - built and maintained as one system.
02

The challenge.

Arabic poetry is one of the deepest literary traditions in the world - and one of the hardest to build software for. The text itself carries layers of meaning that don't exist in most other languages: diacritical marks that change a word's grammar and meaning, prosodic structures (meters, feet, rhyme) that define a poem's form, and editorial conventions for arranging poems into diwans and anthologies that have developed over more than a thousand years.

Off-the-shelf content platforms treat Arabic as a Unicode block. They render the script and stop there. What this client needed was different: a system that understood the literary domain - that could index by meter, search across diacritical variants, present a poem with the visual integrity of a printed diwan, and let a scholar move between a verse, its author's biography, the meter it sits in, and the dictionaries that gloss its vocabulary.

And it had to work for everyone - not only specialists. A student looking up a half-remembered line, a teacher building a lesson, a researcher running a corpus query, and a casual reader listening to a poem aloud all needed to find what they were looking for, on whatever device they were holding.

03

What we did.

  • Arabic-first application architecture. A right-to-left interface designed around Arabic typography from the ground up - including the typographic specifics of poetry: diacritical marks, verse structure, and visual conventions inherited from print scholarship.
  • Solr-based linguistic search at corpus scale. Apache Solr indexes more than two million verses with Arabic-aware analysis: stemming, morphological matching, and diacritics-insensitive lookup so a user can search a word as they remember it, not as it's formally written.
  • Specialized literary domain modelling. Poetry meters (prosody), diwans, dictionaries, and biographies represented in a data model that respects the relationships scholars actually use - not just generic content categories.
  • An in-browser book reader. Page-by-page navigation that preserves the look and feel of a printed diwan, with cross-references, citations, and audio streaming for recited verses.
  • Multi-platform delivery, one source. An Angular web application and Flutter mobile apps (iOS and Android) sharing a single .NET API. New content, new features, and bug fixes deploy to every surface from one workflow.
  • Private Azure cloud, with proper engineering practice. Deployed on a dedicated Azure environment with CI/CD pipelines, automated testing, and observability - so changes ship safely and quickly.
AngularFlutter.NETApache SolrAzureCI/CDArabic NLP
04

The outcome.

01
A working scholarly tool, in everyone's pocket.A platform that holds up under research-grade use - and is approachable enough for a general audience to use casually.
02
Arabic, treated as architecture.Search, layout, data model, and editorial workflows all designed for the language - not translated from an English-first product.
03
One system, three surfaces.Web, iOS, and Android maintained as a single product. New features ship to every device without divergence between platforms.
04
Cultural infrastructure that lasts.Built on engineering practice - version control, automated testing, deployment pipelines - so the platform can be maintained and extended for the long term.
Work with us

Working on something that's genuinely hard?

We like complex domains - bilingual systems, scholarly archives, government workflows, anything where the technology has to respect a real-world tradition. If that's the kind of project you're planning, we'd like to hear about it.