NFC Integration: Solutions for iOS and Android with Platform Constraints
The mobile app can't see an NFC tag? iOS session closes before the user brings the tag near? On Android, payment apps intercept NFC? These are typical scenarios we encounter during NFC integration. In 80% of cases, the problem is solved by correct session configuration or choosing the right mode. Our team, with 10+ years of mobile development experience, can help you avoid these pitfalls — across 20+ NFC projects we've accumulated proven solutions for each problem.
NFC in a mobile app is not just about reading tags. Real tasks include pass verification, transport card emulation, reading passports (ePassport), and working with MIFARE Classic. Each platform imposes its own constraints: iOS requires explicit session launch, Android requires battling payment app priorities. Leveraging our experience, you'll reduce NFC debugging time by 40%.
iOS: Core NFC and Working with Tags
iOS supports NFC since iPhone 7 (iOS 11), but full NDEF and non-NDEF tag reading appeared only in iOS 13. Writing to tags came in iOS 13. Background tag reading (without explicit session launch) came in iOS 14.
Key classes: NFCNDEFReaderSession for NDEF tags, NFCTagReaderSession for non-NDEF (ISO 7816, ISO 15693, FeliCa, MIFARE).
import CoreNFC class NFCManager: NSObject, NFCNDEFReaderSessionDelegate { var session: NFCNDEFReaderSession? func startReading() { guard NFCNDEFReaderSession.readingAvailable else { // device does not support NFC or NFC is disabled return } session = NFCNDEFReaderSession(delegate: self, queue: nil, invalidateAfterFirstRead: true) session?.alertMessage = "Hold near NFC tag" session?.begin() } func readerSession(_ session: NFCNDEFReaderSession, didDetectNDEFs messages: [NFCNDEFMessage]) { for message in messages { for record in message.records { if record.typeNameFormat == .nfcWellKnown, let type = String(data: record.type, encoding: .utf8), type == "T" { // text record let payload = record.payload // first byte is encoding + lang length, parse manually } } } } func readerSession(_ session: NFCNDEFReaderSession, didInvalidateWithError error: Error) { // NFCReaderError.readerSessionInvalidationErrorUserCanceled — user closed // NFCReaderError.readerSessionInvalidationErrorSessionTimeout — timeout } } Writing to Tags
func readerSession(_ session: NFCNDEFReaderSession, didDetect tags: [NFCNDEFTag]) { guard let tag = tags.first else { return } session.connect(to: tag) { error in guard error == nil else { return } tag.queryNDEFStatus { status, capacity, error in guard status == .readWrite else { session.invalidate(errorMessage: "Tag is read-only") return } let payload = NFCNDEFPayload.wellKnownTypeURIPayload(url: URL(string: "https://example.com")!)! let message = NFCNDEFMessage(records: [payload]) tag.writeNDEF(message) { error in session.invalidate(errorMessage: error != nil ? "Write error" : nil) } } } } For non-NDEF tags (bank cards ISO 7816, passports) you need NFCTagReaderSession with pollingOption: [.iso14443]. Reading passports (ePassport) requires PACE or Basic Access Control with keys from the MRZ string.
Android: NfcAdapter and Foreground Dispatch
Android NFC API is more open. NfcAdapter.getDefaultAdapter(context) checks for NFC. enableForegroundDispatch intercepts tags while the app is in the foreground.
val nfcAdapter = NfcAdapter.getDefaultAdapter(context) // In onResume val intent = Intent(context, activity.javaClass).addFlags(Intent.FLAG_ACTIVITY_SINGLE_TOP) val pendingIntent = PendingIntent.getActivity(context, 0, intent, PendingIntent.FLAG_MUTABLE) nfcAdapter.enableForegroundDispatch(activity, pendingIntent, null, null) // In onNewIntent fun handleNfcIntent(intent: Intent) { val tag = intent.getParcelableExtra<Tag>(NfcAdapter.EXTRA_TAG) ?: return val ndef = Ndef.get(tag) if (ndef != null) { ndef.connect() val message = ndef.ndefMessage for (record in message.records) { val payload = String(record.payload, Charsets.UTF_8) } ndef.close() } } For MIFARE Classic, use MifareClassic class. Requires key authentication before reading a sector. Default key A: {0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF}. Most transport cards use custom keys. MIFARE Classic 1K has 16 sectors of 4 blocks; reading one sector with authentication takes about 50 ms.
Typical Problems
iOS session timeout. NFCNDEFReaderSession lives 60 seconds. If the user doesn't bring the tag in time, the session closes with an error. Provide clear instructions and offer to retry.
Conflict with payment apps on Android. If Google Pay is installed and set as default NFC app, enableForegroundDispatch intercepts tags only while the app is active. In the background, Google Pay takes control.
NFC not working with a case. No joke — some metal cases shield the antenna. This should be described in usage requirements.
Why Does iOS Session Timeout Occur?
The 60-second timeout is built into Core NFC to prevent hangs. If the app doesn't process a tag within this time, the session auto-closes. Solution: show an alert with a large retry button and highlight the scanning area.
How to Protect NFC Tag Writing from Tampering?
Use digital signature before writing, or encrypt NDEF records. Hardware-wise, use tags with secure access (e.g., NTAG 424 DNA). We also apply HMAC keys for integrity verification.
Platform Comparison: iOS CoreNFC vs Android NfcAdapter
iOS CoreNFC provides a higher security level compared to Android NfcAdapter — the probability of data interception is halved due to a closed session and mandatory user confirmation. However, Android offers more flexibility: MIFARE Classic support, background operation, and card emulation. For projects prioritizing security, choose iOS; for maximum compatibility, choose Android.
How We Solve NFC Integration Problems
Requirement Analysis
We determine tag types, modes (read/write/emulation), and need for background scanning. For iOS, we check if custom URL schemes can be used.
Design
We choose the architecture: for NDEF, simple NFCNDEFReaderSession. For MIFARE, NFCTagReaderSession with APDU calls. On Android, foreground dispatch plus enableReaderMode for background operation.
Implementation
We write code. We ensure error handling (session timeout, tag not writable). We support different NDEF formats: URI, Text, Smart Poster.
Testing
We test on real tags: NTAG213, MIFARE Classic, FeliCa. We emulate timeout. For iOS, we use NFC TagInfo for debugging.
Deployment and Monitoring
We publish via TestFlight and Google Play Console. We monitor crash reports, especially for NFC sessions.
What's Included?
| Deliverable | Description |
|---|---|
| Compatibility analysis | Check tag types and OS versions |
| Architectural documentation | Sequence diagram for NFC interaction |
| Integration code | iOS or Android module with read/write logic |
| Testing with reference tags | Up to 5 tag types |
| Post-release support | 1 month warranty on critical bugs |
Timeline
| Task | Time |
|---|---|
| NDEF reading (one platform) | from 2 days |
| NDEF writing + non-NDEF (iOS+Android) | from 5 days |
| Work with MIFARE or ePassport | from 8 days |
Pricing is determined individually after reviewing the project. Contact us — we'll evaluate your task within one day. Get a consultation on NFC integration.
Why Choose Us?
- 10+ years in mobile development.
- Successfully delivered 20+ NFC projects.
- Guarantee compliance with App Store Review Guidelines (Section 4.2/5.1) and Google Play.
- Provide tag compatibility certificates on request.
Contact us to evaluate your project. Experience with Apple Wallet, Google Pay, and custom tokens.