What to check before writing an NFC tag on iPhone
A practical checklist for tag capacity, writable status, payload format, and iPhone behavior before a write.
Writing an NFC tag should feel calm because the app has already checked the risky parts. Boreal NFC is designed around that idea: read first, explain what is there, validate the edit, then write.
Check the payload
Common NDEF records include URLs, text, phone numbers, email links, location links, Wi-Fi-like payloads, and contact-style data. The app should show the record in plain language and keep expert details secondary.
Check capacity and write status
A tag can be writable, read-only, locked, unsupported, unknown, or too small for the edited payload. Those states should be clear before the user starts the write session.
Check iPhone behavior
Some NFC payloads are technically valid but still awkward in the real world. For contact sharing, URL-based records are often more predictable than expecting every phone to handle a direct vCard write the same way.
Test after writing
A successful write is not the final step. The user should scan the tag again, confirm the destination, and keep a QR fallback for public sharing.