Documenting Automatic Backup as Observable States

Support becomes easier when “automatic backup” is represented as observable states instead of a boolean. The useful sequence is desktop ready, paired, automation enabled, same network, and one file received. State 1: trigger enabled Automatic Backup is a manual setting. Installing or pairing the apps does not enable it by itself. State 2: network qualified Automatic upload requires the phone and computer to share a network. Initial setup needs internet; after setup, same-LAN Automatic Backup and file access can work without public internet. State 3: background capable Screen-off LAN transfers and background transfers are paid capabilities in the official build. An app-open test should not be generalized to every background state. State 4: file received The smallest reproducible test is one new photo with a known timestamp and an opened destination file. Phone and computer deletions are independent, so this is not full two-way sync. A support report should include operating systems, build versions, network state, destination type, and the last visible state, while omitting credentials, connection codes, IP addresses, and private paths. Disclosure: I work on LynavoDrive. FAQ: https://drive.lynavo.io/download.html?utm_source=devto&utm_medium=article&utm_campaign=automatic_backup_faq_20260807 Top comments (0)