Expand items by topic to read validation records and planned work.
Device discovery and trust
Device discovery and trust · Tested subset
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 · Tested subset
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 · Tested subset
When pairing a new device, verify the security code and confirm on both ends.
Development builds · 11–12 Sep 2026 · LAN and relay diagnostic experiments; the relay experiment is not part of the RC1 installers.
Completed validation
- The three LAN pairings and a cellular relay experiment completed matching security codes and confirmation on both devices; the relay experiment is not part of the RC1 installers.
- Pairing packet-loss and early-confirmation scenarios passed regression checks.
Current limitations: Device names do not establish trust. The relay experiment is not part of the RC1 installers.
Device names and local labels · Tested subset
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 · Tested subset
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: Cover remaining ordinary-product file selection, saving and background workflows.
Messages and images · Tested subset
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 · Tested subset
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: Cover remaining final-product directions for selection, receipt, opening and interruptions.
Android, iOS and macOS · Tested subset
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: Expand device coverage and complete remaining ordinary-product workflows.
Bluetooth short messages · Tested subset
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 RC1 client workflows have remaining cases.
Next steps: Complete role combinations, recovery and product-workflow checks for the nearby candidate.
Validation and distribution
Validation and distribution · To do
RC1 is published. Work order: nearby acceptance, iOS distribution assessment, then DevTools platform validation.
Planned work
- Complete permission, discovery-failure and critical nearby acceptance checks.
- Assess future iOS distribution requirements; the store-submission process has not started.
- Continue DevTools cross-device acceptance and native Linux validation.
Current limitations: Work order may change with test results; no delivery dates are set. Folder sending is outside the plan; cross-network work and relay are deferred.
Network compatibility · To do
Broaden validation of local-network configurations and permission states.
Planned work
- Test more home Wi-Fi networks, hotspots and router configurations.
- Record recovery after permission denial, network isolation and discovery-failure states separately.
Current limitations: This work covers nearby communication, not cross-network direct connections or relay acceptance.
Network and interruption recovery · Tested subset
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: File-recovery stress checks used isolated hosts with the RC1 SDK. Lock recovery is a separately recorded tested subset. The RC1 client passed upgrade and send/receive smoke checks only; more devices, background conditions and Mac sleep remain untested.
Next steps: Complete the remaining cases against explicitly identified devices and release builds.
Installation, upgrades and release · Tested subset
The 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.
- 17 Sep 2026: Windows x64 ZIP and notarized macOS DMG added. Windows native build, package integrity and DLL loading checked; the macOS application is unchanged from RC1.
- A user reports working operation on a Huawei P20 and an HONOR smart screen. OS versions and the screen model remain unrecorded. This is user feedback, separate from automated acceptance evidence.
Current limitations: Public downloads are 0.1.0-rc.1 for Android arm64, Apple Silicon macOS (DMG) and Windows x64 (ZIP). 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.
iOS distribution assessment · To do
Currently Ad Hoc only, for registered devices. The store-submission process has not started.
Planned work
- Check entity, applicable filing and privacy-information requirements.
- Once requirements are clear, decide whether to begin store-build and review-material preparation.
Current limitations: No regions, review outcome or timing are promised. No store download link is available.
DevTools platform validation · Tested subset
macOS arm64 and Windows x64 builds, UI and local two-process communication have passed.
17 Sep 2026 · macOS arm64 Release / Windows x64 MSVC Debug · SDK 0.1.0 / ABI 25
Completed validation
- Both hosts passed SDK loading, Unicode paths, pairing, bidirectional delivery receipts and file integrity checks locally.
- GUI self-checks, identity reopening and wrong-password protection passed; source and validation records are committed in the DevTools repository.
Planned work
- Add cross-device LAN, Windows high-DPI and manual debugging checks.
- Validate native Linux builds before deciding its packaging requirements.
Current limitations: Communication checks used two processes on each host, not cross-device networking or desktop BLE radios. These checks used the corrected development SDK; RC1 client packages were not replaced.
Deferred scope
Deferred scope · Deferred
Cross-network connections, relay and providing relay nodes are outside RC1 and current priorities.
Current limitations: Previous development records are not current product capabilities or a commitment to a future release date.
Cross-network connections · Deferred
Direct internet-wide connections are not delivered in this release.
Current limitations: Current priorities are local-network and nearby Bluetooth communication; reachability across networks is not promised.
Relay (deferred) · Deferred
Current installers do not provide relay communication.
Current limitations: No cloud-hosted offline messages, automatic relay failover or guaranteed background delivery. Resuming this work requires a separate scope and validation criteria.
Providing relay nodes · Deferred
The current product does not offer devices as relay nodes for other users.
Current limitations: Outside this release and the next work items; no availability date is set.
Zhiyu