According to the Acceptance criteria in the US bug 1010713 when the call is finished by any other reason than the other party manually terminating (for example, when connection is lost). This redial button only will be shown if the call back is possible, in other words, when the other party is a Loop registered user.
We need to check the feasibility and the deadline to implement this part of the functionality. Also we will need UX feedback to implement this redial screen.
setting ni to Rafa, Pau and Vicky for the design of this redial screen
According to the ACs in bug 1010713: "In case the call is finished by any other reason than the other party manually terminating, if the other party closes his browser or application or the other party loses Internet connection, I will get notified "Call ended by a unknown reason (or the reason of the termination if it is known) and the call failed tone will be played (The app will wait for a timeout before showing this to user just to check this is not a momentary situation but it is a permanent failure). In this case, a redial button will be shown to the user." After talking with Jose Antonio about this functionality, apart of the need of the Redial screen, we wonder if you are interested in showing the feedback screen when the call is finished by any other reason than the other party manually terminating. To be more clear, are you interested in showing the feedback screen before the redial one? are you interested in that feedback when the call is terminated in those situations? If this is case, we need to know the specific flow no only the redial screen. setting ni to Jorge too to give his feedback from Product perspective
My 2¢: let's not show the feedback screen in this case. We already know it failed by other means and presenting the user with the feedback screen will probably yield bad feedback that will only taint the otherwise interesting results after actual calls.
I´m agree with Rafa, let the feedback screen for normal termination.
Created attachment 8487047 [details] UX Proposal. Redial Here I attach the ux proposal for this scenario. I'm going to upload the screenshots separately. Thanks!
Pau, one question about your proposal, just to confirm the flow, when pressing "Go back", where do we go back? Be aware that we have two types of situations, incoming and outgoing calls. Besides, for Loop outgoing calls, we can launch them from contact details, call log and contact picker. I would like to simplify the solution as much as possible so we can have time to address the solution for 1.0 version.
When pressing the "Go back" button the user will be redirected to the screen from which he launched that call. As you mention above: either contact details, call log or contact picker.
Clearing NI as this was already taken care of.
It was decided not including it in 1.1 Loop Mobile Client version because time constrain (risky bug), we will ask to Product team if it makes sense implement it for next Loop mobile version
3 years ago
For the time being, we are not going to implement this feature, so let's close the bug as won't fix.