Skip to content
About

Arabic-first is not a translation setting.

Almost every productivity app an Arabic speaker can install was designed in English and mirrored afterwards. You can see it: the type is too tight, the numerals are wrong, and the copy reads like a translation because it is one. Rihla is written in both languages side by side, in the same file, and neither side is generated from the other.

Who

One person builds and writes all of this — the Android app, this site, the engines on both sides and the words in both languages. There is no team page because there is no team, and a masthead of invented contributors would be the first lie on a site whose whole argument is that it does not tell any.

What decides arguments here

Three rules, each of which has cost us something.

  1. 01

    The app wins over the brief

    When a design direction and the code disagree, the code is what a user will actually install. A brief asked twice for an emerald accent; the shipped launcher icon is indigo, and the site went back to indigo twice. The brief was the founder’s own, both times.

  2. 02

    Silence beats a plausible number

    Almost every engine in the app has a path that returns nothing. The composite score is unavailable rather than low; the nudge does not fire on an unknown hour; the simulation declines a goal with no history. Each of those costs engagement, and each is the reason the outputs that do appear are worth reading.

  3. 03

    Look at it, do not reason about it

    Every real bug this project has shipped was found by opening the page, not by reading the code: a 3D world rendering perfectly behind its own parent’s background, a chevron pointing at the ceiling in Arabic, a scroll story reporting the wrong act so the section being read was the dimmed one. The build was green for all three.

What is not decided

Things this page would normally assert, and does not.

  • There is no company named anywhere in either repository, so the terms of use carry no governing-law clause. That is a gap waiting on an answer, not an oversight.
  • No launch date. The Android build is in development, and a date published before there is one is a date that gets quietly moved.
  • No funding, no headcount, no revenue. If any of those changes it will appear in the changelog rather than in a paragraph here.

The clearest thing on the site is the code.

The documentation walks through how each engine computes what it shows you, including the branches where it decides not to show anything.