Phone-to-phone transfer

How it works

Nearby tools need proximity. A link needs a network and leaves a server copy. Platform gaps are normal: AirDrop will not see an Android phone.

Two iPhones AirDrop a 40 MB PDF in the lobby. An Android recipient in the same lobby gets a link instead. The PDF arrives both ways. Only the link has an expiry and a log.

How it differs

Phone-to-phone is not a backup. Neither device is a system of record unless a sync product copies it off.

A receive prompt accepted by habit takes a file from a nearby stranger.

Read the sender name.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For phone to phone transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive phone to phone transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.