Closed Bug 894323 Opened 7 years ago Closed 6 years ago

[B2G][NFC][User Story]: Support Reading of NFC tags

Categories

(Firefox OS Graveyard :: NFC, defect)

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: kchang, Unassigned)

References

Details

(Keywords: feature, Whiteboard: [ucid:NFC7, 1.3:p2, ft:RIL])

User Story

As a user, I would like to tap and read the info (typically contact or URL) programmed in a "NFC tag". The device should open an appropriate app to view the read information (e.g. URL with a browser, Contacts app for a contact entry etc). 

Acceptance Criteria:
1. Device has NFC enabled and upon tapping on the tag, opens an appropriate app to view the read information (e.g. URL with a browser, Contacts app for a contact entry etc). 
2. If there are multiple apps registered to view a particular type of info, those apps should open in a list for the user to pick.
3. If the sharing works successfully (or fails), the device will show the appropriate visual or sensory (vibration) indication. (see UX spec)

Attachments

(1 file)

The NFC enabled Mobile device can read an NFC tag. NFC tags are used most commonly to direct a mobile device to a particular web page for a coupon or promotion etc. The reader/writer mode within the NFC stack is used for reading NFC tags.
--Core Protocol stack requirements
1)     Firefox OS must support the reader/writer mode in the NFC stack.
2)     Firefox OS must support the NDEF data exchange format.
3)     Firefox OS must support NFC tag types 1,2,3,4
--User experienceThe user can tap an NFC enabled mobile device against an NFC tag. This will typically cause the mobile device to open up the browser and go to the URI specified by the NFC tag.
Blocks: b2g-nfc
In development code suports this usage (and demo-able now).
Summary: [User story][NFC] Reading from NFC tags → [B2G] [NFC User Story]: Support Reading of NFC tags
Duplicate of this bug: 894684
Summary: [B2G] [NFC User Story]: Support Reading of NFC tags → [B2G][NFC][User Story]: Support Reading of NFC tags
Flags: in-moztrap?
QA Contact: wachen
Flags: in-moztrap? → in-moztrap?(wachen)
Whiteboard: [ucid:NFC7]
So does this in-effect work like a QR code?  

What exactly are the use cases for this technology?
URL's?  Web URL/addresses?  Contact information?  Transferring media?

Is there any real-world use cases of this technology that is out there in the wild and in use that we can evaluate?
Flags: needinfo?(ffos-product)
Use Case wise: I can't speak authoritatively, but QR codes are far more common at various conferences and events.

Technology-wise, support for reading (and writing) does support all other use cases due to shared code underneath.
Whiteboard: [ucid:NFC7] → [ucid:NFC7], [FT:RIL]
Whiteboard: [ucid:NFC7], [FT:RIL] → [ucid:NFC7, FT:RIL]
Moving NI to Sandip
Flags: needinfo?(ffos-product) → needinfo?(skamat)
Where can we get NFC tags? Also, is there any app created for NFC tags? Or, will there be one after all the function completed? If not, I could make an app for testing later maybe (only if api and other stuffs are not restricted to certified/privelege )
I think it is not just doing what QR codes is doing. There are many use cases. I can just come up with some now:
1. User can read the payment information and pay
2. User can save their website or information in a tag and allow user to fetch it
3. User can rewrite their information in a tag
4. User can reencode the tag to keep it secure
5. User can save bunches of settings in NFC, put them in different places, and phone would automatically sense it/change settings. For example, you put the tag under charger before, you can put a tag of mute settings. Also, you can put a tag of vibration only on the desk you study so if you put phone there. It will change to settings of environment you like when you are studying
6. Contacts info
7. Bluetooth auto pairing ...
I think it is way more creative than a QR code. :P
Hi Walter,

We just updated the internal NFC interfaces, and I'll upload the Gaia side nfc-demo app (Bug 860910) that can read, write, and P2P exchange NFC NDEF formatted tags. NDEF is an open standard, so nfc-demo in no way covers al use cases.

Where to get tags: I'll get back to you...
Hi, Garner,

This is not for the real user story or acceptance criteria.
That's for answering Casey's comment 3.

About the nfc-demo app, is it a certified/privelege app?
@Walter:
Tags: At least for US based folks, here's were I believe we got them last time:

 http://nfctags.tagstand.com/

@Chuck:
NFC-Demo (and System App/NFC) is a certified app (it can access the DOM functions to use NFC function), but we can consider how to safely loosen that up a bit. What that means currently is unprivilaged apps will merely get MozActivity notifications with information on it (a vcard, a URL, a phone number, etc), instead of directly from the navigator.mozNfc DOM.
Whiteboard: [ucid:NFC7, FT:RIL] → [FT:RIL, v1.2, ucid:NFC7]
Depends on: webnfc
blocking-b2g: --- → koi+
(In reply to Ken Chang from comment #0)
> The NFC enabled Mobile device can read an NFC tag. NFC tags are used most
> commonly to direct a mobile device to a particular web page for a coupon or
> promotion etc. The reader/writer mode within the NFC stack is used for
> reading NFC tags.
> --Core Protocol stack requirements
> 1)     Firefox OS must support the reader/writer mode in the NFC stack.
> 2)     Firefox OS must support the NDEF data exchange format.
> 3)     Firefox OS must support NFC tag types 1,2,3,4
Based on the discussion with DT during NFC work week, we will remove this one. 
> --User experienceThe user can tap an NFC enabled mobile device against an
> NFC tag. This will typically cause the mobile device to open up the browser
> and go to the URI specified by the NFC tag.
So, the core protocol stack requirements only contains: 
> 1)     Firefox OS must support the reader/writer mode in the NFC stack.
> 2)     Firefox OS must support the NDEF data exchange format.
Whiteboard: [FT:RIL, v1.2, ucid:NFC7] → [FT:RIL, v1.2, ucid:NFC7, koi:p1]
Depends on: 860907
Depends on: 860910
Depends on: 897312
Depends on: 902051
Whiteboard: [FT:RIL, v1.2, ucid:NFC7, koi:p1] → [FT:RIL, NFC v1.2, ucid:NFC7, koi:p1]
Whiteboard: [FT:RIL, NFC v1.2, ucid:NFC7, koi:p1] → [FT:RIL, NFCv1.2, ucid:NFC7, koi:p1]
Will add the exact required tag types after we confirm the OEM/HW. OK to remove this line ("Firefox OS must support NFC tag types 1,2,3,4") from the user story for now on v1.2.
Flags: needinfo?(skamat)
Whiteboard: [FT:RIL, NFCv1.2, ucid:NFC7, koi:p1] → [FT:RIL, koi:p1, NFCv1.2, ucid:NFC7]
Blocks: koi-ril
blocking-b2g: koi+ → 1.3+
Whiteboard: [FT:RIL, koi:p1, NFCv1.2, ucid:NFC7] → [FT:RIL, NFCv1.2, ucid:NFC7]
Whiteboard: [FT:RIL, NFCv1.2, ucid:NFC7] → [FT:RIL, 1.3:p1, ucid:NFC7]
Blocks: b2g-nfc-ux
No longer blocks: b2g-nfc
Remove blocking-b2g flag from User Story bugs. Use whiteboard to indicate what FxOS version we target.
blocking-b2g: 1.3+ → ---
Whiteboard: [FT:RIL, 1.3:p1, ucid:NFC7] → [FT:RIL, 1.3:p2, ucid:NFC7]
Keywords: feature
Update whiteboard tag to follow format [ucid:{id}, {release}:p{1,2}, ft:{team-id}]
Whiteboard: [FT:RIL, 1.3:p2, ucid:NFC7] → [ucid:NFC7, 1.3:p2, ft:RIL]
Close this bug so that QA can do verification.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
It was verified. However, moz-trap- for no real test cases can be applied
Status: RESOLVED → VERIFIED
Flags: in-moztrap?(wachen) → in-moztrap-
Hi Juwei,
Per discussion with QA, we would still need UX doc updated for future tracking.
Tags with URL or vCard are the use cases we would claim as FxOS features.

Set back to RESOLVED FIXED as we are adding more test cases.
Status: VERIFIED → RESOLVED
Closed: 6 years ago6 years ago
Flags: needinfo?(jhuang)
Spec updated.
Flags: needinfo?(jhuang)
User Story: (updated)
Verified on
Device    Flame 
Gaia      2e5636e852a9354a5f8072b179cf16f72647cfd6
Gecko     https://hg.mozilla.org/mozilla-central/rev/8bd92dc9ef59
BuildID   20140608160201
Version   32.0a1
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.