Service
Built for the person using it, not the person who commissioned it.
From product definition to release and improvement, Kerah designs and builds websites, web applications and mobile apps around user needs, business rules and the conditions people actually work in.
Who this is for
- Product and digital leaders launching or replacing a customer-facing product
- Organizations serving customers, members, citizens or applicants digitally
- Teams supporting field, site or frontline staff on mobile devices
- Organizations that need Arabic and English treated as equals
The problems this addresses
- An interface designed for the person who commissioned it rather than the person using it
- Training that never ends because the common task is not the obvious one
- Data entered incorrectly under time pressure, then corrected downstream
- A public site the organization cannot change without going back to whoever built it
- Arabic added late, producing a layout that reads as an afterthought
- No measurement after launch, so nobody knows which parts are working
What changes
- Common tasks take fewer steps and produce fewer errors
- The product is usable by people relying on assistive technology
- Arabic and English are equally considered, not one translated into the other
- Content and pages can be maintained by the organization itself
- Release is repeatable rather than an event
- Product decisions after launch are informed by measurement
What Kerah can deliver
Capability, not a claim of past work. Final scope is established through discovery.
- Product discovery and user journey definition
- User experience and interface design
- Design systems and component libraries
- Corporate and campaign websites with an editable content model
- Responsive web applications
- iOS and Android applications
- Offline-capable capture for work done away from a desk
- Arabic- and English-ready experiences, designed bidirectionally
- Accessibility implementation and testing
- Backend services and APIs
- Authentication and role models
- Analytics and product measurement
- Release and app-store support where agreed
What you receive
Artefacts, not activities. Each one is something you can hold, read or run after the engagement.
- Product definition and prioritised scope
- Interface designs and interaction states
- A design system your team can extend
- Running application and back end
- Content model and editing workflow where you maintain your own pages
- Accessibility test results
- API documentation
- Release process and rollback procedure
How the engagement runs
- Research with the users, not only the sponsor
- The people who will use the product every day describe different problems from the people who commissioned it. Both matter; only one is usually in the room.
- Prototype before code
- Interaction problems are cheap to fix in a prototype and expensive to fix in a release. Designs are tested before they are built.
- Bidirectional from the start
- Right-to-left is a layout decision taken at the beginning. Retrofitting it after the interface is built produces mirrored bugs for months.
Commercial shape. A project with defined releases, or a continuing arrangement with agreed capacity where scope is expected to evolve with evidence.
Raised from the start, not before launch
Architecture, security and data decisions that are cheap to make early and expensive to retrofit.
How Kerah approaches security- Authentication, session handling and account recovery
- Behaviour on poor connectivity, and what happens to work in progress
- Error states that describe the actual problem and the way out of it
- Performance on the devices your users own, not the newest ones
- Who owns and updates the content after launch, and with which tool
- Analytics scoped to product questions, without collecting unnecessary personal data
- App-store operations, review requirements and update cadence where relevant
Where this stops
- Kerah does not claim a product will need no training. The commitment is to reduce friction and make frequent tasks clear, and to measure whether that happened.
- Accessibility is implemented and tested to a defined standard within the engagement. Kerah does not issue conformance certification.
- App-store review is the store's decision. Kerah prepares the submission and resolves what is raised; it cannot commit to an approval outcome or a date.
- Brand identity creation is a separate discipline; Kerah works within a supplied identity or with a specialist.
Other services
Discovery and Architecture
A documented blueprint with a target architecture, a permission and data-role map, a phased roadmap and a scope you can approve, price or decline on evidence.
Enterprise Systems
One operational system where work is assigned, decisions are recorded, permissions are explicit and reporting comes from the same data people work in.
Cloud, Data and Integrations
Defined interfaces, a documented data model and monitored flows, so information moves once and reporting can be trusted.
AI and Intelligent Automation
A bounded use case with defined success criteria, evaluation against representative cases, human review where it matters, and a fallback when the model is unavailable.
Managed Evolution
A defined support and release model with security maintenance, an owned backlog and a roadmap reviewed on a set cadence.
Security and Privacy Engineering
A system whose access model, data inventory, encryption, logging and deletion behaviour were designed together — and the documentation an assessor asks for, produced as delivery output rather than reconstructed afterwards.
Quality, Testing and Accessibility
A system tested in both languages by people who read both, measured against WCAG 2.2 AA, and exercised under realistic load and failure conditions before launch rather than after it.
Discuss a digital product.
Tell us what is not working today, who it affects and what a better outcome would change.