[ALIGNMENT]: NFC tag feature-set (contact & channel sharing / provisioning)

[thebentern]

Area of Alignment

NFC tag support is live but divergent across clients, and absent on firmware:

• Android: full read + write, contacts and channels, in the shared QR dialog, with an enable-NFC prompt and tap-to-import (v2.8.0, feat: NFC tag writing for shared contacts and channels Meshtastic-Android#6030).
• iOS: write-only, contacts-only, iOS 18+ (no Mac Catalyst), buried in Settings → Tools, no in-app reader; entitlement is TAG while the code uses NDEF.
• Web: no NFC.
• Firmware: no NFC — though the T-LoRa Pager already carries an undriven ST25R3916, and [Feature Request]: NFC tag interface for quick onboarding of stations firmware#7236 asks for NFC tap-to-provision.

NFC carries the same meshtastic.org/v/# (SharedContact) and meshtastic.org/e/# (ChannelSet) URLs as QR — so this is a UX + platform-reach alignment, not a data-format one. All work must conform to Design Standards v1.4 (§1 circular ID, §2 light/dark, §3 conditional visibility, §4 labeled actions, §5 native / 44×44, §6 plain language, §7 semantic colors).

Full audit (mismatches, standards-conformance table, canonical UX, firmware feature proposals): standards/audits/nfc-alignment-audit.md, added in #125.

Sub-tasks

• Create Android alignment issue. → [ALIGNMENT]: NFC tag feature-set — Design Standards v1.4 conformance polish Meshtastic-Android#6331 (PR: Align NFC contact import and share dialogs with Design Standards v1.4 Meshtastic-Android#6332)
• Create iOS alignment issue. → [ALIGNMENT]: NFC tag feature-set — reach cross-platform parity with Android Meshtastic-Apple#2135 (PR: Align NFC tag support with Android and Design Standards v1.4 Meshtastic-Apple#2136)
• Create Web alignment issue.
• Create Firmware tracking issue (NFC exploration; cross-link [Feature Request]: NFC tag interface for quick onboarding of stations firmware#7236).

[thebentern]

Android and iOS implementation is now up:

Platform	Issue	PR	Verification
iOS (Meshtastic-Apple)	meshtastic/Meshtastic-Apple#2135	meshtastic/Meshtastic-Apple#2136	Full Debug build succeeded; 12/12 unit tests pass (incl. manually_verified passthrough + channel URL round-trip)
Android (Meshtastic-Android)	meshtastic/Meshtastic-Android#6331	meshtastic/Meshtastic-Android#6332	spotless/detekt/allTests/kmpSmokeCompile clean; 6 screenshot goldens recorded + validated

Cross-platform semantics aligned in both PRs: the manually_verified bit encoded by the sharer is now honored on import on both platforms (Android previously forced true), and both apps write the same NDEF URL records (/v/#, /e/#).

Remaining sub-tasks: Web alignment issue and the firmware NFC exploration tracking issue (audit §6.B, cross-linking meshtastic/firmware#7236).

[garthvh]

Status update (August 2026): the mobile alignment shipped — meshtastic/Meshtastic-Apple#2136 (merged Jul 24) and meshtastic/Meshtastic-Android#6332 (merged Jul 21), with the cross-platform semantics aligned per the table above (manually_verified honored on import on both platforms; contacts and channels both supported). iOS is no longer write-only/contacts-only.

Remaining scope: firmware-side NFC (meshtastic/firmware#7236 — the T-LoRa Pager's ST25R3916 is still undriven) and Web, which has no NFC path (Web NFC being Chromium-only makes that a deliberate decision to record here rather than an oversight).