Cadence keeps repertoire, practice sessions and recorded progress on your device. Local practice does not require an account or a live internet connection. To protect that record, export a backup file and keep a copy outside the device. The current web app also supports cloud backup and sync when enabled for your signed-in account; keep the separate file export for recovery.
Android and the web have different first-load requirements
The Android app bundles its application assets and fonts. Once it is installed, its local practice screens do not need to download those assets at each launch. You can work with pieces, plans, practice history and local file backups when you are disconnected.
The web app needs an initial successful online load so its PWA can cache the application assets. Open the app while connected before relying on it offline. A failed first visit is not the same as a ready offline installation.
Installing a PWA gives you an app window and a convenient launch point. It does not create a cloud account or make local data permanent. Browser storage can still be cleared by the user, a profile reset or a device change.
What you can do without signing in
Local repertoire, planning, practice sessions and progress use the same local record whether you are connected or not. Reconnecting should not replace that work with a blank account state.
An account is a separate server identity. Registration, email verification, password recovery and other account operations need a connection. If one of those operations fails because you are offline, return when a connection is available. You can continue local practice meanwhile.
The current web app supports signed-in cloud backup and sync when available for your account. Use the same account on your other web/PWA device. Check the cloud status and resolve any account or copy conflict before continuing. Older installed Android releases may have different capabilities; a separate exported file remains useful for recovery.
Export before you need the backup
Open Settings in Cadence and use the backup export action. Save the exported file somewhere you can find again. Keep another copy outside the device that holds the original practice record.
Do this before clearing browser data, uninstalling the app, changing devices or replacing the local record. A backup created after data has been removed cannot recreate what was already lost.
The backup can contain personal repertoire titles, notes and practice history. Treat it as personal information. Do not post it publicly or send it to an unknown person. If you choose a cloud drive or another storage provider, that provider’s access and privacy rules apply to the copy you put there.
The practice backup is distinct from the developer’s Android signing key and from the server’s account database. A player should use the in-app practice backup, not an application-build or administrator recovery file.
Restore is an intentional replacement
Select the backup file using the restore action in Settings. Cadence validates the artifact before applying it and asks for replacement consent. Read that confirmation: restore replaces the current local practice record rather than silently combining two histories.
Export your current record first if you might need it later. If the selected file is not the one you intended, cancel before confirming. If validation rejects the file, do not assume it was partly imported; keep the original file and check that it came from Cadence’s export action.
Older supported backup formats are handled by the app’s migration boundary. An unsupported or malformed file is not a reason to discard the current local record. Keep a copy of the file and contact support if you cannot identify the issue.
Check your copy with a small, clear routine
- Confirm that the exported file exists and has a recognizable name.
- Keep a copy outside the device, not only in its Downloads folder.
- When moving devices, retain both the source export and the destination’s earlier export until you have checked the restored record.
- After restore, inspect the expected pieces and practice history before deleting any old copy.
Do not test a restore over your only copy of important data. A deliberate replacement is useful, but it is not a synchronization or merge operation. Keeping the previous export is the recovery path if you chose the wrong file.
When storage or connectivity is unavailable
Private browsing, restricted storage or a full device can affect persistence. If Cadence reports a storage problem, avoid repeated resets. Follow the displayed recovery or export option and preserve the original data where possible.
Web offline access also depends on the cached application assets still being available. Clearing site data can remove both the cache and the local practice record. Reinstalling or revisiting online restores application files; it does not reconstruct deleted practice history without your backup.
This journal is a public website served from the backend. Its articles are not part of the practice app’s offline guarantee. Save a guide separately if you want to read it without connectivity.
Questions about accounts and recovery
Does signing out delete my practice? Accounts and local practice have separate responsibilities. Do not confuse account sign-out with the explicit local-data deletion or replacement controls.
Can I use two devices? The current web/PWA app can sync a signed-in practice backup between devices when cloud access is available for the account. Account and cloud operations require internet. File import remains a separate replacement operation, so keep the previous export before importing.
Where do I ask for help? Contact [email protected]. Describe the device, the action and the error message. Never include your password. Ask before sharing a backup that contains personal notes.
Keep one current export and one recoverable copy outside the original device. That is the practical protection available today.