canmove, Confirmed users
2,887
edits
WebAPI/ContactsAPI: Difference between revisions
Jump to navigation
Jump to search
→Priority 6 feature requests: add bunch more feature requests, ContactTelephone favorite, carrier, category and outstanding questions
m (→Proposed API) |
(→Priority 6 feature requests: add bunch more feature requests, ContactTelephone favorite, carrier, category and outstanding questions) |
||
| Line 185: | Line 185: | ||
=== Priority 6 feature requests === | === Priority 6 feature requests === | ||
Features requested by one or more individuals which are not in any existing device implementations. Wish list. | Features requested by one or more individuals which are not in any existing device implementations. Wish list. | ||
* formal-name | |||
Contact properties: | |||
* '''formal-name''' - suggestion from Jonas. Like name, but with all "honorable so and so" etc. included as you would formally address or introduce someone. needs examples of publication on the web, and/or device address books that actually include such a field (haven't seen one yet). Outstanding questions: | |||
** what existing device address books have a field in the UI? | |||
*** what do they export in vCards when such a field is used? | |||
** are there any examples of real world websites that publish this property? | |||
* custom dates | * custom dates | ||
* | * favorite contact (as a native feature rather than workaround with category:favorite) | ||
* tagged fields - allow any contact field to be arbitrarily tagged with one or more tags by the user. | * tagged fields - allow any contact field to be arbitrarily tagged with one or more tags by the user. | ||
* t-shirt size - as used in https://phonebook.mozilla.org | * '''t-shirt-size''' - as used in https://phonebook.mozilla.org | ||
ContactTelephone properties: | |||
* '''favorite''' - suggestion from Jonas. Which phone number of several of a contact is a "favorite" that is caller prefers to use. Seems similar to the PREF value for the 'type' property, which is however the preferred means of the callee, not the caller. | |||
* '''category''' - suggestion from Jonas. The field would be an array of strings. That way we can add "favorite" to the category array to favorite a phone number, and we could add "operator:Telephonica" to indicate a particular operator. | |||
* '''carrier''' per request from Telefonica. Recommendation: postpone til after v1. Outstanding questions: | |||
** What problem is it solving? | |||
*** Rates in Brazil depend a lot on the carrier of the person you are communicating with. | |||
** Is this a "nice to have" stretch innovative feature or is it a competitive parity feature? In which case... | |||
*** What existing device address books have a field in the UI? | |||
**** A quick search didn't turn up any prior art. | |||
**** When found, what do they export in vCards when such a field is used? | |||
** Can this information be automatically determined rather than user-entered? | |||
*** This information is available in operator network infrastructure (HLR), there are also some services that offer this information publicly, and some applications are built in different countries to expose that information. In Spain, for instance [http://www.rawnak.com/914-discover-the-operator-of-your-contacts-with-whatsop-for-android/ an app in the Android Market] for doing it. Unknown how to do this in Brazil. | |||
** Problem: adds additional burden to the user to investigate and fill out the carrier of phone numbers from friends. How exactly is the user supposed to be able to *know* what carrier the number is associated with in order to pick it? | |||
*** E.g. personally in the US we have no idea if the cell phone numbers of friends are serviced by AT&T, Verizon, Sprint, T-Mobile, Virgin Mobile etc. and frankly, don't (and shouldn't) care, since the functionality is equivalent. | |||
=== Out of scope === | === Out of scope === | ||