[messaging-app] Make it easier to resend messages that can't be sent

Bug #1417353 reported by Bill Filler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
Unassigned
Ubuntu UX
Fix Released
High
Olga Kemmet
messaging-app
Fix Released
High
Tiago Salem Herrmann
history-service (Ubuntu)
Fix Released
Undecided
Unassigned
messaging-app (Ubuntu)
Fix Released
Undecided
Unassigned
messaging-app (Ubuntu RTM)
New
Undecided
Unassigned

Bug Description

From usability testing:
Testers expected the phone to provide a resent option or to automatically resend the message when the singal is back if a message is not sent successfully

Testers received a 'no network' pop up, and the full text message stayed in the compose bar. As a result, they had to constantly check if the network is back, and then resend the message again. Phone is often used on the move, and network issue can be a common issue when such as on the train or around places where full of high buildings. It is important to design for these retrictions.

Proposed solution:
Until we have "Save as draft" support, I'd propose the following:
- If we detect No Network or No SIM Card and the user presses Send, directly add the message to the message thread, but mark it as failed (with the resend icon visible)
- Then pop up the dialog as we do today

This way, the message is part of the history and the user can resend whenever is convenient without losing their message.
Also, eventually when we have auto resend these messages will be in the queue.

Tags: usability ww07

Related branches

Bill Filler (bfiller)
Changed in messaging-app:
importance: Undecided → High
tags: added: usability ww07
Changed in messaging-app:
assignee: nobody → Tiago Salem Herrmann (tiagosh)
Changed in ubuntu-ux:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Olga Kemmet (olga-kemmet)
summary: - Make it easier to resend messages that can't be sent
+ [messaging-app] Make it easier to resend messages that can't be sent
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package history-service - 0.1+15.04.20150210-0ubuntu1

---------------
history-service (0.1+15.04.20150210-0ubuntu1) vivid; urgency=medium

  [ Tiago Salem Herrmann ]
  * Add support for writing events from qml. Iterate over attachments
    when qdbus_cast fails. (LP: #1417353)
 -- Ubuntu daily release <email address hidden> Tue, 10 Feb 2015 19:22:48 +0000

Changed in history-service (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package messaging-app - 0.1+15.04.20150211-0ubuntu1

---------------
messaging-app (0.1+15.04.20150211-0ubuntu1) vivid; urgency=medium

  [ CI Train Bot ]
  * Resync trunk

  [ Omer Akram ]
  * Provide a pre-populated database for search test so that we don't
    conflict with the On Screen Display Notification (LP: #1418074)

  [ Tiago Salem Herrmann ]
  * Inject messages into the history service when it is impossible to
    send them. (LP: #1417353)
 -- Ubuntu daily release <email address hidden> Wed, 11 Feb 2015 18:09:01 +0000

Changed in messaging-app (Ubuntu):
status: New → Fix Released
Changed in ubuntu-ux:
status: Triaged → Fix Committed
Changed in messaging-app:
status: New → Fix Released
Changed in ubuntu-ux:
status: Fix Committed → Fix Released
Changed in canonical-devices-system-image:
status: New → Fix Released
Changed in canonical-devices-system-image:
milestone: none → ww28-2015
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.