Setup

Using an Android phone as a baby monitor with an iPhone

The spare phone in the drawer is usually the old Android; the phone in your pocket is often the iPhone. Most first-party solutions pretend this household does not exist.

Updated 22 August 2026 5 min read

This is the most common real-world version of the setup and the worst-served one. The obvious tools are all single-ecosystem: an old iPhone talks nicely to a new iPhone, and Google's things talk to Google's things. Put an Android by the crib and an iPhone in your hand and the neat options disappear.

It works fine. You just have to pick software that does not assume both ends share an account.

Why the mismatch is a problem at all

Nothing technical stops an Android phone streaming video to an iPhone — they are two computers on the same network. The obstacles are product decisions.

Ecosystem features like a shared account, handoff, or a device list are built on one company's identity system, so they stop at its edge. Anything using them for pairing inherits that boundary. And leaving a video call running across platforms technically works but fails for the usual reasons — it cannot alert you, so you have to watch it, and it does not tell you when it drops.

What you need is software where pairing is between the two devices, not between two accounts on the same platform.

What has to be true for it to work

  • Both phones on the same Wi-Fi. Same network, and — worth checking — the same band or at least a router that lets its 2.4 GHz and 5 GHz networks talk to each other. Older phones often join 2.4 GHz only.
  • Client isolation turned off. Some routers, and most guest networks, block devices from seeing each other. That setting stops any local monitor dead. If discovery fails and everything else looks right, this is usually why.
  • The app on both platforms. Obvious, but check the Android version requirement against the old phone before you plan around it.
  • Pairing that is not an account. Scanning a code or confirming on both devices, rather than "sign in with the same Apple Account".

Which phone should be the camera

Almost always the older one, and usually the Android — not because Android is better at it, but because the bedside job is the one you cannot interrupt.

The camera phone stays plugged in, in one place, doing one thing, all night. The watching phone gets picked up, carried around, and used for other things. So the phone you still use should be the one watching, and the phone you have stopped using should be by the crib.

One practical point in Android's favour for the bedside role: it is generally more willing to let an app keep the camera running with the screen off, where iOS is stricter. The trade is that Android will kill a background app to save battery unless you tell it not to — which is a setting, and it is in the steps below.

Setting it up

  1. Prepare the Android. Factory reset it if you are done with what is on it. Cancel every alarm and silence notifications — a forgotten alarm next to a sleeping baby is the classic mistake.
  2. Put both phones on the same Wi-Fi. Not the guest network. If your router publishes separate 2.4 GHz and 5 GHz names, put both on the same one to start with; you can experiment later.
  3. Install the app on both. On the Android, allow camera, microphone, and — this one gets missed — local network access.
  4. Pair them. The bedside phone opens a short pairing window and shows a code; the iPhone scans it. There is no shared account, which is exactly why the platform mismatch does not matter.
  5. Stop Android killing the app. Settings → Apps → the app → Battery, and set it to unrestricted. Skipping this is the single most common reason a monitor is silently dead by 3am.
  6. Position, plug in, and check. Frame the whole mattress, give the phone air on every side, and keep the charging cable three feet from the crib. Then run the five overnight checks.

When it does not connect

Nearly every failure is one of four things, in this order:

  • Different networks. Including one phone on 5 GHz and one on 2.4 GHz where the router keeps them apart, and the classic: one phone quietly on mobile data.
  • Client isolation, or a guest network. See above.
  • Local network permission denied on iOS. Declined once at install and never asked again. Settings → Privacy & Security → Local Network.
  • The bedside app was killed. Battery optimisation on Android, or the app pushed out of the foreground on iOS.

The limits worth knowing first

Two, and neither is about platforms.

One watching phone at a time. In Bebrise today, a single caregiver phone connects to the bedside phone — so two parents cannot both have the picture open on their own phones. It is the most-requested thing we have not built.

Same network only. Both phones have to be on your home Wi-Fi. You cannot watch the Android from the iPhone once you have left the house, and that is a deliberate consequence of the video never leaving your network.

Bebrise runs on iPhone 6s and newer and on Android phones from roughly 2016, in either role, and the pairing does not care which is which. It is in small-scale home testing and not in the app stores yet — ask us for the install details. If you use something else, the setup steps and the failure list above still apply.

Read next

How to turn an old phone into a baby monitor — placement, heat, cords, and the overnight checks.

Baby monitors that don't send video to the cloud — why same-network-only is the trade being made.