Closed Bug 1093154 Opened 10 years ago Closed 6 years ago

[Loop] "Tell us what happened so we can improve" screen is automatically closed after a few seconds.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog)

RESOLVED WONTFIX
tracking-b2g backlog

People

(Reporter: lolimartinezcr, Assigned: borjasalguero)

References

Details

(Whiteboard: [mobile app])

Flame
eng
v2.0
Gecko-dde9d61
Gaia-7b8df99
Loop version: 1.1 , aba155c

1. Device A makes a video call to Device B.
2. Device B picks up the Loop videocall.
3. Once Loop call has been established, Device B hangs up the call.
4. Device B shows "how do you feel about firefox hello" screen, the user taps in "Sad" button.

Actual result:
"Tell us what happened so we can improve" screen appears but it is closed automatically after 6-7 seconds. User can check or uncheck options but screen is automatically closed.

Expected result:
"Tell us what happened so we can improve" screen isn't closed after 6-7 seconds.
Blocks: 1036490
Whiteboard: [mobile app]
This works as expected as this was required by UX.
(In reply to José Antonio Olivera Ortega [:jaoo] from comment #1)
> This works as expected as this was required by UX.

Agreed, as the feedback window is shown in the Call screen we can not maintain itfor a long time. Anyway, once "sad" option is selected perhaps we need some time, at least to read the options properly... 

Setting ni to Monica an Vicky so they can review the current implementation and provide their feedback about the necessary time we need to show this window.
Flags: needinfo?(vpg)
Flags: needinfo?(monica.meika)
I want to confirm with Borja, but I think that the call screen is closed after aprox. 7 seconds, independently if the user has selected the "sad" option or not. So if the user takes some time in selecting "sad" option, later he doesn't have time to read and select the cause.
Borja, can you confirm it?
Flags: needinfo?(borja.bugzilla)
Assignee: nobody → borja.bugzilla
Flags: needinfo?(borja.bugzilla)
Currently we have 10 seconds as a global timeout for closing the call screen after ending the call. This is a 'shield' in order to avoid some scenarios where the call could be blocked or frozen.
However, if we want to deal with different timers based on the user decision, we need to specify how much time we consider is enough when answering 'sad' before closing the call screen, so let's wait UX Team to get a value here!
I think that 8 seconds in first feedback screen it's ok, and 15 seconds in second feedback screen. 
23 seconds as a global timeout.
Flags: needinfo?(monica.meika)
CLearing ni as Monica is dealing with this.
Flags: needinfo?(vpg)
[Tracking Requested - why for this release]:
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.