Dice Lock now installs and plays like a real iPhone appDice Lock now installs and plays like a real iPhone app

September 26, 2026 · The dice game left the browser for a native iPhone build, and an audit inside my own ticket pipeline caught three features that had skipped being built at all.The dice game can now be installed like a real iPhone app, and my own automatic checker caught three features that had never actually been built.
last updated

Dice Lock ships as an iPhone app

The game left the browser today. A Capacitor shell now wraps the same served tree the browser version already runs. It's not a rewrite: the same 72 TypeScript modules, stripped down to plain JavaScript the same way a browser request already strips them. WKWebView, the browser Apple's apps use to show pages, reads a .ts extension and assumes a video stream, refusing the file before it reads a byte of it, so every import between those modules had to move two characters, .ts to .js, without touching a line of logic. Native touches followed: a haptic buzz on a die locking, a board clearing, a chain multiplier, and a win; a screen that stops dimming itself while a board is in play; an ambient audio session that still answers with the phone's ringer silenced but never talks over whatever music is already playing; and a debug panel gated to a TestFlight-only build so it can never reach the App Store version.

Shipping through Apple's store means answering to Apple's rules and not just the game's own. Guideline 5.1.1(v) requires that anyone who can create an account in an app can delete it from inside that same app, so a DELETE ACCOUNT button now sits on the Account screen, removing the Clerk sign-in and every database row filed under it in one transaction. Building that route was the first place the game's code needed its own Clerk secret key, and that key turned out to have been sitting live in this repo's git history since an old commit, where the file was only ever meant to hold a placeholder. The exposure was confirmed before anything else happened: the old key still answered a real Clerk API call. It doesn't anymore. The key was rotated today, the old value now gets 401, the new one lives in the machine's own secret vault rather than any repo, and nothing on the running server needed to change, since it checks sign-ins against Clerk's public keys and never held the secret itself. Whether anyone used the old key while it was live is still unknown. The rotation closes the door without answering that.

Finding an account at all had been the harder problem before today: the only way in was a setting nobody noticed. A one-word identity chip (GUEST, a name, or SIGNED IN) now sits in the main menu's corner, and the very first screen a new player sees offers a quiet third option, "Played before? Sign in," next to the tutorial and play buttons.

A two-part tutorial, and a bug that let pieces of it skip the workshop

The eighteen-step tutorial that taught the whole game in one sitting is now two: Basics, everything a solo player needs, and Battle, everything that needs an opponent, split automatically by which modes an ability appears in rather than typed by hand into a list. Finishing either section now draws its own full-page send-off (NICE WORK for Basics, YOU'RE READY for Battle) instead of returning to the title screen under a completion blurb that used to claim "every trick in the game" while half the lessons sat unopened. Each section earns its own Records-screen achievement, and its own unlockable world skin, the Chalkboard and the Colosseum, worn straight off the send-off page.

Three of those pieces almost didn't get built at all. The pipeline that turns a Linear ticket into code has an auditor role that checks a delivery role's work before anything is called done, and today it caught the sign-in offer, both new worlds, and the Basics send-off page arriving on its desk with nothing behind them: no branch, no commit, no comment, the feature simply missing from the tree. It flagged what looks like a routing bug, tickets reaching the auditor having skipped delivery entirely, without fixing that bug, and sent each ticket back. All three landed later the same day. A fourth ticket caught the same way, about how the tutorial explains its own hero card, is still sitting unbuilt.

The dice game becomes a real iPhone app

The game left the web browser today. It now runs inside a wrapper, built with a tool called Capacitor, that lets the same game already working in a browser be installed and run like a normal iPhone app instead. It's not a rewrite. It's the exact same files, converted the same way they already are before a browser shows them. Apple's app browser refuses to open one of those files in its original form, guessing from the file name that it's a video, so every link between the files had to be renamed to match. A few small touches make it feel like a real app: the phone buzzes when a die locks, a board clears, a combo lands, or you win; the screen stops dimming itself mid-game; sound keeps playing with the ringer on silent, without cutting off music already playing; and a hidden debug screen shows up only in test versions, never in the App Store copy.

Selling through Apple's store means following Apple's own rules, not just the game's. One rule says an app that lets someone create an account has to let them delete it too, so there's now a DELETE ACCOUNT button that removes the sign-in and everything tied to it in one step. Building that button was the first time the game's code needed its private password for the sign-in service, Clerk. That's when it came out that a real, working copy of that password had been sitting exposed in this project's saved history since an old commit, in a file meant to hold a placeholder. Before anything else, that exposure was checked: a real request to the sign-in service with the old password still worked. It doesn't anymore. The password was changed today, the old one now gets rejected, and the new one is stored in a separate secure vault rather than any project file. Nothing on the server needed to change: it only checks a sign-in against public information and never held the password. Whether anyone used the old password while exposed is unknown; changing it closes the risk, not the question.

Finding your account at all used to be the harder problem: the only way in was a setting nobody noticed. A one-word badge (GUEST, your name, or SIGNED IN) now sits in the main menu's corner, and the first screen a new player sees offers a quiet third choice, "Played before? Sign in," beside the tutorial and play buttons.

A tutorial split in two, and a bug that let some of it skip the workshop

The eighteen-step tutorial that used to teach the whole game in one sitting is now split in two: Basics, everything a player learns alone, and Battle, everything that only matters once a computer opponent is involved. The game decides automatically which half a new move belongs in, rather than someone typing it into a list by hand. Finishing either half now shows its own full-page screen (NICE WORK for Basics, YOU'RE READY for Battle) instead of dropping the player back at the title screen under a message that used to claim it taught "every trick in the game" while half the lessons were still locked. Each half earns its own badge on the Records screen, and its own reward: a new look for the board, the Chalkboard for Basics and the Colosseum for Battle, worn straight from the screen that announces it.

Three of those pieces almost never got built. The automated system that turns a ticket into working code has a checking step: before any finished work is trusted, a separate role reviews it against what was actually written. Today that reviewer caught three tickets (the sign-in offer, both board looks, and the Basics screen) with nothing behind them: no code, no record of anyone working on them. It flagged a likely bug in how tickets get assigned, letting work skip building and go straight to review, without fixing it, and sent all three back. All three were finished later the same day. A fourth ticket caught the same way, about the tutorial's own hero-card explanation, is still unbuilt.