WebAPI/AppDefinedTelephony: Difference between revisions

WebAPI/AppDefinedTelephony (view source)

23 bytes added , 1 October 2014

no edit summary

Confirmed users

1,340

edits

Revision as of 07:30, 14 July 2013 (view source) Thinker (talk \| contribs) (Created page with "For B2G, communication applications likes Skype, WhatsApp, LINE, Facebook, Google plus..., etc, will define their owned communication protocols for short/instant messages, voi...")		Latest revision as of 23:48, 1 October 2014 (view source) Chaasof (talk \| contribs) No edit summary
Line 106:		Line 106:

	Communication Apps should be registered with their capabilities; messaging, voice call, and video call, so a contacts app can provide correct functions on UI to the user for a given address handled by a communication App. That means we should provide an API to query capabilities of and list apps.		Communication Apps should be registered with their capabilities; messaging, voice call, and video call, so a contacts app can provide correct functions on UI to the user for a given address handled by a communication App. That means we should provide an API to query capabilities of and list apps.

			[[Category:Web APIs]]