NFC
Near field communication is short-range hardware interaction. The app should describe what it wants to do, then let the host open the platform NFC session, display the platform prompt, read or write the tag, and return typed records.
By the end of this guide, you will know how to build a screen that scans an NFC tag and stores the first NDEF text or URI record. The same pattern applies to larger apps: declare the capability when native configuration is needed, store the result in typed app state, request the host operation from a reducer, and test both success and failure with a memory host.
Do not put NFC SDK calls in reducers. NFC sessions are host-owned because permissions, hardware support, background behavior, and entitlements differ by target.
1. Start with the state the screen needs
Add the smallest state fields the screen needs to render honestly. For this flow, useful state is:
#[derive(Default)]
struct NfcState {
// Add these fields to your existing app state.
nfc_text: Option<String>,
nfc_error: Option<String>,
scanning_nfc: bool,
}
impl GlobalState for NfcState {}
State is the source of truth for the UI. Do not store whether the host "probably" succeeded; wait for the typed success action and store the returned value.
2. Configure the target and host
Run this once from the project root:
fission add-capability nfc --project-dir .
That command records the capability in fission.toml and updates generated platform files where Fission can do so safely. It does not replace product-specific review of native manifests, usage text, entitlements, service identifiers, domains, or store policy.
The CLI adds Android NFC permission and optional hardware feature metadata. iOS needs an NFC usage description and reader-session entitlement. Desktop targets usually need a product-specific hardware provider for the reader you ship or support.
This is the difference between the Fission API, a provider, and packaging configuration:
•
The Fission API is the typed Rust contract your reducer calls, such as ctx.effects.camera().capture_photo(...).
•
The provider is the shell-side Rust implementation that turns that typed request into the correct OS, browser, or hardware call.
•
Packaging configuration is the manifest, plist, entitlement, service-worker, protocol, domain, or store metadata that lets the platform permit that call in a real installed app.
If the API exists but the provider is missing, the request returns a typed unsupported error. If the provider exists but packaging is missing, the operating system or browser may deny the request before the provider can complete it.
3. Define reducers for success and failure
Capability work finishes later, after the reducer that started it has returned. You therefore need one reducer for the successful result and one reducer for the error path.
#[fission_reducer(TagScanned)]
fn on_tag_scanned(state: &mut NfcState, tag: NfcTag) {
state.scanning_nfc = false;
state.nfc_text = tag.records.first().map(|record| String::from_utf8_lossy(&record.payload).to_string());
state.nfc_error = None;
}
#[fission_reducer(TagScanFailed)]
fn on_tag_scan_failed(state: &mut NfcState, error: NfcError) {
state.scanning_nfc = false;
state.nfc_error = Some(error.message);
}
Keep both paths explicit. A denied permission, unavailable device, unsupported host, or cancelled prompt is not an exceptional mystery; it is normal product behavior the UI should explain.
4. Request the capability from a reducer
Call the capability from the reducer that handles the user's intent. The reducer queues a host effect and returns. The runtime later dispatches either the success reducer or the failure reducer.
state.scanning_nfc = true;
ctx.effects
.nfc()
.scan_tag(NfcScanRequest {
technologies: vec![NfcTechnology::Ndef],
prompt: Some("Hold a tag near the device".into()),
timeout_ms: Some(15_000),
allow_multiple_records: true,
})
.on_ok(ctx.effects.bind(
TagScanned(NfcTag::default()),
reduce_with!(on_tag_scanned),
))
.on_err(ctx.effects.bind(
TagScanFailed(NfcError::default()),
reduce_with!(on_tag_scan_failed),
));
The call does not run the OS API directly. It records a typed host request. That keeps shared app logic portable across Fission targets where the capability applies, plus static-site previews and tests.
5. Trigger the reducer from the UI
Wire the user-facing control with the normal Fission action pattern. This example uses a small widget so the binding has one clear home.
struct ScanNfcTagButton;
impl From<ScanNfcTagButton> for Widget {
fn from(component: ScanNfcTagButton) -> Self {
let (ctx, view) = fission::build::current::<NfcState>();
let run = with_reducer!(ctx, ScanNfcTag, on_scan_nfc_tag);
Button::new("Scan tag")
.disabled(view.state().scanning_nfc)
.on_press(run)
.into()
}
}
Rename the widget and action for your product, but keep the shape: the widget dispatches one typed action, the reducer starts the capability request, and the success or failure reducer updates state.
6. Provide and test the host behavior
Register an NfcHost with .with_nfc_host(...). Use MemoryNfcHost in tests. Real providers should report availability before scanning and return NfcError::unsupported(...) for operations the device cannot perform.
Test availability, successful scan, timeout, cancel, and unsupported write/emulation paths. For product flows, include a test proving the UI disables the scan button when availability says no NFC hardware is present.
A useful first test creates the app with the memory host, dispatches the start action, feeds the queued effect through the host, and asserts that the reducer updates state from the returned payload. Add a second test for the error path before you ship the screen.
Platform expectations
Android and iOS are the primary targets. Web NFC is limited to specific browsers and devices. Windows, macOS, and Linux normally require external readers or smart-card stacks rather than one standard app-level NFC API.
For a cross-platform summary, read the capability matrix. For exact request fields, provider traits, and generated configuration, see the NFC reference.
Finished capability flow
A complete NFC integration has all of these pieces in place:
Piece | What should exist |
|---|---|
Configuration | fission.toml declares the capability and generated platform files contain the permission text, manifest entry, entitlement, domain, or protocol metadata the target needs. |
State | App state records the in-flight flag, the successful value, and the user-facing error separately. |
Reducers | One reducer starts the host request, one handles success, and one handles denial, unsupported hosts, cancellation, or provider errors. |
Provider | The shell registers a real provider for production and a memory provider for tests. |
Tests | At least one test covers success and one covers permission denial or unsupported host behavior. |
Diagnose capability failures
Capability failures should be safe to retry and easy to explain. Start by checking fission.toml, then run fission doctor, then inspect the generated target files. If the provider is missing, the request should return an unsupported error. If the provider exists but the platform configuration is wrong, the OS or browser will usually deny the request before the provider can complete it. Keep those cases distinct in the UI so users know whether they can retry, change settings, connect hardware, or choose another path.
Fission
A cross-platform, GPU-accelerated user interface framework for Rust. MIT licensed.
Copyright (c) 2026 Fission
Ready to use today. Widget APIs are expected to remain stable; some runtime and shell APIs may change before 1.0.0.
Fission 0.7.0