DeenODDEENOD STUDIO

studio

One story, three surfaces

July 1, 2026 · Moody · 4 min read

For a few weeks there has been a button in the app that said WATCH THE STORY, and behind it there was nothing. A player who tapped it got a fake timeline over a still image - a placeholder pretending to be a film. On iOS it promised one minute. On Android, two. Both numbers were invented. That button bothered me more than any bug in the battle engine, because the battles were never the point. The stories are the point. The trivia is how you earn them.

So the working theory became: the game is missing its story. Write it, produce it, ship it. Simple.

Except when I actually took inventory, the story was not missing. The narration script for Adam existed, finished and reviewed. Five painted scenes existed - the garden, the two offerings, the crow, the grave, the lamp - stills and animated plates both. The app had a fully built video player on each platform, waiting for a file that had never been rendered. This site had four finished devlog posts and no devlog page, and a waitlist API that no form ever posted to. Nothing was missing. Nothing was connected.

The rule we adopted

Every chapter's story now gets written once and ships three ways:

  1. In the app - the chapter's story scenes: full-bleed art, a few lines per beat, the ayah reference on screen, sources at the end. When a chapter's episode is eventually rendered as real video, the same button plays that instead. The app checks; nobody updates anything.
  2. On the channel - the episode itself, plus the short cuts of its strongest beats.
  3. Here - a story page you can read in five minutes, with the art and every citation listed. Adam's is live now at /stories/adam.

Eighteen chapters in the journey means eighteen stories. Written once each. That is the whole content plan, and the game, the channel, and this site are the same work wearing three coats.

What the app shows now

The placeholder is gone. The button reads WATCH THE STORY - 8 SCENES, because there are eight scenes, and the label is computed from the content instead of typed by an optimist. Chapters that do not have a story yet do not show the button at all. This sounds like a small thing. It is not. A studio that invents a runtime for a video that does not exist will invent other things too, and players can smell it. Every string in that row is now something the app can prove.

The scenes themselves follow the same discipline as everything else we make: the story of Adam contains no Adam. A tree on a stone terrace. Two altars, one lit. A crow scratching at the dirt. A lamp. If you have read the off-screen rule, you know why - and you know we treat the constraint as the aesthetic, not as a workaround.

The part where the process caught me

Everything narrative goes through theological review before it ships - the episode scripts, the social copy, even the arrangement of already-cleared material into a new page. Today the reviewer went through the second episode pack, Nuh, and sent back a list. One item on it: an ayah I had typed into the Arabic draft was wrong. Not a nuance - wrong. The draft carried its own warning in bold, written before the review: never trust AI-typed Qur'an, check every ayah against a mushaf. The review is the net under that warning, and today the net worked. The verse gets corrected from the mushaf before a single frame is produced.

I am telling you this for the same reason the process page exists. A studio working with sacred source material owes its audience the failure modes, not just the wins. The pipeline produced an error; the discipline caught it; that is the system functioning, and pretending errors never happen would be a worse look than admitting one on day one.

What July looks like

A question from the game's bank goes out every morning - source cited with the answer, the next day. Adam's episode lands first, Nuh's at the end of the month, each with its story page here. The devlog you are reading is now actually published, which felt overdue for a studio that keeps saying it wants to work in the open.

If you want the stories as they land, the channel is @deenodstudio everywhere. If you want the game they belong to, it is free on iOS, with Android on its way. And if you just want to read - the first story is here.