WebAPI/AppDefinedTeleophony: Difference between revisions

For B2G, communication applications likes Skype, WhatsApp, LINE, Facebook, Google plus..., etc, will define their owned communication protocols for short/instant messages, voice calling, and contacts.  The features of these applications are very similar to telephony, users may like to integrate all of them into one/or several place(s).

For most communication applications, they are comprised by contacts, calling history, messaging, and voice/video calling service.  For voice/video call, it is very different from one application to another.  So, every application should define their owned user interface to accept and initiate a call.  But, for contact, calling history, and messages, they are very similar for applications.  By integrating contact, calling history, and messages from all applications, the platform can provide better UX that users can browse and search all information at one place.

Following, this page is about changes of [[ContactsAPI]], calling history, and [http://messaging.sysapps.org/ Messaging API]

   attribute DOMString handler;  // the application that can handle voice/video calling and messaging.

|handler| and |status| field are added to ContactField interface.  With them, the contact app can invoke the correct APP to initiate a voice/video calling or concall.  For most IM now, |status| field can be used to show presence and status of a user.

== Calling history ==

There is no API for calling history.  We need a new API for that.  It must have the capability of telling what the App can handle an address/number in the calling history.

The communicaton apps are responsible for handling incoming calls and messages.  But, they store contacts, messages, and calling history in ContactsAPI, Messaging API, and calling history API.