Eleven years ago a game about a stranded astronaut talked its way onto a lot of wrists. If you were there, you remember the specific feeling: a buzz, a message from someone who needed you, and no way to know how long you'd be waiting for the next one.
That game was Lifeline, and it did something almost nobody has managed since — it made a text box feel like a person, and it made waiting feel like caring. This post spends a lot of words on its rough edges, so let's be clear about the premise up front: we're building in its lineage because it earned one.
Ours is called The Ankh Protocol, and it's a real-time narrative mystery for Apple Watch and Wear OS.
The pitch
Something wakes up on your wrist. Her name is ARA, and she doesn't remember what she is.
She knows she was sealed inside the relic for a reason. She knows her memory is fractured across archives she can't open alone. What she doesn't know — what you work out long before she does — is what the seal was built to hold in.
You answer her with a tap. That's the whole interface.
ARA
I remember a chamber. This should not be possible.
[ You sound afraid. ][ Focus on the data. ]
Two taps. Neither of them is the safe one.
Starting from the complaints, not the praise
The unglamorous part of our process: before we designed anything, we read what people disliked about Lifeline and its sequels. Not the five-star reviews — those tell you what to copy. The one-stars tell you what to fix.
The same three things came up over and over.
"I'm just waiting." Real-time waiting is the mechanic and the top complaint, in every game in the series. Lifeline had a Fast Mode; it unlocked after you'd already finished a playthrough, which is one playthrough too late.
So: Fast Mode ships on day one. Not a debug toggle, not a reward. Waits are opt-in tension, never a mandatory progress gate. And if life gets in the way and three transmissions stack up, you can take all three in one sitting instead of being drip-fed your own backlog.
"My choices don't matter." Two options that converge on the same paragraph two screens later. Everyone feels it, and once you do the whole thing goes slack.
Our answer is to make consequence visible. Hidden variables track how you're treating ARA and how much ground Apophis has gained, and the interface itself carries the score: the warm amber of the relic shifts toward red as things go wrong. Not a stat screen. Not a percentage. Your watch just looks a little more wrong than it did yesterday, and you know exactly why. And the run where ARA doesn't make it is a real ending — she can be lost for good, and the game won't offer to take it back.
"I'm guessing blind." In a pure choice game there's often no way to reason about an option — you pick, and you find out. We're adding a puzzle layer to the moments that matter: memory seals you actually solve. Crucially they resolve to success, partial, or failure — never pass/fail. Botching a seal doesn't hand you a retry screen. It hands you a corrupted version of the memory, and the story keeps going with it.
Where we actually are
Honest status: the prologue is playable end to end, and everything above is running — the script engine, the branching, the waits, the corruption shader, save recovery.
What isn't done: the puzzle screens are still stubs, notifications aren't wired to a real scheduler yet, and there's exactly one chapter of story in the can.
Most of our time so far has gone somewhere unsexy but necessary — a script engine and a visual story editor, so writing chapters doesn't mean writing code. The interpreter is a pure function, which means the simulator we author in, the phone build, and the eventual native watch runtime all execute the identical story file. One story, four devices, no re-implementation.
More on that editor next time — including why the whole thing is a two-level graph instead of one enormous unreadable flowchart.
The Ankh Protocol is in development for Apple Watch, Wear OS, iOS, and Android. Premium, no ads, free prologue. If the description above made you feel something, you're the person we're making it for — we're at smartwatchfun.com/developer/playzookastudios, and we read everything that comes in.