Technology Division

Apps People Keep Using

iOS and Android applications designed for Arabic users, connected to your systems, and shipped through the stores without surprises.

  • iOS & Android from one codebase
  • Arabic RTL interfaces
  • Store release handled for you
  • 2Platforms, one codebase
  • AR+ENTested in both languages
  • 100%Store submission handled

Most apps are uninstalled in the first week

Usually because they are slow, confusing, or solve a problem the customer did not have. We prototype the main journey before building it, test on real devices in both languages, and measure what people actually do after launch.

  • One codebase, both platforms, consistent behaviour
  • Offline and poor-connection states designed, not ignored
  • Local payment and identity integrations
  • Crash reporting and analytics from day one
What's included

From idea to the store

Design, build, release and the monitoring that tells you what to fix next.

  • iOS & Android apps

    One codebase delivering native-quality performance and platform-correct behaviour on both stores.

  • Backend & APIs

    The services behind the app — authentication, data, notifications — built and documented with it.

  • Payments & integrations

    Local payment gateways, Absher-style identity flows and connections to your existing systems.

  • Arabic-first interfaces

    Right-to-left layouts, Arabic typography and numerals treated as the primary design, not a variant.

  • Store release

    Developer accounts, listings, screenshots, review responses and phased rollout managed for you.

  • Analytics & monitoring

    Crash reporting, performance traces and funnel analytics so decisions come from data.

How we work

From prototype to published app

  1. 01

    Scope & journeys

    We define the one job the app must do well, and the screens that deliver it.

  2. 02

    Prototype

    A clickable prototype reviewed on a phone, so problems are found before development.

  3. 03

    Build

    Two-week increments you can install and try, with the backend built alongside.

  4. 04

    Test on real devices

    Arabic and English, low-end phones, poor connections and the edge cases that break apps.

  5. 05

    Release & iterate

    Store submission, phased rollout, then improvements driven by real usage.

What we build with

Chosen for maintainability and for finding developers later, not for novelty.

Apps
  • React Native
  • Expo
  • Swift
  • Kotlin
  • TypeScript
Backend
  • Node.js
  • NestJS
  • Firebase
  • REST & GraphQL APIs
Data
  • PostgreSQL
  • Firestore
  • Redis
  • Offline sync
Release & monitoring
  • App Store
  • Google Play
  • Sentry
  • Firebase Analytics
FAQ

Questions we hear often

  • Rarely. One codebase covers both for most business apps, at roughly half the cost. We recommend fully native only when the app depends on heavy device features.

  • You do. Accounts are created in your company's name, and the source code is yours from the first commit.

  • We handle the review process, including responses and resubmission. Common rejection causes are checked before we submit.

  • Yes, after a short code and architecture review so we can tell you honestly whether it is worth continuing or rebuilding.

Have an app idea, or an app that is not working?

Tell us what it should do. We will come back with a realistic scope, timeline and cost.