A Smoke Test for Automatic Phone-to-Computer Photo Backup

Treat automatic backup as a workflow to observe, not a toggle to trust. A useful smoke test has three preconditions and one observable result.

Preconditions

1. The desktop app is installed and the receive folder is known.
2. The mobile app is paired and Automatic Backup is enabled manually.
3. The phone and computer are on the same network.

Create one new photo with an obvious timestamp. The test passes only when the destination file exists and opens on the computer.

This small test is easier to diagnose than importing an entire library. It also exposes product boundaries: initial setup requires an internet connection; after setup, same-LAN Automatic Backup can work without public internet access. Original files are transferred without intentional compression, while actual behavior depends on devices, network, storage, and file characteristics.

Do not infer background behavior from an app-open test. Screen-off LAN transfers and background transfers are paid capabilities in the official build. Phone and computer deletions are independent, so the result is not full two-way sync.

The general engineering lesson is simple: make the first successful state observable, test one known input, and record the environment before scaling up.

Disclosure: I work on LynavoDrive. Setup guide: https://drive.lynavo.io/download.html?utm_source=devto&utm_medium=article&utm_campaign=automatic_backup_checks_20260806