User Story: When I send a message to more than one recipients, I should be taken back to the thread-list view where a thread for each number I messaged will be available. (note: this is pending UX approval as of the 8.0 version of the spec)

This is now the agreed upon behaviour for v1.1. As there is no concept of a "group message", only mass-messaging, the user should be redirected to the thread list to access all the possible threads created.

That's going to be a big thing in Gecko. For SMS, there's never group message, so this somehow unites behaviours of SMS and MMS. But then do we still need 'thread id'? It will then have identical meaning of 'number'. And we don't need an array for thread::participants because there is always one person. Besides, what's the desired behaviour for received, multiple recipients, MMS messages? What happens if you're going to reply all?

In this case we need to follow the requirements detailed in WF. AFAIK in the case of MMS to a group, we will use the thread_id as usual. However in the case of SMS, as 'Grouping' is not a feature supported by the network, we could go back to the thread-list and show the 'new' threads created. Ping Ayman here for getting more info.

Hi All referencing wireframe pack: HTML5_SMS-MMSUserStorySpecifications_20130503_V8.0 __steps__ 1) user constructs message in 'new message' mode (page 6) 2) user adds more than one recipient 3) user selects send __expected__ a) message is sent b) mode is switched from 'new message' to 'sent message' (page 35) c) user will remain in 'sent message' mode (page 35) until they actively navigate away from it.....They are not transfered to the inbox (page 12)

(In reply to ayman maat :maat from comment #4) > __expected__ > a) message is sent > b) mode is switched from 'new message' to 'sent message' (page 35) > c) user will remain in 'sent message' mode (page 35) until they actively > navigate away from it.....They are not transfered to the inbox (page 12) Then what happen when we navigate back to thread list view? Are there three different new threads for group SMS?

(In reply to Vicamo Yang [:vicamo][:vyang] from comment #5) > (In reply to ayman maat :maat from comment #4) > > __expected__ > > a) message is sent > > b) mode is switched from 'new message' to 'sent message' (page 35) > > c) user will remain in 'sent message' mode (page 35) until they actively > > navigate away from it.....They are not transfered to the inbox (page 12) > > Then what happen when we navigate back to thread list view? Are there three > different new threads for group SMS? Hey there Vicamo Referencing wireframe pack: HTML5_SMS-MMSUserStorySpecifications_20130503_V8.0 pages 12, 13, 14, 15 There is a single outgoing thread created for a group SMS. This has been in the wireframe specifications since Feb 6th 2013 when casey was leading them. Let me know if you require any more clarification on functionality. Ayman

This will actually end up being addressed as part of https://bugzilla.mozilla.org/show_bug.cgi?id=868679 (simply a side effect of updating the app to use threadId instead of "number")

Rick confirmed was fixed by bug 868679.

in-moztrap+, tag: Messages-001