Confirmed users
398
edits
WebAPI/AppDefinedTeleophony: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
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 == | ||