iPhone NFC vs Android NFC — What Each One Can and Can't Do

For everyday NFC tasks, iPhone and Android behave the same way. Both read NDEF tags, write to blank stickers, and speak the same 13.56 MHz radio. The differences live at the edges — card emulation, MIFARE Classic, background tag triggers — and that's where Android still does more. Here's what each platform can and can't do today. If you want the radio-layer background first, see how NFC actually works.

What both phones do equally well

Both platforms read NDEF records — URL, vCard, Smart Poster, Wi-Fi credentials, plain text — from any NFC Forum Type 2 or Type 4 tag, and both write to unlocked NTAG213/215/216 and MIFARE Ultralight stickers. Same 4 cm range at 13.56 MHz. A tag written by a Pixel works on an iPhone. That covers almost every common use case: tap-to-Wi-Fi, NFC business cards, museum labels, Shortcuts triggers, plant-care tags. The platform differences only matter once you push past plain NDEF.

What iPhone NFC can do

Core NFC arrived in iOS 11 and was opened up in iOS 13 — apps can read and write a wide set of tag technologies, including ISO 7816, ISO 15693, FeliCa, and MIFARE-compatible tags (Ultralight and the NTAG family).

Two things stand out. First, background tag reading on iPhone XS and later: the OS shows a banner the moment a tag enters the field, with no app open — see how to read an NFC tag with your iPhone. Second, Apple Wallet handles payments, transit, hotel and car keys, and state IDs through a secure-element path no third-party app can touch.

iOS 17.4 added third-party Host Card Emulation, but with significant constraints. It requires an entitlement, is limited to users in the European Economic Area, and covers only approved use cases like in-store payments, closed-loop transit, car/home/hotel keys, corporate badges, memberships, and event tickets. Outside the EEA, third-party HCE on iPhone is effectively unavailable.

What Android NFC does that iOS doesn't

Android exposes two modes simultaneously — reader/writer and card emulation — both as first-class APIs available to any app.

Full Host-based Card Emulation has been there since Android 4.4 in 2013. Any app can declare an Application Identifier (AID), extend HostApduService, and process ISO 7816-4 APDUs over ISO-DEP on NFC-A. No region gate, no entitlement, no approved-use-case list. That's the biggest practical difference between the platforms today.

Android also reads and writes MIFARE Classic on devices with NXP NFC chips — most Samsung, Pixel, OnePlus, and Xiaomi handsets. iPhone can't touch MIFARE Classic because Core NFC doesn't expose NXP's proprietary CRYPTO1 stack. Our tour of MIFARE Ultralight, Classic, and DESFire covers what each family is suited for.

Tag intents on Android fire system-wide. An app can register an intent filter and launch automatically when a matching tag is detected. On iOS, every reader session needs a foreground app and a system NFC sheet. To be fair, Android Beam (peer-to-peer NDEF push) was deprecated in Android 10; both platforms have moved on from true device-to-device NFC.

What this means for NFCore

For standard NDEF tags — Wi-Fi, vCard, URL, Smart Poster, plain text — either platform works fine. NFCore ships the same UI on both stores. On iOS you'll see the system NFC sheet when you start a read or write; on Android the same action can happen through a background intent. The app surfaces what each OS allows.

If your use case needs MIFARE Classic, freeform card emulation, or background-triggered automation, Android is the wider canvas. Apple is opening that surface slowly. Try NFCore on the App Store or Google Play.

Frequently Asked Questions

Can iPhone emulate an NFC card like Android can?

Only inside Apple Wallet, and — since iOS 17.4 — through a tightly gated HCE entitlement restricted to specific use cases for users in the European Economic Area. Android lets any app emulate a card using HostApduService, with no region or use-case gate.

Why can't my iPhone read a MIFARE Classic card?

Core NFC supports MIFARE Ultralight, the NTAG family, ISO 7816, ISO 15693, and FeliCa — but not MIFARE Classic, which uses NXP's proprietary CRYPTO1 stack on NFC-A. Android phones with NXP NFC chips can read and write Classic through dedicated MifareClassic APIs.

Do both platforms read the same NFC tags?

For common NDEF tags — NTAG213/215/216, Wi-Fi tags, vCard tags, smart posters — yes, both phones read them identically. Differences only matter for proprietary chip families, freeform card emulation, and background automation.

Which iPhones support background NFC tag reading?

iPhone XS and later on iOS 13 or newer. The system shows a banner the moment a tag enters the field — no app open. Earlier iPhones (7, 8, X) need an app to start a reader session first.