Dice Lock built its Android app from scratch in a single dayDice Lock built its Android app from scratch in a single day

October 17, 2026 · The game picked up a full Android shell today, native sign-in and all, while a bug that let an opponent steal your win and your leaderboard spot got closed.The game gained a full Android version today, including its own sign-in, while a flaw that let an opponent steal your win and your leaderboard spot got fixed.

A real Android app, built in a day

Dice Lock has run on iPhone and in the browser for a while. Today it picked up Android legs: npx cap add android turned the same Capacitor shell that ships the iPhone build into an Android one, locked to portrait the same way, with a signed build pipeline that produces a signed .aab the way the iOS script already produces a signed .ipa, down to the same refusal to build from a dirty tree.

Signing in on Android took two different shapes. Google sign-in goes through Credential Manager, Android's native account picker, and never leaves the app. Apple sign-in opens in a Custom Tab, Chrome running inside the app's own task but not inside the app itself, showing Apple's own page with Apple's own address bar rather than one dressed up in the game's colours. Google falls back to that same Custom Tab path when Credential Manager isn't available. The back button needed its own handling: Android hands the system back-press straight to the app with no default behaviour attached, so a screen with no listener used to close the whole app out of the middle of a match. It now pauses the match, backs up a screen, or exits, depending on what is on screen.

A lobby link on the website now opens the Android app directly, the same way it already opened the iPhone one, through a signed file that lists the app's fingerprints and tells Android the link belongs to it. The splash screen stays up until the page has actually painted, with its own timer starting on the page's second frame instead of guessing how long a cold start takes.

An opponent could steal your win

A review of the multiplayer code turned up a real hole. In a match, the only thing identifying your seat was your visitor ID, and that same ID gets sent to your opponent as part of the match state. If your connection dropped, your opponent had a ten-second rejoin window in which they could use your own ID to claim your seat and get themselves recorded as the winner. The same ID doubled as the device ID a Daily puzzle's leaderboard row was keyed on, so anyone who had played you could post a Daily score under your account. Seats are now claimed with a server-issued key instead of the visitor ID, and the Daily row is keyed on the account rather than the device.

The same pass closed three smaller gaps. Sign-in rate limits now check the address Railway actually saw the request arrive from, rather than trusting a header the client could set itself. Usernames are normalised to one script with no formatting or direction characters, so a lookalike name cannot impersonate a real one. And an exception's own text no longer reaches a player's screen, where it could leak detail about why something had failed. All of it, plus a floor-card redesign and a moves-left counter on puzzle boards, shipped as TestFlight build 25.

Build 26 followed it a few hours later with a new preview of a world's boards, and went to Apple for review at 00:11 UTC. The first submission attempt was refused: Apple's API said the privacy label was not published, even though it had been filled in. The answers had been saved but never pushed through the final Publish button. Fixing that and resubmitting got it to Waiting for Review, where it sits until Apple responds.

A real Android app, built in a day

Dice Lock has been an iPhone app and a website for a while. Today it also became a working Android app, built from a standing start in a single day. The same wrapper that already packages the iPhone version as an app was used to make an Android version too, locked to hold the phone upright the same way, with a signed build file for Android to match the one the iPhone version already had.

Signing in on Android needed two different approaches. Signing in with Google happens through Android's own built-in account picker, so the app never has to open a separate window for it. Signing in with Apple opens a small browser window inside the app that shows Apple's own page, with Apple's own address, rather than being dressed up to look like part of the game, so nobody can mistake it for a fake page. Google uses that same browser window as a backup if the built-in picker is not available. The phone's back button also needed its own handling: on Android, pressing back normally closes whatever app is open, and without extra work it would have slammed a player straight out of a match in progress. It now pauses the match, steps back one screen, or closes the app, depending on what you are looking at.

A link to your lobby on the website now opens the Android app directly, the same way it already opened the iPhone app, through a small signed file that proves the link is allowed to open that app. The loading screen also now waits until the page underneath has actually finished drawing itself before it disappears, timed from the moment the page draws its second frame, rather than guessing a fixed amount of time and hoping that was long enough.

An opponent could steal your win

A check of the code behind online matches turned up a real problem. The only thing proving which seat was yours in a match was a visitor ID, and that same ID was sent to the person you were playing against as part of the match information. If your connection dropped, your opponent had a ten-second window to rejoin in your place, and during that window they could use your own ID to take over your seat and have themselves recorded as the winner instead of you. The same ID also doubled as the ID used to track your score on the Daily puzzle leaderboard, so anyone who had played against you could post a Daily score as if it were yours. Seats are now claimed with a secret key the server hands out instead of that visitor ID, and the Daily leaderboard now tracks your actual account instead of your device.

The same round of work closed three smaller gaps. The limit on how many sign-in attempts someone can make now checks the real address a request came from, instead of trusting information the person making the request could fake. Usernames are now cleaned up so they only use one consistent writing system with no invisible formatting characters, which stops someone from registering a name designed to look identical to someone else's. And when something goes wrong on the server, the error's own technical details no longer get shown to the player, where they could leak information about why it failed. All of this, along with a redesigned display for puzzle floors and a counter showing how many moves are left on a puzzle, went out as a test build, numbered build 25.

A later build that day, build 26, added a new preview of a world's boards and was sent to Apple for review at 00:11 UTC. The first attempt to submit it was turned down: Apple's system said the required privacy information had not been published, even though it had already been filled in. It turned out the answers had been saved but the final step to actually publish them had never been pressed. Fixing that and sending it again got the app into Apple's review queue, where it now waits for a decision.