Skip to content

Commit 612821a

Browse files
Updated explainer (#534)
* Updated explainer * Address feedback
1 parent e075f9e commit 612821a

File tree

1 file changed

+15
-6
lines changed

1 file changed

+15
-6
lines changed

EXPLAINER.md

Lines changed: 15 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -10,19 +10,27 @@ Participate
1010
- https://lists.w3.org/Archives/Public/public-web-nfc/
1111

1212
## Introduction
13+
1314
Web NFC aims to provide sites the ability to read and write to nearby NFC (Near
14-
Field Communication) devices (e.g., tags and phones) in a secure and privacy
15-
preserving manner.
15+
Field Communication) tags in a secure and privacy preserving manner.
1616

1717
NFC consists of a rather large set of technologies, so for this first iteration
1818
of the API the focus has been on supporting the NFC Data Exchange Format aka
1919
[NDEF](https://www.oreilly.com/library/view/beginning-nfc/9781449324094/ch04.html),
2020
a lightweight binary message format, as it works across different tag formats.
2121

22-
The focus has been on making an easy to use, and very webby API that web
23-
developers would be comfortable with, and at the same time making sure that it
24-
is low-level and flexible enough so that users can get the full potential out of
25-
NDEF and even integrate with legacy solutions.
22+
Web NFC is only available to top-level, secure browsing contexts, and origins
23+
must first request the “nfc” permission while handling a user gesture. To then
24+
perform a read or write, the web page must be visible when the user touches an
25+
NFC tag with their device. The browser uses haptic feedback to indicate a tap.
26+
Access to the NFC radio is blocked if the display is off or the device is
27+
locked. For backgrounded web pages, receiving and pushing NFC content are
28+
suspended.
29+
30+
We believe Web NFC is an easy to use API that web developers will be comfortable
31+
with, and at the same time that it is low-level and flexible enough so that
32+
users can get the full potential out of NDEF and even integrate with legacy
33+
solutions.
2634

2735
## Goals
2836

@@ -34,6 +42,7 @@ Make sure the API is extendable to cover more NFC use-cases, like non-NDEF, in
3442
the future.
3543

3644
## Non-goals
45+
3746
In this version of the API, proprietary NFC technologies used in hotel keys,
3847
e-passports etc are not supported. Automatic handling of NFC content, such as
3948
opening or saving files, making calls or saving contacts (with “smart posters”),

0 commit comments

Comments
 (0)