Add ongoing research #535
Closed
Add ongoing research #535
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
| === | ||
|
|
||
| In order to make sure that the Web NFC API is future-proof, it is important to have a good overview of all the technologies that as part of NFC as well as those that support it. There are many technologies that are used by NFC but has broader usage and there are technologies not defined in the NFC Forum that people consider part of NFC. | ||
|
|
There was a problem hiding this comment.
has --> have (broader usage).
Examples for the last clause?
Split up line?
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
| NFC Simple Exchange Protocol | ||
| --- | ||
| The SNEP is a simple protocol for doing peer-to-peer (P2P) NDEF transfers. It is not supported by CoreNFC (iOS) and it is being deprecated on Android (where is branded Android Beam) due to security issues). | ||
|
|
There was a problem hiding this comment.
If need to quote the reason, provide link?
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
|
|
||
| ### Conclusion | ||
|
|
||
| Due to SNEP being deprecated on Android and not supported by CoreNFC, Web NFC will not be adding P2P supporting over SNEP. |
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
|
|
||
| Host Card Emulation | ||
| --- | ||
| The idea of HCE was originally introduced on BlackBerry devices but today it is supported by Android out of the box. |
There was a problem hiding this comment.
Links would be welcome, if available.
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
| MiFare Classic and Plus cards can be configured to support NDEF, but are not NFC compatible, meaning they do require a NFC reader chip from NXP. | ||
|
|
||
| CoreNFC doesn’t support MiFare Classic (proprietary protocols) but people have had success reading NDEF formatted MiFare Classic cards. | ||
|
|
There was a problem hiding this comment.
Link to what is CoreNFC?
Maybe some more explanation would not harm, i.e. how MIFARE exposes NDEF, but it's up to you.
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
| --- | ||
| NXP MiFare cards are quite popular and exists in different generations, with some NFC support, but also with support for proprietary protocols. As many phones have NFC readers from NXP, these additionally supports MiFare proprietary protocols. As iPhone’s NFC reader is also from NXP, CoreNFC supports MiFare protocols in addition to NFC protocols. | ||
|
|
||
| MiFare Classic and Plus cards can be configured to support NDEF, but are not NFC compatible, meaning they do require a NFC reader chip from NXP. |
There was a problem hiding this comment.
Not NFC Forum compatible, I guess.
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
|
|
||
| ### Conclusion | ||
|
|
||
| MiFare is proprietary technology and thus is not aligned with standards based approach of the web platform, thus proprietary MiFare protocols will not be supported, but as many tags and cards sold as NFC tags are actually MiFare Classic/Plus, we have decided that implementation may support Web NFC NDEF for MiFare Classic/Plus tags/cards. |
There was a problem hiding this comment.
Split up line, replace second "thus" (or split sentence)?
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
|
|
||
| ### Conclusion | ||
|
|
||
| T1T and T2T are usually used for NDEF and ISO-DEP is the most common low-level protocol for T4T so it makes sense to not support these protocols initially or at long as not supported by CoreNFC. |
There was a problem hiding this comment.
T1T, T2T, T4T need links or definition.
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
|
|
||
| Protocol support | ||
| --- | ||
| Android supports most protocols expect SNEP which is deprecated. |
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
|
|
||
| If you are building an experience on top of NFC, then you know exactly what tech (tags, card) and protocols you support and getting notified for things you don’t support is not very useful. | ||
|
|
||
| A discoverability API additionally makes it easy to snoop info, and it makes permission handling potentially harder - like do you need to ask permission for everything when you start scanning, or when technology is detected? |
There was a problem hiding this comment.
Snoop info from where? Publicly readable tags?
zolkis
reviewed
Jan 13, 2020
RESEARCH.md
Outdated
| A discoverability API additionally makes it easy to snoop info, and it makes permission handling potentially harder - like do you need to ask permission for everything when you start scanning, or when technology is detected? | ||
|
|
||
| The FIFO order can be implemented on the web but it is quite hard and presumable hard for users tounderstand, especially as all async work in one reader session should block moving on to the next reader session in the FIFO queue: | ||
|
|
There was a problem hiding this comment.
Split sentence.
tounderstand --> to understand
|
Nice work, needs more discussion. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preview | Diff