canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,627
edits
Line 10: | Line 10: | ||
== Why Talkilla? == | == Why Talkilla? == | ||
Integrating real time communications into the browser will enhance a user's browsing experience allowing conversations to continue alongside | Integrating real time communications into the browser will enhance a user's browsing experience allowing conversations to continue alongside web navigation and the sharing of data, e.g. files and urls. | ||
WebRTC does not standardize peer discovery nor does it touch on contact and presence management. This is a significant hurdle for web sites to fully leverage | WebRTC does not standardize peer discovery nor does it touch on contact and presence management. This is a significant hurdle for web sites to fully leverage RTC. Talkilla aims at offering some of those features through web application APIs, as a reflection of what individual Service Providers have to offer. | ||
In addition, Talkilla provides a set of ready made use cases UI in order to deliver | In addition, Talkilla provides a set of ready made use cases UI in order to deliver an integrated RTC experience in the browser. Using those, operators will for example be able to expand their networks with Talkilla to let their users make and receive calls to and from the Internet and provide them with value-added services e.g. in-depth call histories, account details. | ||
More generally, developers will be provided with APIs where they can hook into Talkilla and provide different functionalities and web applications for users based on Talkilla's core services. | More generally, developers will be provided with APIs where they can hook into Talkilla and provide different functionalities and web applications for users based on Talkilla's core services. |