“Open a computer file on my phone” looks like one feature, but the implementation depends on where the authoritative copy lives.
If email, chat, or cloud storage is the transfer path, the system creates or uploads another copy. If the computer remains the source of truth, the phone becomes an authorized client and the computer becomes an availability dependency.
A useful state model is:
computer-online -> client-running -> device-authorized -> network-qualified -> file-readable
For LynavoDrive, initial setup requires internet and an initial same-LAN connection. After setup, LAN file access can work on the same local network without public internet. Cross-network access is paid, may use an encrypted relay, and still requires the computer to remain online. The server retains account information but not file content.
The minimal verification is one non-sensitive file in a non-hidden directory. Browse to it from the phone, download it, and open it. Record the last visible state if the test fails.
Deletion semantics belong in the model too. LynavoDrive keeps phone-side and computer-side deletions independent, so direct access is not full two-way folder sync.
The architecture lesson is simple: define the source of truth first, then make availability, authorization, network path, and deletion behavior explicit.
Disclosure: I work on LynavoDrive. Current setup: https://drive.lynavo.io/download.html?utm_source=devto&utm_medium=article&utm_campaign=phone_computer_access_20260810
Top comments (0)