Designing a Deterministic First-Backup Runbook
Turn a two-device onboarding flow into observable checkpoints.
The first successful backup should be a deterministic runbook, not a hopeful wait after enabling a switch.
Checkpoint 1: destination ready
Install the desktop app first. Select the receive folder and prepare the connection code. The destination should exist before the source device attempts to pair.
Checkpoint 2: devices paired
Install the mobile app, select the intended computer, and enter its connection code. Pairing proves the relationship between devices; it does not yet prove that Automatic Backup is enabled.
Checkpoint 3: automation enabled
Enable Automatic Backup manually. Keep the phone and computer on the same network.
Initial setup requires public internet access. After setup, same-LAN Automatic Backup can work without public internet access. Model those as separate network checkpoints.
Checkpoint 4: first object observed
Create one new photo and confirm that it appears in the receive folder and opens on the computer.
The file is transferred in its original form without intentional compression. Actual behavior still depends on the devices, network, available storage, and file.
Record semantic boundaries
Phone and computer deletions are independent, so the workflow is not full two-way folder sync. Screen-off and background transfers are separate paid capabilities in the official build.
A passing first-run check confirms the path. It does not turn one computer copy into complete disaster recovery.
Disclosure: I am part of the LynavoDrive team. https://drive.lynavo.io/download.html?utm_source=hashnode&utm_medium=article&utm_campaign=first_backup_setup_20260803