Keep the puzzle and its state near the player.
Core Android play is designed to function from local state: the board, progression, settings, and save/resume experience should not require a sign-in flow to remain meaningful.
Offline-first is a product boundary, not a slogan. This page separates the Android core experience from things that naturally require a network, and describes Recovery Vault as a device-change tool rather than account sync.
Core Android play is designed to function from local state: the board, progression, settings, and save/resume experience should not require a sign-in flow to remain meaningful.
Rewarded ads, updates, store delivery, public sharing, and other externally hosted services are separate from the logic board. When a reward ad is unavailable, the product should be clear about it rather than pretending a network promise exists.
Recovery Vault uses an encrypted export file, a chosen four-digit PIN, and a separate recovery key. A player must retain the file and both factors for a transfer; the app cannot reconstruct a lost key from a server it does not operate.
No. It describes the critical Android puzzle path and local state. Store delivery, updates, optional ad rewards, and public web pages necessarily rely on external systems.
No offline-web claim is made for this browser sample. It is a small online demonstration of the classic 9×9 rules.
No. It is a player-controlled encrypted device-change transfer path, not an account service or shared drive.
No. The product is designed so core play does not require a mandatory user account.