Is there a public specification for the NFC part of the new-for-2020 App Clip? Is it just an External NDEF record? I'm asking as someone who is responsible for encoding NFC and RFID chips, not as an app developer.
As #Gereon said they are just URL's and for NFC they would be URI records and the NFC specification for URI's is available at https://github.com/haldean/ndef/blob/master/docs/NFCForum-TS-RTD_URI_1.0.pdf
Related
I successfully created a pass with PassKit. But I want to add NFC capability to this pass to, when other smartphone (NFC reader) read the card, an URL will be opened to this smartphone.
I don't know if I need to do an NFC Certificate request for Apple Pay, because I don't want to use NFC for Apple Pay (https://developer.apple.com/contact/passkit/) ?
Can I achieve this without a certificate ?
No, you absolutely must have a certificate authorizing the use of NFC even if it is not a payment.
To obtain a certificate, contact Apple: http://developer.apple.com/contact/passkit.
But they rarely answer
I want to build a payment app by NFC and iOS13 to send/receive data from contactless payment machine for a country not support apple pay, is it possible?
The only way to work with NFC at iOS is Core NFC.
https://developer.apple.com/documentation/corenfc
You can read tags and get some special Informations. For example to get information about a product.
In my opinion Apple blocks the data evaluation of payments. So you can only use the Core NFC.
When you enable the nfc dictionary in the pass what does that pass do? It emulates an MIFARE card or simply extends Apple Pay with some extra data?
Yes, it certainly is possible to get an NFC certificate. However, the details of the implementation are protected by an NDA. There is a link where you can apply for a certificate here
Does Samsung Tizen support native NFC app. I'd like a native app that sits on the watch to read scanned tag and do a data exchange ?
If it has to be done in html5, does it support NFC data exchange ?
Does Samsung Tizen support native NFC app. I'd like a native app that
sits on the watch to read scanned tag and do a data exchange ?
Yes it does. Please refer to the Wearable Native reference
To read a tag you should take a look at the TAG APIs. If you also want to perform data exchange then you should take a look at the Peer to Peer APIs.
If it has to be done in html5, does it support NFC data exchange ?
Similar functionality is supported using the web APIs. Take a look at the NFCTag and NFCPeer interfaces in the Web API reference.
A nice start (Native development) point could be to check the existing tutorials for NFC here.
Here you will find the tutorials for the web APIs.
The currently accepted answer is not correct. Both NFCTag and NFCPeer APIs are not supported on Samsung Gear devices.
Just SE (secure element) API - used for processing payments - is.
It's possible to verify that when registering for notifications callbacks as per the following guide. Functions nfc_manager_set_tag_discovered_cb and nfc_manager_set_p2p_target_discovered_cb returns NOT SUPPORTED.
The following SO questions mentions the same problem:
NFC Tag not working on Gear S2
You can develop rich Web applications(HTML5) using NFC available on Samsung Gear S2. Yes it does support data exchange.
You can follow following links for more info
NFC Guide
NFC API Details
NFC Tutorial/Code
Refer this link for app Tizen Wearable Web Device API Reference.
Apologies in advance if this question is a bit low end - I am only a quarter tech savy.
I am trying to produce some NFC enabled business cards and have been trialling some Mifare 1K compatible and also ultralight cards. I have been encoding the data using a Tag writer app via a Samsung GS3 and it seems to be performing well (ie when contact occurs the GS3 seamlessly asks which email account I would like to add the contact card too without requiring a particular installed app etc.
My question relates to a universal format for contact data that can allow the same type of outcome as occurred with the GS3 above with other phone formats when they inevitably become NFC enabled (ie Blackberry, Windows phone and the next I-phone). I have been reading about .VCF or Vcard as being the universal format however when I have encoded a mifare card with a contact card in this format and tried to get by GS3 to read it, the phone asks which application I would like to use. Is there a format I can use which will allow all phones to process and ask where the user would like to save the data without a tagreader app or similar?
Thanks
Brad
Unfortunately, there isn't a format that's universal for vCard on NFC tags. The closest thing to it is using a MIME type within the NDEF payload and referencing the vCard spec. The problem with this approach is that every cellphone OS or manufacturer may implement this differently.
The details lie in how the NFC standards body, NFC Forum, has not explicitly defined vCard as a Well Known Type. The format that data is stored on NFC tags is called NDEF. The NDEF specification lays out a structure and provides a TNF field to select WKF, MIME, EXT, and others. These TNF values map to what applications should process the NDEF data. In the case of WKT, typically a native application knows what to do with it (this is what you are asking for). However, WKT currently only specifies the following structures:
Text
URI
Smart Poster
Handover
Generic Control
Signature
Since there's no WKT for vCard, what Samsung's GS3 app is doing is using a MIME type. MIME has a similar structure to NDEF but not managed by the NFC Forum so Windows, Blackberry, etc. might choose to implement the vCard structure in a different way (using an EXT type, for instance) and still be NFC Forum compliant.
More about breaking down NDEF here.