An Android phone with a MacBook for developers: codes, links, and files

Developers who carry an Android phone and work on a MacBook already have the best free tools for the hard parts: adb for builds and logs, scrcpy for the screen, and Chrome's remote debugging for web pages. What is missing is the everyday layer an iPhone owner gets from Apple for nothing: the login code that lands on the Mac, the link that opens on the other device, the copied token that pastes across. Free tools cover each of those one at a time. The Relay puts them in one Mac app for $19.99, paid once.

Publisher note: The Relay publishes this guide and is one of the products discussed. Details about other products come from each maker's own pages, checked on 1 October 2026. Prices and features change, so confirm before you buy.

What does the working day look like?

The MacBook is open with an editor, a terminal, and a browser full of tabs. The phone is face down beside it, or charging across the room. The Git host wants a code. A colleague messages a staging link to the phone. A build needs to go onto the phone, and a screenshot of the bug needs to come back. An error string copied on one device is needed on the other.

None of these takes long. Each one means picking up the phone, unlocking it, and losing your place.

Moment 1: the sign-in that texts you a code

Free fix. Keep Google Messages for web open in a pinned tab. Google says it works in Chrome, Firefox, Safari, or Edge. Better still, move the accounts you control to an authenticator app or a passkey. Google's passkey page describes signing in on a computer by scanning a QR code with the phone, with Bluetooth turned on.

With The Relay. An SMS that arrives on the phone shows up on the Mac, and a login code in it is copied to the Mac's clipboard so you can paste it. The steps and the trade-offs are in SMS verification codes from Android on a Mac.

Do not plan on a notification mirroring app for this. Google's Android 15 behaviour changes describe "redacting OTPs from notifications accessible to untrusted apps".

Moment 2: a link that is on the wrong device

Free fix. With Chrome on both and the same Google Account, Send to your devices pushes the tab across, and it opens in Chrome on the other device. For inspecting the page on the phone, Chrome's remote debugging lets you "inspect and debug live content on your Android device from your development machine" over a USB cable, through chrome://inspect#devices.

With The Relay. Share a page from the phone and it opens in the Mac's default browser, and the other way round. That matters if your default is Safari or Firefox, or if you test in a browser other than Chrome on the phone. More in send a link from Android to a Mac.

Moment 3: builds, screenshots, and logs

Free fix. This is adb's job and nothing beats it. Google's adb documentation covers adb install, and adb pull and adb push to copy files to and from a device. It also says phones on Android 11 or later can be debugged wirelessly once paired with a QR code or pairing code, as long as the workstation and the device are on the same wireless network. If you would sooner drag files in a window, OpenMTP is a free file browser for the Mac that works over a USB cable.

With The Relay. A window on the Mac browses the phone's storage, and you drag files either way over the local network. It suits the non-developer files: a design export, a PDF, a folder of test images. It does not replace adb. All the routes are in every way to transfer files from Android to a Mac.

Moment 4: something copied on one, needed on the other

Free fix. KDE Connect is free and open source, and its download page lists a stable release for macOS. Its wiki says text copied on the computer is immediately available on the phone, and that sending the other way on Android 10 or later means tapping a "Send Clipboard" button, because Android stops background apps from reading the clipboard. If scrcpy is already running, its README lists copy-paste in both directions.

With The Relay. Clipboard sync works both ways, for text, images, and links. Details and a five-minute test are in clipboard sync between Android and a Mac.

Moment 5: the phone buzzing while you are in the middle of something

Free fix. KDE Connect's home page lists phone notifications synced to the desktop, and its wiki describes notifications for incoming calls. See Android notifications on a Mac.

With The Relay. The phone's notifications appear as Mac notifications, and an incoming call shows on the Mac, where you can accept or decline it.

How do the moments add up?

If you are comfortable assembling tools, the free column is a complete setup. The Relay is for the developer who wants the everyday rows to work without thinking about them.

What will The Relay not do for you?

• It is not a developer tool. No adb, no APK install, no screen mirroring, no remote control. Keep adb and scrcpy.
• It has no USB mode. It talks over your own Wi-Fi network, with Bluetooth as a fallback.
• It does not work across the internet. The phone and the Mac must be on the same local network or in Bluetooth range. The NearDrop README notes that local network communication "may not work on some public networks". Test on the network you actually work on.
• It does not send texts from the Mac. It shows incoming ones. Google Messages for web sends.
• It is not free and not open source. KDE Connect is both.
• Check your employer's rules before you put any phone-syncing app on a company Mac. That applies to every tool on this page.

Your clipboard, files, texts, and notifications travel directly between your phone and your Mac over your local network. They are not uploaded to The Relay's servers. The privacy policy has the detail. It needs Android 8.0 or later and macOS 13 Ventura or later, and comes from the download page.

Questions people ask

Can I develop Android apps on a Mac with an Android phone?

Yes. Google's adb documentation covers USB and, on Android 11 or later, wireless debugging from a workstation on the same network. None of that needs a paid app.

Do I need The Relay if I already use adb and scrcpy?

Not for builds, logs, or mirroring. It covers a different layer: texted login codes, link handoff, clipboard sync, notifications, and incoming calls. If those rarely interrupt you, skip it.

Is it safe to sync a clipboard that sometimes holds API keys?

Any clipboard sync carries what you copy to a second device. No tool can promise an outcome, so lock both devices and prefer a password manager's own app on each one for secrets.