Confirmed users
398
edits
WebAPI/AppDefinedTeleophony: Difference between revisions
no edit summary
(→WebSMS) |
No edit summary |
||
| Line 3: | Line 3: | ||
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. | 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 [[ | Following, this page is about changes of [[ContactsAPI]], calling history, and [[http://messaging.sysapps.org/|Messaging API]] | ||
== Contacts API == | == Contacts API == | ||
| Line 18: | Line 18: | ||
For handling changing of |status|, the App should listen on ContactsManager::oncontactchange event. | For handling changing of |status|, the App should listen on ContactsManager::oncontactchange event. | ||
== Messaging == | == Messaging API == | ||
interface SmsManager | interface SmsManager | ||
{ | { | ||
| Line 46: | Line 46: | ||
addArrivedMessage() is added to SmsManager to let communication Apps add a message for a new arriving message. |handler| is added to SmsMessage to record the application can handle replying the message. The message app is not supposed for responding for editing messages. It should wake up the handler of the message for editing. | addArrivedMessage() is added to SmsManager to let communication Apps add a message for a new arriving message. |handler| is added to SmsMessage to record the application can handle replying the message. The message app is not supposed for responding for editing messages. It should wake up the handler of the message for editing. | ||
Should we provide a way for synchronization between the database of | Should we provide a way for synchronization between the database of Messaging API and App's local storage? | ||
== Calling history == | == Calling history == | ||
| Line 54: | Line 54: | ||
The communication apps are invoked through activities or other IPC mechanism. A communication App should provide following functions. | The communication apps are invoked through activities or other IPC mechanism. A communication App should provide following functions. | ||
* initiate a voice/video call to a receiver | * initiate a voice/video call to a receiver | ||
* reply an existing message in the database of | * reply an existing message in the database of Messaging API | ||
* send a new message to a given receiver | * send a new message to a given receiver | ||
* show a user in contacts | * show a user in contacts | ||
The communicaton apps are responsible for handling incoming calls and messages. But, they store contacts, messages, and calling history in ContactsAPI, | 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. | ||