Closed Bug 807782 Opened 12 years ago Closed 12 years ago

Writing a text message, then selecting a contact to send it to, does not make it clear how to actually send the message

Categories

(Firefox OS Graveyard :: Gaia::Contacts, defect, P1)

x86_64
Linux
defect

Tracking

(blocking-basecamp:+)

RESOLVED WORKSFORME
blocking-basecamp +

People

(Reporter: bjacob, Assigned: jmcf)

Details

(Keywords: b2g-testdriver, unagi, Whiteboard: Interaction , SMS)

STR:

 - on home screen, click the second icon at bottom, for text messaging
 - compose your text message
 - click top-right 'person' icon to select a contact to send it to
 - select a contact
 - now you land on that contact's details page. There is no clear button to say "OK, that's the contact I want to send that to. Now go send it!"
 - to make things more confusing, there is an icon in the top-right corner that looks like a pen writing a letter. I thought it would be the "send message" button. But it only takes me to the page to edit this contact.
Blocking-. Good usability feedback, Benoit. This is something we will monitor. Sounds like this may also be related to a bug.
We're not able to reproduce this, as tapping the contact should take you back to the compose screen.  Can you retry in current builds?
blocking-basecamp: ? → +
I'll retry as soon as I get an update for my unagi.
Component: Gaia → Gaia::Contacts
I just took a look at this one, and while it does appear to work, it is a bit cludgy. I think this screen could definitely be improved, and here's a few of my thoughts:

1 - Tapping the contact takes you right into the message thread with that contact. This pattern this leaves no way for multi-recipient messages in the future. I think waiting until after the message is sent to take you to the thread might be better.

2 - As you are now inside of a message thread, there is no way to delete the previously chosen contact.

3 - Focus is not applied to the message field on load after tapping on a contact.
Flags: needinfo?(jcarpenter)
Josh do you think we should change something in a UX point of view ?
Assignee: nobody → jmcf
ok so, we have this problem because the implementation does not follow the specifications:

referencing wireframes: HTML5_SMS_20120810_R2S1_V7.0

(https://www.dropbox.com/sh/iz77fgagyd3pb7w/g78AmVFmnc)

Page 11

1) The contact list when launched from the SMS app should not display the add contacts icon or the settings icon in the top right hand corner.


2) upon tap on a contact
- If a contact within the contact list has only one phone number irrespective of ‘type ’of phone number
	- clicking the contact in the contact list returns user immediately to the message thread with the contacts name populating the ‘To’ field.
- If a contact has more than one phone number irrespective of ‘type ’of phone number
	- clicking the contact in the contact list opens wireframe ‘SMS : contact list phone numbers’ (page 12 of same document)
- If a contact within the contact list does not have a phone number
	- dialogue informing the user that there is no phone number is opened. 


Let me know if you require any more clarification
Priority: -- → P1
Whiteboard: Interaction SMS
Whiteboard: Interaction SMS → Interaction , SMS
WFM in today's build, according to the steps in comment #0. I select a contact and it goes directly to the sms edit screen, with that contact populated.

For comment #4 & comment #6, please file new bugs.
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(jcarpenter)
Resolution: --- → WORKSFORME
(In reply to Dietrich Ayala (:dietrich) from comment #7)
> WFM in today's build, according to the steps in comment #0. I select a
> contact and it goes directly to the sms edit screen, with that contact
> populated.
> 
> For comment #4 & comment #6, please file new bugs.

Hey Dietrich

Can you please clarify what other bugs need to be raised from comment #6? I have reviewed the current build and I cannot see any issues right now that *directly* relate to what was written in comment #6. 

Thanks
You need to log in before you can comment on or make changes to this bug.