- from Slovenia, a tiny country in the middle of Europe\n- ex MarandLAB\n- I build products\n- eComm Europe veteran\n- founder of vox.io\n
- ex MarandLAB\n- I build products\n- eComm Europe veteran\n- founder of vox.io\n
- trends\n- why now\n- what have we done so far\n- the future\n
- trends\n- why now\n- what have we done so far\n- the future\n
we have seen a lot of applications move into the browser.\n\nwhy?\nconvenience, sync, accessibility and reusability\neasy sharing and integration\n\n
but mobile is big on apps, since the US discovered it in 2007 :)\n\napps rule, because the web on mobile is still limited\nusers have no preference on the channel, just their experience, and currently apps guarantee a much better experience, just like native clients did a few years ago.\n
we have seen a lot of applications move into the browser.\n\nwhy?\nconvenience, sync, accessibility and reusability\n\n
ubiquitous reachability\ndesktop vs. mobile\ngeographically\nreal-time / time-shifted\ninspired by the web - twitter profiles, Facebook vanity URLs\n----\n- I have 4 SIM cards\n- do you really expect me to message my 820 contacts each time I travel?\n- but you have that service that gives you one phone number to ring all your phones; true, but what about my friends back in Europe?\n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- there is a huge demand for tools / platforms and data sources\n- I am sure many specific use cases will be mentioned in other presentations\n- CRM is the most obvious example, however we still do not have a great product that would integrate telephony and CRM functionalities\n
\n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
\n
\n
- the basic infrastructure is available, you don’t have to talk to a telco to get your calls terminated anywhere\n- the cost of infrastructure is low\n- you can host stuff into the “cloud”\n----\n- the technology is ready\n- Flash now (p2p, echo cancellation, speex + h264 soon; G711 soon)\n- WebRTC or RTCWeb in the future (hope soon, realistically it will take a while)\n- mature network tech (several opensource projects that can be reused)\n----\n- we finally have enough understanding of design patterns for such use cases\n- several web services have emerged that suggested a new direction (as mentioned before)\n- finally and most importantly - a big number of users are ready and “get it” \n
- the basic infrastructure is available, you don’t have to talk to a telco to get your calls terminated anywhere\n- the cost of infrastructure is low\n- you can host stuff into the “cloud”\n----\n- the technology is ready\n- Flash now (p2p, echo cancellation, speex + h264 soon; G711 soon)\n- WebRTC or RTCWeb in the future (hope soon, realistically it will take a while)\n- mature network tech (several opensource projects that can be reused)\n----\n- we finally have enough understanding of design patterns for such use cases\n- several web services have emerged that suggested a new direction (as mentioned before)\n- finally and most importantly - a big number of users are ready and “get it” \n
\n
we have seen a lot of applications move into the browser.\n\nwhy?\nconvenience, sync, accessibility and reusability\n\n
This is how a browser based phone should look like in 2011, no clutter, pure simplicity - but an amazing set of features hidden under a beautiful interface.\n
\n
\n
\n
\n
but mobile is big on apps, since the US discovered it in 2007 :)\n\napps rule, because the web on mobile is still limited\nusers have no preference on the channel, just their experience, and currently apps guarantee a much better experience, just like native clients did a few years ago.\n
\n
we have seen a lot of applications move into the browser.\n\nwhy?\nconvenience, sync, accessibility and reusability\n\n
- easy import from Google contacts & LinkedIn\n- synced across the service (web/mobile)\n- \n
ubiquitous reachability\ndesktop vs. mobile\ngeographically\nreal-time / time-shifted\n----\n- I have 4 SIM cards\n- do you really expect me to message my 820 contacts each time I travel?\n- but you have that service that gives you one phone number to ring all your phones; true, but what about my friends back in Europe?\n
\n
- the basic infrastructure is available, you don’t have to talk to a telco to get your calls terminated anywhere\n- the cost of infrastructure is low\n- you can host stuff into the “cloud”\n----\n- the technology is ready\n- Flash now (p2p, echo cancellation, speex + h264 soon; G711 soon)\n- WebRTC or RTCWeb in the future (hope soon, realistically it will take a while)\n----\n- we finally have enough understanding of design patterns for such use cases\n- several web services have emerged that suggested a new direction (as mentioned before)\n- finally and most importantly - a big number of users are ready and “get it” \n
\n
google for vox.io tomaz\n
google for call tomaz\n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
\n
\n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
\n
- content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- several levels of potential integration (URL is the easiest, embed codes is the second, API is the third)\n- decouple data from network\n- allow users to distribute their data and created content\n
- import existing graphs\n- embed content in the existing service, add context to calls\n- distribute call recordings as content \n
To understand the future we must look back into the past.\n
- we will see a ubiquitous network\n- data is the name of the game (I guess we all know 4G does not feature CS telephony) \n- you will sign a contract with your platform provider (Apple, Google, Microsoft...)\n- the operator as you knew it will be just an “app” like Instagram, Twitter or Foursquare\n----\n- tech (WebRTC, RTCweb, will Skype be the alternative?)\n----\n- design will be key.\n- not design as the colors and spacing, but intelligent service design around the technology\n- hopefully I showed some of that today\n\n
To understand the future we must look back into the past.\n