Design and engineering
Production-grade web and mobile builds, shipped in weeks. Design and engineering are the same conversation here, not two departments passing files between them.
One team, one call
The usual arrangement puts design upstream of engineering: a set of screens is agreed, handed over, and then renegotiated in a hundred small messages as the build meets reality. Every one of those messages is a decision made twice.
We run both on the same call. The people who scope the work are the people who build it — that is what being a studio rather than an agency means in practice. A layout that will fight the data model gets caught while it is still a drawing, and an engineering constraint that would quietly ruin an interaction gets raised before the interaction is designed around it.
You see real software weekly. Not a staging link to a prototype that has been polished for the demo, but the build, in the state it is actually in.
Bilingual, properly
Arabic and English are both first-class, which is a stronger claim than it sounds. A right-to-left interface is not a mirrored left-to-right one: the places where mirroring is wrong are the whole problem. Numbers, code, phone numbers and Latin brand names stay left-to-right inside a right-to-left line. Icons that encode direction flip; icons that encode a real-world object do not. Form inputs, sliders, progress bars, carousels and swipe gestures each need a deliberate answer.
We treat the two languages as two real documents, not one document with a toggle. On this site that is why English lives at the root and Arabic under /ar/, each with its own canonical URL — a language switcher that rewrites the page in place gives search engines one URL for two languages and gets one of them dropped.
Petro Defense took this to three languages. English, Arabic and Spanish, each a first-class surface with full right-to-left parity for Arabic, live in production.
What production-grade means here
Responsive across the range people actually use, not three breakpoints that happen to match the designer's monitor. Accessible: real semantics, keyboard reachability, and contrast that survives the brand palette rather than being negotiated against it.
Deployed, with the deploy automated. A build that only one person can release is not finished. Handover means the repository, the pipeline and the documentation, in a state where your team or another studio can pick it up — which is also the only honest proof that the work was not built to keep you dependent.
What ships
- A design system — tokens, components and the rules for using them — not a folder of screens.
- The web and mobile build itself, bilingual Arabic/English throughout.
- Automated deployment, so releasing is a command rather than a person.
- Documentation and a handover session: the repository is yours and readable.
- Weekly demos of the actual build for the whole engagement.
Shipped
Omaraty is the studio's own product and live on Google Play: a building operating system for residential buildings, Arabic-first and fully bilingual, replacing WhatsApp groups and paper ledgers with shared-fund accounting, receipt-backed expense approvals, announcements and resident polls. Petro Defense is a live trilingual corporate platform for a defense, energy and commodities group — English, Arabic and Spanish as equal surfaces.
Common questions
Four to ten weeks for a whole product?
For a scoped first release, yes — and the scoping is what makes it possible. The range is wide because a single-platform web build and a bilingual web-plus-mobile build are not the same job. The strategy week is where it narrows to a date.
Do you work with our existing designers or engineers?
Yes, and it is common. The thing to agree early is who owns the design system, because two teams extending the same component library in different directions is the most expensive kind of duplicated work.
Who owns the code?
You do. The repository, the pipeline and the documentation are handed over, and the handover is part of the deliverable rather than a favour at the end.
Start with a brief
Tell us what you're building. We send back a one-page response with scope, timeline, and a number you can plan around.
Send us a brief