Pairing answers who; acceptance answers what
Pairing is the decision to recognize a particular device and account on a future connection. Accepting a file offer is the decision to receive a particular package now. Those decisions have different lifetimes. You may work with a consultant for a year while wanting to receive only the report discussed in today’s meeting. Remembering their device should make the next meeting easier without silently turning every later offer into an accepted transfer.
Treat the first connection as an identity check
A list of nearby phones is a useful starting point, especially in a busy office, but device names can be similar. In ZipPigeon’s upcoming Nearby flow, both people sign in, unlock their workspace, and choose to turn sharing on in a compatible iOS app. On the first connection, check the displayed account and device, compare the complete pairing code together, and confirm on both phones. If something does not match, stop and select the intended device again.
Remember the particular accounts and devices
An approved pairing applies to the devices and accounts that made it. A later connection with those same identities can skip another code comparison while both approvals remain valid. Signing in to a different account or resetting a device’s sharing identity requires another pairing. The same person’s replacement phone also needs its own connection to be approved. This makes returning visits quicker without assuming that a familiar name on any phone represents the same relationship.
Keep the receiver in the loop for every package
Before accepting, the receiver should check who is sending and whether the file title matches what they expect. ZipPigeon Nearby asks for acceptance on every offer, including offers from remembered devices. Declining or leaving an offer unanswered does not release file access. The sender can clarify the package and make another offer when the receiver is ready. Pairing should remove repeated setup, while the visible decision about the files remains part of the conversation.
Use the right control when the relationship changes
Several everyday events call for different actions. You do not have to delete an account or its files to stop recognizing a nearby device.
- At the end of a meeting, turn sharing off to stop being available for Nearby handoffs.
- When a device should no longer be remembered, forget its pairing. Both people will need to confirm a new pairing before another handoff.
- When retiring a phone, remove it from your sharing devices to revoke its Nearby identity and associated pairings.
- When deliberately replacing this phone’s sharing identity, reset it and pair again with the people you still want to recognize.
A saved pairing is not permission to browse an account
Remembering a Nearby device does not make the other person a member of your workspace or grant access to your stored transfers. File access is a separate decision. It also has separate limits once delivered: a recipient can keep a downloaded copy, and a full file link with its decryption key can be passed to someone else. Expiry, download limits, and revocation apply to service access; pairing does not add a promise that files can never be copied or forwarded.
What to expect before the public launch
ZipPigeon’s apps are coming soon, with no announced public release date. Compatible native test builds can exercise Nearby now; operational controls stay hidden in ordinary browsers during prelaunch. Browser workspace access is planned for after app-store availability. Both participants need internet access because account verification and encrypted file delivery use the service. Precise distance guidance on supported phones can help locate a device, but it does not replace checking identity or accepting the package.