Public Services That Work on Any Phone

Every engagement starts with a paid diagnostic on one service, the DLS 2.0 Readiness Review. Fixed scope, fixed fee, agreed before it starts. The build that follows is priced from what that review finds, because a form with four fields and a service with nine approvals are not the same job. We do not quote a portal before we have walked it.

A readiness review on one service runs 2 to 3 weeks. One service rebuilt, tested and launched usually runs 8 to 12 weeks from brief to live, and most of that time is approvals, not design. A full portal is a programme rather than a project, so we plan it service by service and put something live every quarter.

Yes, both, and with semi-government bodies. What matters more than the entity type is whether the service owner can sit in the reviews. Projects stall when screens are approved by people who never watched a resident use them. We ask for one named owner on your side before the work starts.

Access to the service as it runs today, the rules behind it, and one named owner. That means the current forms, the approval steps, and someone who can tell us why each rule exists. If you hold complaint logs or call centre notes, send those as well. They usually point straight at the screen that is failing.

The common failure is a service that meets the standard and still frustrates residents, because the rules behind it never changed. Design cannot remove an approval step that policy requires. If we find one, we say so, and we tell you which part sits with your policy or legal team rather than with us. That conversation is cheaper before the build than after it.

DLS 2.0 is the UAE Design Language System 2.0, the government standard for how a public digital service must look and work. It sets layout, type, colour, forms, error messages, and how the service behaves in Arabic and in English. Federal entities are expected to follow it. For residents it means every government service works one familiar way.

We follow UAE government security standards. We encrypt data at rest and in transit, and we run security audits on a fixed schedule. We host inside UAE-approved data centres, or inside the infrastructure your own IT team already runs, so nothing new leaves your control.

It means a resident with a disability can finish the service alone. We test with a screen reader, with keyboard only, and at large text sizes, against WCAG, the international accessibility standard. We also check colour contrast and error messages, because a form that flags a mistake in red text and nothing else fails a colour blind user.

Arabic takes more. Arabic reads right to left, so the whole layout mirrors, and most sites break when you flip them. We build the Arabic version properly and we write it fresh, never machine translated. Both versions are tested with real residents, because a label that reads oddly stops people as often as a broken button.

Yes, and that is usually the cheaper place to start. We take one live service, walk it as a resident, and hand you the fix list ordered by cost and return. Entities often find that three or four screen changes do more than a full rebuild would, and the rebuild can then be planned against evidence instead of opinion.