Closed Bug 1007932 Opened 10 years ago Closed 9 years ago

Allow to enclose a contact (serialized as vCard) as a message attachment

Categories

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

defect
Not set
normal

Tracking

(feature-b2g:2.2+, tracking-b2g:backlog, b2g-v2.2 verified, b2g-master verified)

VERIFIED FIXED
2.2 S3 (9jan)
feature-b2g 2.2+
tracking-b2g backlog
Tracking Status
b2g-v2.2 --- verified
b2g-master --- verified

People

(Reporter: adamone, Assigned: jmcf)

References

Details

Attachments

(8 files, 5 obsolete files)

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release)
Build ID: 20140428193609

Steps to reproduce:

I've saved some contacts than I wanted to send one phone number to an other contact. I tried to find option for it also tried to attach contact card to an email.


Actual results:

I didn't find any way to send a phone number to an other contact


Expected results:

There should be an option to send contact card to a phone number or an other contact. Also it would useful to be able to attach contact to an email.
Adding blocking-b2g to backlog, we think this is an interesting nice feature to add to FxOS. We would like Mozilla to consider it in their roadmap.
blocking-b2g: --- → backlog
Assignee: nobody → jmcf
Target Milestone: --- → 2.2 S1 (5dec)
Attached file [Contacts] UX Spec. Share Vcard (obsolete) —
This spec shows how a user might be able to share a Vcard via MMS while being in Contact Details within Contacts app.

Carrie, I would need some feedback on this, please.

Thanks :).
Flags: needinfo?(cawang)
Attached file [2.0 Messages] SharevCard v1.pdf (obsolete) —
This spec shows how a user might be able to attach a Vcard via MMS while being in a conversation within SMS app.

Jenny, I would need some feedback on this, please.

Thanks :).
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Not able to send contact card → Allow to send a contact (serialized as vCard) enclosed in a message's attachment
Setting ni to Jenny according comment 3
Flags: needinfo?(jelee)
Hi Pau,
See my comments below:
- Screen 3-4: Please refer to the share contact via BT flow (Contacts> settings> export contacts> Bluetooth) for the correct picker flow. 
- Last screen (contact detail view): we probably don't want to allow user to access the functions here, ex. call, send message, consider gray out the buttons or re-layout so that it will be "pure preview".
- What about sharing multiple contacts at the same time?

Thanks!
Flags: needinfo?(jelee)
Hi, 

My suggestion is that maybe we can move this share contact button to the "SOCIAL NETWORKS" section. Thanks!
Flags: needinfo?(cawang)
(In reply to Carrie Wang [:carrie] from comment #6)
> Hi, 
> 
> My suggestion is that maybe we can move this share contact button to the
> "SOCIAL NETWORKS" section. Thanks!

This bug is for attaching the contact in a message, but being the caller (the app which initiates the flow) the messaging app and not the contacts app. The other flow Contacts --> Msging would be a different feature.
(In reply to Jenny Lee from comment #5)
> Hi Pau,
> See my comments below:
> - Screen 3-4: Please refer to the share contact via BT flow (Contacts>
> settings> export contacts> Bluetooth) for the correct picker flow. 
> - Last screen (contact detail view): we probably don't want to allow user to
> access the functions here, ex. call, send message, consider gray out the
> buttons or re-layout so that it will be "pure preview".
> - What about sharing multiple contacts at the same time?
> 
> Thanks!

Hi all,

I think we are overcomplicating the feature. So what we are planning right now is to extend the pick contact activity to allow to send a vCard as a result. 

So the flow would be Messaging App --> Attach --> Contact --> Contact list --> User chooses a Contact --> Contact is attached. 

In the future we will be considering attaching multiple contacts but that will be a new feature for v2.2. To clarify, What we are planning to do here is a simple patch (implementing what I've described above) aimed at uplifting it to v2.1 . 

Hope this clarifies
Summary: Allow to send a contact (serialized as vCard) enclosed in a message's attachment → Allow to enclose a contact (serialized as vCard) as a message attachment
(In reply to Jenny Lee from comment #5)
> Hi Pau,
> See my comments below:
> - Screen 3-4: Please refer to the share contact via BT flow (Contacts>
> settings> export contacts> Bluetooth) for the correct picker flow. 

Jenny, here I agree with Jose Manuel since I believe the Export contacts via BT flow would be much complicated for the user to get to same objective, which is simply attaching a contact in a SMS conversation.

Regarding the other changes you suggested, I'm working on them and I'll attach the new version ASAP.
Thanks!
Here's spec updated. Carrie, can you confirm it is ok?

Thanks!
Attachment #8522808 - Attachment is obsolete: true
Setting ni to Carrie to review the spec attached by Pau in comment 10
Flags: needinfo?(cawang)
Hi, 

I think overall it looks fine to me, but from comment 8, aren't we doing the part of attaching a vcard from message? but the updated version is sharing from contacts (I'm quite confused now). 
Also,ni? Jenny to double confirm the MMS part. Thanks!
Flags: needinfo?(cawang) → needinfo?(jelee)
Attached file [2.0 Messages] SharevCard v1.pdf (obsolete) —
Attachment #8522810 - Attachment is obsolete: true
Hi Pau,

(Comment based on attachment 8527567 [details]) Looks fine to me except for:
Screen 2 - Maybe consider moving Contact to the last on the menu since media content is more likely to be attached 
Screen 5 - "Converting to multimedia message" banner is missing, and the title should probably be "MMS"

Let's see if Carrie is ok with the contact picker flow too. Thanks!
Flags: needinfo?(jelee) → needinfo?(cawang)
Attached file [2.0 Messages] SharevCard v1.pdf (obsolete) —
Here I attach the new spec according to Jenny's comments. Just waiting for Carrie's approval. Thanks to both! :)
Attachment #8527567 - Attachment is obsolete: true
Postponing for next sprint. We have too many things in our place, will take this the next sprint.
Target Milestone: 2.2 S1 (5dec) → 2.2 S2 (19dec)
Hi, 

Only one suggestion. We shall replace the Screen 4 with the "Contact Details View" so that users will not call/ message the contact during Vcard sharing process. Thanks!
Flags: needinfo?(cawang)
Ok! Changes applied. Thanks!
Attachment #8527683 - Attachment is obsolete: true
(In reply to Pau Masiá [:Pau] from comment #18)
> Created attachment 8528230 [details]
> [2.0 Messages] SharevCard v1.pdf
> 
> Ok! Changes applied. Thanks!

The pick activity would only allow you to select a contact, i.e. you are not going to be able to see the contact detail from the activity. I think that's a reasonable assumption and not very harmful, are you ok with that?

thanks!
These are the small changes proposed at Contacts App Level. At least the SMS and email apps would need to be modified as well in order to support this new kind of attachment
Attachment #8529712 - Flags: feedback?(francisco)
Comment on attachment 8529712 [details]
Contacts Part. Pick Activity returning an vcard blob

I like this approach, I though we were going to allow multiple selection, but as a first step is ok.

We reuse, the activity, since we are doing a pick with a specific mime type.

Just left a comment on github, please sync with Julien as this will require integration with SMS (and probably email)
Flags: needinfo?(felash)
Attachment #8529712 - Flags: feedback?(francisco) → feedback+
(In reply to Francisco Jordano [:arcturus] [:francisco] from comment #21)
> Comment on attachment 8529712 [details]
> Contacts Part. Pick Activity returning an vcard blob
> 
> I like this approach, I though we were going to allow multiple selection,
> but as a first step is ok.

Yes, UX and product agreed to initially only support one contact attachment at a time. 

> 
> We reuse, the activity, since we are doing a pick with a specific mime type.
> 
> Just left a comment on github, please sync with Julien as this will require
> integration with SMS (and probably email)

Julien, would you be happy if I implement the SMS part as well? But unfortunately that will not be possible until the week of Dec 08th, as I'm on vacation next week.

thanks
Hi,

I'm always happy if people do work I don't need to do ;)

I wonder if your change in the pull request is enough?
Flags: needinfo?(felash)
(In reply to Julien Wajsberg [:julienw] from comment #23)
> Hi,
> 
> I'm always happy if people do work I don't need to do ;)
> 
> I wonder if your change in the pull request is enough?

oh no, it was enough to test the activity but we would need to add an icon in the attachments section of the sms app to indicate that we are enclosing a contact ... I think we would need some visual design input as well
Julien,

Please could you do a first review and feedback over the code?. 

Regarding tests, I'm planning to do a couple of integrations tests  to test the attachment part between Contacts and Messaging apps. 

Please let me know if you think I should be doing unit tests as well, any hint would be appreciated. 

thanks, best
Attachment #8529712 - Attachment is obsolete: true
Attachment #8539220 - Flags: feedback?(felash)
Hi,

As said in comment 7 this bug will be focused on sharing a contact from Messaging app so changing the component to SMS to be more accurate. 
On the other hand, Bug 1113605 has been opened to deal with sharing a contact from "contacts detail" screen.
Thanks!
Component: Gaia::Contacts → Gaia::SMS
See Also: → 1113605
Comment on attachment 8539220 [details] [review]
Pointer to GH PR #26912

Yes, please do unit tests :) The idea is that each change you make is covered by a unit test change or a new unit test.

Please request a review from :steveck once you're ready, he knows SMIL way better than me, and he may have other phones to test (I have only Firefox OS phones).

Thanks, I really want to see this feature !
Attachment #8539220 - Flags: feedback?(felash) → feedback+
Comment on attachment 8539220 [details] [review]
Pointer to GH PR #26912

Comments from Julien addressed. I have provided both new unit and integration tests.
Attachment #8539220 - Flags: review?(schung)
Attachment #8539220 - Flags: review?(francisco)
Target Milestone: 2.2 S2 (19dec) → 2.2 S3 (9jan)
Attached image SMMS. Vcard icon 1
Here I will attach a set of three proposals for the Vcard icon when attaching a contact via MMS.

Please Fang, could you take a look to them and send me some feedback? :)
Thanks!
Flags: needinfo?(fshih)
Attached image SMMS. Vcard icon 2
Version 2
Attached image SMMS. Vcard icon 3
Version 3.
Comment on attachment 8539220 [details] [review]
Pointer to GH PR #26912

Some suggestion on github, and you might need unit test for certain changes
Attachment #8539220 - Flags: review?(schung)
Hi Pau, just a reminder that Fang took PTO until next week, please ping Carol Huang or Peko Chen instead if you want more feedback this week.
Thanks Steve! setting ni on Carol and Peko, please read from comment 29 and on.
Flags: needinfo?(pchen)
Flags: needinfo?(chuang)
Hi Pau,
For the contact card icons, personally I like version 2 the most. because to me version 3 is more like a document of information. 
Only one comment on v2: I'm just wondering if you can simplify the shape of the card, or simplify the element of the hinge.
Thanks!!
Flags: needinfo?(chuang) → needinfo?(b.pmm)
Comment on attachment 8539220 [details] [review]
Pointer to GH PR #26912

Left some comments in github for the contacts part. No mayor issues, please address them, also we will need the r+ from Steve.
Attachment #8539220 - Flags: review?(francisco) → review+
Comment on attachment 8539220 [details] [review]
Pointer to GH PR #26912

Ready for a second review round from Steve

thanks
Attachment #8539220 - Flags: review?(schung)
Thanks Carol! I also like the version 2 the most. It's more straightforward and more close to the actual object. I would simplify the shape of the hinge. Since the icon may lose some detail from our device. It would be good to keep it simple and not too much element. Thanks!
Flags: needinfo?(fshih)
Blocks: 1113605
Flags: needinfo?(pchen)
Hi Jose, I add some comments on githab, it looks good overall except some small nits. The only problem is a failed unit test. So still keeps review flag for now.
Flags: needinfo?(jmcf)
Hi Steve,

Thanks for spotting the unit test error. I have addressed your comments and now TBPL should be green.
Flags: needinfo?(jmcf)
Comment on attachment 8539220 [details] [review]
Pointer to GH PR #26912

Looks great, thanks!
Attachment #8539220 - Flags: review?(schung) → review+
landed in master:

https://github.com/mozilla-b2g/gaia/commit/c4d0ca5d7821ed7c0b3d7fca51033b0482c57cfc

There is a pending minor improvement here, the new icon for enclosed contacts. We can leave this bug open or create a follow-up. As in this bug we already have the history of the design of the icon I'm more inclined to leave this one open.
We have open follow-up bug 1119190. So closing this. setting flag for QA verification as well.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Keywords: verifyme
See Also: → 1119190
feature-b2g: --- → 2.2?
It was landed on master before FLR so we'll have it in v2.2
Flagging to 2.2+ to get QA verification.
feature-b2g: 2.2? → 2.2+
Depends on: 1119738
QA Whiteboard: [COM=Gaia::Messages]
Flags: in-moztrap?(echang)
Tested with today build in Flame( Gecko-7a1f501.Gaia-9946a49) there is an option to attach contact details(.vcf) when writing a MMS. Thank you everyone for your effort to finish it!
Hi Francisco, 
Page 4 of [2.0 Messages] SharevCard v1.pdf https://bugzilla.mozilla.org/attachment.cgi?id=8525272, when we try to view an attached VCF, it looks like an details page with any editing text box, I didn't join the conversation until now Is that a spec change? Or we need to fix that? 
http://youtu.be/BwDImXh-sCw
Flags: needinfo?(francisco)
(In reply to Eric Chang [:ericcc] [:echang] from comment #46)
> Hi Francisco, 
> Page 4 of [2.0 Messages] SharevCard v1.pdf
> https://bugzilla.mozilla.org/attachment.cgi?id=8525272, when we try to view
> an attached VCF, it looks like an details page with any editing text box, I
> didn't join the conversation until now Is that a spec change? Or we need to
> fix that? 
> http://youtu.be/BwDImXh-sCw

that's bug https://bugzilla.mozilla.org/show_bug.cgi?id=1120878
I've attached the new versions of the icon in Bug 1119190. Thanks!
Flags: needinfo?(b.pmm)
Jose already replied to my ni in comment 47
Flags: needinfo?(francisco)
Depends on: 1119190
See Also: 1119190
Depends on: 1120878
Flags: in-moztrap?(echang) → in-moztrap+
This bug has been successfully verified on Flame v2.2&3.0.
See attachment: verified_v2.2.png
Reproduce rate: 0/5.

STR:
1.Open a contact->tap Share contact icon->Select Message (or Email) to share.
**The contact can be shared as a Vcard file in Message edit page (or Email compose page).
2.Launch Messages->create a new message->add a attachment->select Communications ->select a contact.
**The contact can be added to Message app and shared as a Vcard file.

Flame v2.2 build:
Gaia-Rev        80d5b797fd0497a7e3337b7798a21b2e1219681a
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/01bf1516a65b
Build-ID        20150127002504
Version         37.0a2
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150127.035842
FW-Date         Tue Jan 27 03:58:52 EST 2015
Bootloader      L1TC000118D0

Flame 3.0 build:
Gaia-Rev        b02ec9713e6de8d96c6954d2c0dfd0442b0656ac
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/38e4719e71af
Build-ID        20150127010228
Version         38.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150127.043726
FW-Date         Tue Jan 27 04:37:39 EST 2015
Bootloader      L1TC000118D0
Status: RESOLVED → VERIFIED
QA Whiteboard: [COM=Gaia::Messages] → [COM=Gaia::Messages],MGSEI-Triage+
Keywords: verifyme
Depends on: 1138371
See Also: → 1138377
No longer depends on: 1138371
See Also: → 1138371
Depends on: 1138371
See Also: 1138371
Depends on: 1143186
blocking-b2g: backlog → ---
No longer depends on: 1143186
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: