What NectarLink is
The project covers notifications, messages, calls, clipboard, files, photos, screen mirroring and phone apps in windows, between Android and Windows 10 (2004+), Windows 11 or Linux. The developer says it came from juggling Phone Link for notifications and messages, KDE Connect for the clipboard and LocalSend for files, while wanting one app that did all of it.
MakeUseOf's author says he has almost stopped using LocalSend since installing NectarLink. That is one user's experience. He also admits to running into a few bugs, which fits an app this new.
Requirements
- Windows x64: Windows 10 (2004+) or 11, 64-bit Intel or AMD. Phone as webcam needs Windows 11.
- Windows on ARM: Windows 11 on ARM (Snapdragon).
- Android: Android 8.0 or newer.
The release page also shows the project is moving fast. The listed stable release is 0.1.5, and nightly builds of 0.1.6 are appearing almost daily. Nightly 9 was published on 12 November. The release notes describe nightly builds as a way to try new features that can bring "new bugs." Stay on the stable channel unless you want to test.
Setup
The project's guide gives these steps:
- Download the Windows installer from the project's GitHub Releases page. It is
x64-setup.exefor Intel/AMD orarm64-setup.exefor Snapdragon. - Run the installer. It isn't code-signed yet, so SmartScreen may warn you. Choose More info, then Run anyway.
- Allow the administrator prompt. Setup registers a Windows Firewall rule, adds shortcuts and sets the app to start in the tray at sign-in. You can turn that off under Settings > General.
- Install the Android APK from the same Releases page, or scan the QR code that Windows setup shows at the end.
- Pair the devices. You can scan the PC's QR code, or choose the PC from the phone's nearby list and confirm a six-digit code on both screens. A USB cable also works, but it needs Android's adb running on the PC.
- Grant only the Android permissions you want. Each feature has its own switch for each device, and the sensitive ones start off.
The project says the apps update from GitHub Releases and check downloads against SHA-256 sums.
The sideloading trade-off
NectarLink is not on Google Play. The guide says the full app is distributed as a signed APK because it uses permissions that Google Play restricts. Those include full SMS/MMS, call logs, notification actions, accessibility input and optional All files access.
Google Play Protect can get in the way. In markets where Enhanced Fraud Protection is on, including India, the guide says it blocks the APK with no "Install anyway" button. The project offers two workarounds:
- Install over USB with
adb install -rand the APK file. - Temporarily pause Scan apps with Play Protect, install, then turn it back on.
MakeUseOf's instructions only say to turn scanning off. The project's own wording says to turn it back on afterward, and that is the safer approach. I would use the adb route if you are comfortable with it. If you do pause scanning, re-enable it right after installing. Take the APK only from the official release page and compare its checksum. This is general security advice, not something the project requires.
Android 13 and newer add another step. The guide says the Notification access and Accessibility switches may be grayed out for sideloaded apps. To unlock them, open App info, tap the three-dot menu, choose Allow restricted settings and verify with your screen lock.
Privacy: what "local-first" means
MakeUseOf says there is no account and no cloud. The project's description is "Local-first, end-to-end encrypted, no account." The guide says that by default, traffic goes directly over your local network or a USB cable. Installed copies contact GitHub Releases over HTTPS only to check for updates.
The guide also lists "Connect over mobile data" as a network option, so the "no cloud" claim describes the normal setup, not every possible one. Pairing uses mutual Ed25519 keys and an end-to-end encrypted QUIC session. The README says keys are protected by Windows DPAPI and the Android Keystore.
Power levels and what they unlock
The guide describes three levels. Your choice decides how much access you hand over.
| Level | Setup | Notable capabilities |
|---|---|---|
| Standard | Ordinary Android permissions | Notifications, messages, calls, files. Phone-to-PC clipboard is manual. Mirroring is view-only. |
| Assist | Enable NectarLink in Android Accessibility | Tap, swipe and type on the mirrored screen from the PC |
| Elevated | One-time Wireless debugging pairing (Android 11+) or USB adb | Background clipboard sync, phone apps in their own PC windows, real touch input |
Two points follow from this table. First, the app-in-a-window feature that MakeUseOf highlights needs the Elevated setup, which is not the default. Second, opening a phone app in its own window with its own taskbar icon is a headline feature, but you have to opt in to the deeper access to get it.
How it compares with Phone Link
Phone Link asks for a Microsoft account at setup, according to MakeUseOf. NectarLink does not need an account. The cost is that you manage sideloading, permissions and updates yourself, instead of getting a Microsoft-supported app.
NectarLink is also not the only alternative. Android Police recently covered Sefirah, an open-source take on the Phone Link concept, which is on the Play Store and open-source repositories. Windows Central covered scrcpy, which mirrors a phone's screen on a Windows desktop. The Play Store route avoids the Play Protect problem entirely, though it may not match NectarLink's feature list.
Beware of look-alike repositories
A search for NectarLink turns up many forks. The original is thtbee/nectarlink, and the other repositories are forks of it. Some older forks describe a Windows 11-only build with different download tables. Use the original project's Releases page, not a fork.
A sensible way to try it
- Install the stable release, not a nightly.
- Pair over your home network and enable only notifications, clipboard and file transfer. MakeUseOf suggests the same order.
- Leave remote control, shell commands and phone-storage access off until you need them.
- Check the checksum on every download, and re-enable Play Protect if you paused it.
- Don't rely on it as your only way to receive one-time codes until you trust it.
Bottom line
NectarLink has a broad feature set, a clear permission model and active development. It is also young, unsigned on Windows, and sideloaded on Android with real permission trade-offs. It suits tinkerers who want more than Phone Link offers. Most other users should wait for a few more releases.