977088 - [Messages] Change the texts for delivery/read reports

Status: RESOLVED WONTFIX

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

Description

[Julien Wajsberg [:julienw]]

From Bug 926852 comment 23, 24, 26:

And on this screen - https://bug919974.bugzilla.mozilla.org/attachment.cgi?id=8336260:

"Message Report" -> "Message Details"

"Delivery: 05th october 2013 at 11:45" -> "Sent: 5 October 2013 at 11:45"

"Read: Report requested" -> "Opened: pending"



Like for Bug 977081 I'm not sure about replacing "Delivery" with "Sent", needinfo Ayman for this.

Comment 1

[Steve Chung [:steveck]]

I don't think replacing the delivery to sent is a good idea. Like Julien said in bug 926852 comment 31, these terms have different meanings actually, and these terminology were applied since feature phone. We could have a better description about the delivery/read status, but I would suggest keep the delivery/read at least.

Comment 2

[ayman maat :maat]

Sorry I am late getting a grip on this, I should have caught this much earlier but have been somewhat distracted by other things.

(In reply to Julien Wajsberg [:julienw] from comment #0)
> From Bug 926852 comment 23, 24, 26:
> 
> And on this screen -
> https://bug919974.bugzilla.mozilla.org/attachment.cgi?id=8336260:
> 
> "Message Report" -> "Message Details"

From a UX PoV I cannot agree with this. The user requests ‘Delivery Reports’ and ‘Read Reports’ - the CTA to access these reports once requested is called ‘View message report’ (path to CTA = ‘message app’ > ‘message thread’ > long press on outgoing message) therefore the header of the ‘Report’ should be ‘Message Report’

The key word ‘Report’ in all these instances is important to continuity and discoverability/fundability and therefore ease for a user to build their mental model about the ‘Report’ experience.   

> 
> "Delivery: 05th october 2013 at 11:45" -> "Sent: 5 October 2013 at 11:45"

From a UX PoV I cannot agree with this either. There is a practical difference between ‘Send’ and ‘Delivery’. A message can be *sent* but for technical reasons never *delivered*

We record the ’Sent’ time and ‘Sent’ status in the first section of the Message Report:

      24th September 2013, 11:45 am
      <tick> Sent

referencing: https://bug919974.bugzilla.mozilla.org/attachment.cgi?id=8336260
   
We record the Delivery status within the module for each individual recipient.

      Delivered: 05th october 2013 at 11:45 

referencing: https://bug919974.bugzilla.mozilla.org/attachment.cgi?id=8336260


We should not ‘muddy the waters’ by renaming ‘Delivery’ to ‘Sent’ …because ‘Sent’ ≠ ‘Delivered’

> "Read: Report requested" -> "Opened: pending"
> 

Hypothetically changing ‘Read’ to ‘Opened’ is not a problem because in reality it is the same thing really. But as Steve rightly points out in comment 1 ‘Read’ is a establish nomenclature that has been around since feature phones and from a UX PoV I do not really see a strong enough reason to change this TBH.

Comment 3

[Julien Wajsberg [:julienw]]

(In reply to ayman maat :maat from comment #2)
> Sorry I am late getting a grip on this, I should have caught this much
> earlier but have been somewhat distracted by other things.
> 
> (In reply to Julien Wajsberg [:julienw] from comment #0)
> > From Bug 926852 comment 23, 24, 26:
> > 
> > And on this screen -
> > https://bug919974.bugzilla.mozilla.org/attachment.cgi?id=8336260:
> > 
> > "Message Report" -> "Message Details"
> 
> From a UX PoV I cannot agree with this. The user requests ‘Delivery Reports’
> and ‘Read Reports’ - the CTA to access these reports once requested is
> called ‘View message report’ (path to CTA = ‘message app’ > ‘message thread’
> > long press on outgoing message) therefore the header of the ‘Report’
> should be ‘Message Report’
> 
> The key word ‘Report’ in all these instances is important to continuity and
> discoverability/fundability and therefore ease for a user to build their
> mental model about the ‘Report’ experience.   

Note that this is for the panel's title. In this panel we're really showing more details about the message. Reports are part of the details, but there are details that are not reports (eg: sent timestamp, message size, message status).

This is actually the only change I'd vouch for.

> 
> > 
> > "Delivery: 05th october 2013 at 11:45" -> "Sent: 5 October 2013 at 11:45"
> 
> From a UX PoV I cannot agree with this either. There is a practical
> difference between ‘Send’ and ‘Delivery’. A message can be *sent* but for
> technical reasons never *delivered*
> 
> We record the ’Sent’ time and ‘Sent’ status in the first section of the
> Message Report:
> 
>       24th September 2013, 11:45 am
>       <tick> Sent
> 
> referencing: https://bug919974.bugzilla.mozilla.org/attachment.cgi?id=8336260
>    
> We record the Delivery status within the module for each individual
> recipient.
> 
>       Delivered: 05th october 2013 at 11:45 
> 
> referencing: https://bug919974.bugzilla.mozilla.org/attachment.cgi?id=8336260
> 
> 
> We should not ‘muddy the waters’ by renaming ‘Delivery’ to ‘Sent’ …because
> ‘Sent’ ≠ ‘Delivered’

There was also a slight date format change in the proposal. Although I'm not sure if we can do it :)

> 
> > "Read: Report requested" -> "Opened: pending"
> > 
> 
> Hypothetically changing ‘Read’ to ‘Opened’ is not a problem because in
> reality it is the same thing really. But as Steve rightly points out in
> comment 1 ‘Read’ is a establish nomenclature that has been around since
> feature phones and from a UX PoV I do not really see a strong enough reason
> to change this TBH.

I think the main issue was the "Report requested" line, with a capital letter, and quite technical words. Not that I really mind here, though.

Needinfo mainly for the first paragraph.

Comment 4

[Matej Novak [:matej]]

Using "delivery" sounds right to me, but I've lost track of the exact strings. Can someone summarize what we're proposing now? Thanks.

Comment 5

[Julien Wajsberg [:julienw]]

I would go for:

"Message Report" -> "Message Details"

"Delivery: 05th october 2013 at 11:45" -> "Delivered: 5 October 2013 at 11:45"
(or keep "delivery", but try to change "05th" to "5")

"Read: Report requested" -> "Read: Report pending"
(not necessary)

Comment 6

[Matej Novak [:matej]]

I would prefer "delivered" so it's in the same part of speech as "read." And if we use "read" here, we should also use it in the other bug.

Is the date format dictated by the phone (i.e. will it change if the user selects a different language)?

Comment 7

[Julien Wajsberg [:julienw]]

(In reply to Matej Novak [:matej] from comment #6)
> I would prefer "delivered" so it's in the same part of speech as "read." And
> if we use "read" here, we should also use it in the other bug.

I think "Delivered" is also what was in the original UX spec.
 
> Is the date format dictated by the phone (i.e. will it change if the user
> selects a different language)?

2 answers here:
* we use an API that should change according to the locale [1]
* we also keep the format in the locale files so that it's easy to change if necessary

[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toLocaleFormat

Comment 8

[David Scravaglieri [:scravag]]

Definitely not a blocker must be checked with pike if it's on time for l10n in 1.4

Comment 9

[Axel Hecht [:Pike]]

Please don't ask me schedule questions, I don't have answers.

My personal take is that this feature is broken.

Re localizing dates: There's code for that in /shared. toLocaleFormat doesn't work in b2g, as it's forwarding to libc, at least in the absence of ICU/js globalization api. And we're not shipping a localized libc.

Comment 10

[ayman maat :maat]

fine

Comment 11

[Julien Wajsberg [:julienw]]

Mass closing of Gaia::SMS bugs. End of an era :(

Comment 12

[Julien Wajsberg [:julienw]]

Mass closing of Gaia::SMS bugs. End of an era :(