Open mxandreas opened 1 week ago
We had a short sync with @americanrefugee and concluded that from the UX perspective it makes the most sense to solve this in the same way as text messages:
@manuroe could you please confirm that this is not feasible to be done until we have implemented the local echo for file upload. Once the latter is there, it becomes fairly straightforward / easy?
@manuroe could you please confirm that this is not feasible to be done until we have implemented the local echo for file upload. Once the latter is there, it becomes fairly straightforward / easy?
This is correct. Media do not appear in the timeline until they are received by the server, which will not happen in this case.
If we want to add such alert now, we need to do it in the current blocking sending flow.
Description
Background
When sending a text message, it currently fails to send in case of these 2 scenarios.
The message appears on the timeline with a "failure" indicator, and user can tap on it to send it anyway (or additionally withdraw verification). The respective design [1, 2] for reference (iOS version).
The challenge is that when a user is trying to send a file, they will not see anything on the timeline. Sending the media just fails with a general error message and the user has no idea what is wrong. Also, besides just knowing what is wrong, the user must also be able to continue messaging.
Story
Acceptance criteria
Size estimate
None
Dependencies
Out of scope
Open questions
Subtasks