Closed Bug 823075 Opened 12 years ago Closed 12 years ago

Need to provide feedback while setting up call forwarding rules.

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jaoo, Unassigned)

Details

(Whiteboard: [LOE:S]interaction ux-p2)

While the user set up any call forwarding rule (always forward, forward when busy, etc.) there's no feedback about what's happening. Moreover there is no error information when the forwarding rule cannot be established. The idea here is to implement something similar to the UX we have for MMI codes for call forwarding in the Phone app.
blocking-basecamp: --- → ?
Flags: needinfo?(kaze)
@fabrice: Are we ready on the platform side to do call forwarding ? @daniel: Is it a certification requirement ? Does the target market expects this ? I mean, it costs a lot of money. Moreover I am afraid this could be a bunch of work at this stage of the project.
Flags: needinfo?(kaze)
Flags: needinfo?(fabrice)
Flags: needinfo?(dcoloma)
Adding José for LOE and risk estimation.
Flags: needinfo?(josea.olivera)
(In reply to David Scravaglieri [:scravag] from comment #1) I'll answer here with Fabrice's permission ;). > @fabrice: Are we ready on the platform side to do call forwarding ? Yes, we are. The platform support for this landed nearly couple of months ago. > @daniel: Is it a certification requirement ? Does the target market expects > this ? I mean, it costs a lot of money. > > Moreover I am afraid this could be a bunch of work at this stage of the > project. No, I don't think so. It's just showing an spinner while the call forwarding rule is being established and showing the result in a pop-up notification. Something similar is already implemented in the Phone app for dealing with MMI codes for call forwarding.
Flags: needinfo?(josea.olivera)
Whiteboard: [LOE:S]
I expect that the intended behavior of this toggle will be very similar to the call waiting UI since it is also a network enabled feature. It's very important that we have at least some kind of error feedback if the toggle is not settable due to network or no-connection issues. As a secondary priority we should also indicate progress state when a setting is toggled since these types of network features take time to set. cc. Raffa for additional comment.
Whiteboard: [LOE:S] → [LOE:S]interaction ux-p2
Flags: needinfo?(fabrice)
Reminder to split this issue
Hey guys, In terms of flow and functionality, call forwarding is similar but more nuanced than call waiting. In any case, this feature is mostly done (functional) and what's left is UX polishing, mostly nicer error alerts and better feedback. Both Jose Antonio and myself are aware of this, but quite simply neither of us has had the time to give it the final push. In any case, it's a rather obscure feature that I believe we need to have for compliance and right now it's basically functional, more so than other features out there. Let's work to give it some polish, but I don't think we should stress *too* much about it.
Splited into two issues: bug 823506 bug 823508 Closing this one.
blocking-basecamp: ? → -
Flags: needinfo?(dcoloma)
(In reply to David Scravaglieri [:scravag] from comment #7) > Splited into two issues: > > bug 823506 > bug 823508 > > Closing this one. David, since you split this bug into tow different ones we should resolve this bug as WONTFIX, shouldn't we?
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
blocking-basecamp: - → ---
You need to log in before you can comment on or make changes to this bug.