Text roadmap: expand any node to read its details.
Device discovery and trust
Device discovery and trust · Validated
Discover devices, verify identities and establish trusted connections.
Development builds · 11–12 Sep 2026 · SDK tests on physical devices and UI regression tests
Completed validation
- All three local-network pairings between Android, iOS and macOS completed discovery and security-code confirmation on both ends.
- Device names, local labels and duplicate discovery entries have dedicated regression coverage.
Current limitations: This stage summarizes the scope verified for its child nodes. It does not certify every device model or complete user workflow.
Next steps: Validate first-time pairing with more routers and system permission states.
Local-network discovery · Validated
Find devices available for pairing on the same local network.
Development builds · 11–12 Sep 2026 · Three-platform device tests and regression tests
Completed validation
- A Mac, Pixel 7 Pro and iPhone SE discovered and connected to one another on the same Wi-Fi network.
- Regression tests cover merging duplicate entries for authenticated devices, recovery windows and retaining newly discovered devices.
Current limitations: Network isolation and app network permissions can affect discovery. Finding a device does not establish trust.
Next steps: Test more routers and permission-denial followed by reauthorization.
Security codes and pairing · Validated
When pairing a new device, verify the security code and confirm on both ends.
Development builds · 11–12 Sep 2026 · Local-network and relay diagnostic experiments
Completed validation
- All three local-network pairings and the cellular relay experiments completed matching security codes and confirmation on both ends.
- Regression tests passed for packet loss during pairing and early confirmation.
Current limitations: Device names are not proof of trust. Identity verification is retained for relay connections.
Device names and local labels · Validated
Set a device name and add labels for paired devices that are visible only on your device.
Development builds · 12 Sep 2026 · SDK and UI regression tests, plus selected Android interactions
Completed validation
- SDK tests verified that renaming preserves identity and relationships, and updates the name on the peer after reconnection.
- UI tests cover editing and clearing labels and handling failed saves. The Android client entry points were checked.
Current limitations: Name and label editing on iOS has not been manually validated step by step. Labels only affect local display.
Files and messages
Files and messages · Validated
Exchange messages, images and files in a device conversation.
Development builds · 11–12 Sep 2026 · Three-platform SDK tests and selected client workflows
Completed validation
- Bidirectional messages and file integrity checks passed for all three local-network platform pairings.
- In-conversation file controls, image cards and input interactions have regression coverage and manual experience checks.
Current limitations: SDK transport tests and complete client workflows are validated separately. System file selection, saving and background transfers still have cases to cover.
Next steps: Test the complete workflow from selecting a file to opening it on the receiving device in the next release candidate.
Messages and images · Validated
Send text and images, and browse conversation history on your device.
Development builds · 11–12 Sep 2026 · Three-platform SDK messaging and selected client image workflows
Completed validation
- Bidirectional messaging passed for every pairing of the three platforms on a local network.
- A Pixel sent an image to a Mac with matching content checks; its history entry was not duplicated after restart.
Current limitations: The image workflow above covers Pixel → Mac. The iOS photo-library entry point has not been validated step by step.
Next steps: Cover more image-sending directions, platform combinations and photo-library permission states.
File transfers · Validated
Select files in a conversation, view progress and receive files.
Development builds · 11 Sep 2026 · Same Wi-Fi network, product SDK in separate test apps
Completed validation
- Mac ↔ Pixel, Mac ↔ iPhone and Pixel ↔ iPhone each completed a 32 MiB file transfer in both directions.
- Independent SHA-256 checks matched for the actual received files in all six transfers.
Current limitations: This experiment does not replace full-client acceptance testing for file selection, external saving, background resumption or restart recovery. It is not a transfer-speed promise.
Next steps: Validate selection, sending, receiving, opening and interruption handling in the next release candidate.
Android, iOS and macOS · Validated
Android, iOS and macOS completed local-network interoperability experiments on physical devices.
Development builds · 11 Sep 2026 · Mac, Pixel 7 Pro and iPhone SE
Completed validation
- All three pairings completed discovery, security codes, bidirectional messages and bidirectional file verification.
- Each device held two online sessions at once; the data paths were confirmed to use Wi-Fi.
Current limitations: Development interoperability tests and final-product smoke checks are recorded separately. iOS is supplied privately through Ad Hoc packages for registered devices; no universal public IPA.
Next steps: Cover more device models and repeat full-client acceptance tests on final release candidates.
Bluetooth short messages · Validated
Exchange authenticated short text and delivery receipts between nearby devices over Bluetooth.
Development builds · 16 Sep 2026 · Android, iOS and macOS nearby tests
Completed validation
- Messages and receipts were checked in all six directions with only Bluetooth available to the phones.
- Over-limit requests were rejected, and subsequent normal messages still worked.
Current limitations: Bluetooth does not carry files and does not guarantee background availability or arbitrary range. Repeated new pairings, recovery and final product workflows have remaining cases.
Next steps: Complete role combinations, recovery and product-workflow checks for the nearby candidate.
Reliability and release validation
Reliability and release validation · Next
Current focus: free local-network files and messages, Bluetooth short text, reliability and release validation.
Planned work
- Expand coverage across networks, devices and permission states.
- Test recovery after network changes, disconnects and returning to the foreground.
- Collect RC1 installation and usage feedback and cover remaining candidate scenarios.
Current limitations: RC1 is available and reliability validation continues. Each release’s notes define its scope.
Network compatibility · Next
Expand real-network coverage using default configurations.
Planned work
- Test more home Wi-Fi, hotspot and mobile-network combinations.
- Record direct, relay, permission-denial and network-isolation results separately.
Current limitations: Not all carriers, network combinations or public address families have been covered.
Network and interruption recovery · Validated
Validate interrupted-file resumption and automatic recovery when phones return to the foreground.
Development candidates · 16 Sep 2026 · Isolated tests on Mac, Pixel 7 Pro and iPhone SE
Completed validation
- File tasks resumed automatically after process interruption, retained their original task IDs and passed integrity checks.
- Bidirectional Pixel-to-Mac/iPhone files resumed after Wi-Fi interruptions and passed checksum checks.
- After 30-second, 2-minute and 10-minute locks, iPhone recovered automatically with queued messages and original contacts retained.
Current limitations: Recovery stress tests used isolated hosts with the same SDK as RC1. Final ordinary products received upgrade and communication smoke checks only. Other devices, background durations and Mac sleep remain to be covered.
Next steps: Complete the remaining cases against explicitly identified devices and release builds.
Installation, upgrades and release · Validated
The free nearby 0.1.0-rc.1 candidate is available.
RC1 · 16 Sep 2026 · Build 10 · Mac, Pixel 7 Pro and iPhone SE
Completed validation
- Final signed packages retained existing contacts and chat history after upgrades on all three devices.
- Final-product messages and receipts passed Mac → Pixel → iPhone → Mac; a Chinese-named file was received and opened on Pixel from Mac.
- Android uses the release key; macOS uses Developer ID signing and Apple notarization; iOS uses private Ad Hoc distribution to registered devices.
Current limitations: Public downloads are 0.1.0-rc.1 for Android arm64 and Apple Silicon macOS. There is no universal public iOS IPA. This is not a stable release or a claim that the full test matrix passed.
Next steps: Extend permission, device and background coverage. Fixes receive new release tags.
Cross-network exploration (deferred)
Cross-network exploration (deferred) · Experiment record
Earlier direct-connect and encrypted-relay experiments remain documented. The free nearby release takes priority.
Development builds · 12 Sep 2026 · Network experiments on physical devices
Completed validation
- A Pixel on cellular and a Mac on Wi-Fi exchanged short messages in both directions through a relay node.
- Both initiation directions completed matching security codes and confirmation on both ends.
Current limitations: The experiments used separate diagnostic apps. They do not establish that the full client invitation workflow has passed acceptance testing, or guarantee connectivity on every network.
Next steps: Complete the local-network and Bluetooth release first; cross-network work is deferred.
Cross-network direct connections · Experiment record
Attempt a direct connection between devices on different networks.
Development builds · 11 Sep 2026 · Selected cellular and Wi-Fi combinations
Completed validation
- Selected cellular and Wi-Fi combinations with an IPv6 path completed security-code confirmation and bidirectional short messages.
- IPv4 cellular direct-connection failures were also recorded. A successful case does not establish universal reachability.
Current limitations: These were diagnostic experiments under specific network conditions. The website does not ask users to change access-point settings or promise direct connectivity with every default configuration.
Next steps: Further work is deferred while the local-network and Bluetooth release takes priority.
Optional encrypted relay · Experiment record
When a direct path is unavailable, both participants can explicitly choose a relay connection.
Development builds · 12 Sep 2026 · Pixel cellular ↔ Mac Wi-Fi, separate diagnostic apps
With consent from both participants, a relay node forwards end-to-end encrypted data. Both ends still verify the security code.
Completed validation
- Both initiation directions completed matching security codes, confirmation on both ends and short-message delivery in both directions.
Current limitations: The full client invitation workflow still needs acceptance testing. The cellular experiment did not test files. There is no default automatic fallback, automatic node failover or relay-to-direct upgrade.
Next steps: Further work is deferred while the local-network and Bluetooth release takes priority.
Volunteer a relay node · Experiment record
After explicitly enabling it, provide limited relay service for other SovKit users.
Development builds · 12 Sep 2026 · Node regression tests and selected client UI checks
Off by default. Enabling it explains bandwidth and battery use and sets a rate limit and per-run data cap. A device is listed as available only after an external send/receive check.
Completed validation
- Regression tests passed for forwarding, revocation, data caps and withdrawal when backgrounded.
- The Android settings entry and default-off state were checked. The page shows availability or pause reasons and current-run data use.
Current limitations: Phones contribute only in the foreground on Wi-Fi or Ethernet marked unmetered by the system; unknown status pauses service. This does not guarantee zero charges. Disabling service or reaching the cap stops it. Pausing preserves the count; restarting restores the agreed settings and starts a new count.
Next steps: Further work is deferred while the local-network and Bluetooth release takes priority.
User-controlled device collaboration
User-controlled device collaboration · Long-term goals
Connect your own devices, and the people you trust.
Goals and open questions
- Develop collaboration scenarios around trusted devices.
- Explore availability with multiple voluntary nodes.
- Enable more clients and persistent hosts to participate.
Current limitations: These goals do not imply that remote device management, offline delivery or cross-device history synchronization already exist.
Trusted-device collaboration · Long-term goals
Develop collaboration around your own devices and trusted contacts.
Goals and open questions
- Choose device-collaboration scenarios based on real needs.
- Provide clear consent and exit controls for new capabilities.
Current limitations: This does not imply existing remote desktop, system device management or identity export features.
Multi-node availability · Long-term goals
Explore connection availability with multiple voluntary nodes.
Goals and open questions
- Study what happens when nodes join, leave or become temporarily unavailable.
- Build recovery and alternative-path tests on the existing single-session relay experiments.
Current limitations: Automatic failover, offline delivery and replicated storage are not delivered capabilities. Permanent availability is not promised.
More clients and hosts · Long-term goals
Bring shared collaboration capabilities to more clients and persistent hosts.
Goals and open questions
- Start with the existing mobile clients, desktop clients and persistent nodes.
- Determine suitable capabilities for each host based on its platform’s operating conditions.
Current limitations: A shared core does not imply identical runtime, background or distribution support on every platform. The full SDK and persistent node require separate release validation.
Nearvia