Closed Bug 894673 Opened 9 years ago Closed 4 years ago

[B2G][NFC][User Story]: Support NFC Pairing (Wifi AP case)

Categories

(Firefox OS Graveyard :: NFC, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: skamat, Unassigned)

References

Details

(Keywords: feature, Whiteboard: [FT:RIL, ucid:NFC2])

Attachments

(1 file)

The user can tap an NFC enabled WiFi access point or ad-hoc Wifi device with FxOS device to initiate Wifi setup.
Duplicate of this bug: 894316
Summary: [B2G] [NFC User Story]: Support NFC Pairing (Wifi AP case) → [B2G][NFC][User Story]: Support NFC Pairing (Wifi AP case)
Blocks: b2g-nfc
Flags: in-moztrap?
QA Contact: wachen
Flags: in-moztrap? → in-moztrap?(wachen)
Whiteboard: [ucid:NFC2]
There may not be a "well known" NDEF message. If not, we'll need to define a common format for exchange.
(In reply to Garner Lee from comment #2)
> There may not be a "well known" NDEF message. If not, we'll need to define a
> common format for exchange.

Yes, you are right. We will need to define a common NDEF meesage for WIFI.
UX Note: the interaction for pairing with AP, BT speaker or headset should be the same as Bug 894672.
<Acceptance Criteria> (Proposal)
1. User can connect to a Wifi access point
2. User can connect to an ad-hoc Wifi device

Please advise if there is any restrictions/spec on connection time.
Whiteboard: [ucid:NFC2] → [ucid:NFC2], [FT:RIL]
Whiteboard: [ucid:NFC2], [FT:RIL] → [FT:RIL, v1.3, ucid:NFC2]
Based on the discussion with DT during NFC work week: 

1. How important is it? All of us suggest to remove this user story. Sandip?
Flags: needinfo?(skamat)
Depends on: webnfc
Depends on: 860907
Depends on: 897312
Depends on: 902051
removing from 1.2/1.3 and postponing till later. Would like to understand what challenges are here.
Whiteboard: [FT:RIL, v1.3, ucid:NFC2] → [FT:RIL, NFCv1.3, ucid:NFC2]
Flags: needinfo?(skamat)
blocking-b2g: --- → 1.3+
Whiteboard: [FT:RIL, NFCv1.3, ucid:NFC2] → [FT:RIL, 1.3:p1, ucid:NFC2]
Hi all,
Interaction spec updated, please refer to attachment.
According to comment 6 and 7, remove this user story from 1.3.
blocking-b2g: 1.3+ → -
Whiteboard: [FT:RIL, 1.3:p1, ucid:NFC2] → [FT:RIL, ucid:NFC2]
Blocks: b2g-nfc-ux
No longer blocks: b2g-nfc
Put this as a candidate feature in v1.4.
blocking-b2g: - → 1.4?
Remove blocking-b2g flag from User Story bugs. Use whiteboard to indicate what FxOS version we target.
blocking-b2g: 1.4? → ---
Keywords: feature
Flags: in-moztrap?(wachen) → in-moztrap+
It is not in NFC user story.
No longer blocks: b2g-nfc-ux
blocking-b2g: --- → backlog
Whiteboard: [FT:RIL, ucid:NFC2] → [1.4, FT:RIL, ucid:NFC2]
1.4 user story supposedly needs to be complete before Sprint3.
Will communicate with team to reconfirm target milestone.
Target Milestone: --- → 1.4 S3 (14mar)
It isn't a 1.4 feature.
Whiteboard: [1.4, FT:RIL, ucid:NFC2] → [FT:RIL, ucid:NFC2]
Target Milestone: 1.4 S3 (14mar) → ---
Note: This is an expected partner contribution to Firefox OS platform. The details of landing timeframe are currently TBD. We will tentatively track it for 2.0 for now, but can confirm when the contribution landing details are finalized.
blocking-b2g: backlog → ---
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.