NFC

sys.NFCViewer

bb.action.SHARE

Any valid URI value that is preceded by file:// (for example, file://, http://, https://)

Any valid MIME type value, such as audio/mp3, image/jpg, and application/myfiletype

sys.NFCViewer

bb.action.SHARE

filelist://

Any valid MIME type value, such as audio/mp3, image/jpg, and application/myfiletype

Data can be sent in JSON format as a list of metadata in the following format:

[{
    "uri":<file-uri>,
    "type":<mime-type>,
    "data":<metadata>
}] 

In the above code, the uri is the local path to the file, type is the MIME type for the specified file, and data is the associated metadata for the specified file (for example, thumbnail).

sys.NFCViewer

bb.action.SHARE

text/plain

Text is sent as a byte array. UTF-8 encoding is supported.

sys.NFCViewer

bb.action.SHARE

application/vnd.rim.nfc.ndef

NDEF message is sent in the form of a byte array. The following method is used to create the byte array message: nfc_get_ndef_message_bytes().

sys.NFCViewer

bb.action.SHARE

text/URI-list

Data is sent as a URI to the remote file or link and must be URI encoded (for example, http://somesite/multi%20word%name.doc).

sys.NFCViewer

bb.action.SHARE

MIME type can be specified in the following format: application/myapp, text/vCard. Make sure that the values specified are different from the MIME type values used to share text, NDEF messages, and URLs.

Custom data is sent in Byte array form, specific to the application and MIME types mentioned above.