Downloaded 15 times
Uploaded byeCommConf
Tomaz Stolfa - Presentation at Emerging Communications Conference & Awards (eComm 2011)
The document discusses emerging technologies that are replacing traditional VoIP clients and desktop applications. It describes how the browser is becoming the new platform for services like email, video, audio and documents. It also outlines new concepts for communication like disposable phone numbers that expire after one call, and making conference calls simple through shared links. The document advocates for an approach where users have a single URL to reach them across different services and profiles, and for allowing others to access APIs and build on top of the core platform.
More Related Content
Similar to Tomaz Stolfa - Presentation at Emerging Communications Conference & Awards (eComm 2011)
![[Mobile Future] Benjamin Keyser | Telefónica Digital](https://cdn.slidesharecdn.com/ss_thumbnails/benjaminkeyser-131115081545-phpapp01-thumbnail.jpg?width=640&height=640&fit=bounds)
Tomaz Stolfa - Presentation at Emerging Communications Conference & Awards (eComm 2011)
- 2. Goodbye VoIP Clients. Hello New Browser Technologies. Hello New User Cases Tomaž Štolfa vox.io founder § @tomazstolfa
- 3. Goodbye Old Hello New Tomaž Štolfa vox.io founder tomaz@vox.io § @tomazstolfa
- 4. who am I 4 tomaz@vox.io § @tomazstolfa
- 5. mobile web telephony 5
- 6. trends & concepts solutions future predictions 6
- 7.
- 8. desktop ➽ browser email / video / sound / docs 8 tomaz@vox.io § @tomazstolfa
- 9. desktop ➽ mobile apps rule mobile 9 tomaz@vox.io § @tomazstolfa
- 10. the graph is context 10 tomaz@vox.io § @tomazstolfa
- 11. ubiquitous reachability nomatter where I am & what I am doing 11 tomaz@vox.io § @tomazstolfa
- 12. content + context what / when / where / with who 12 tomaz@vox.io § @tomazstolfa
- 13. let others playtoo platform / API 13 tomaz@vox.io § @tomazstolfa
- 14.
- 15. collect calls please callme, I beg you! 15 tomaz@vox.io § @tomazstolfa
- 16. disposable phone I don’twant you to keep calling me 16 tomaz@vox.io § @tomazstolfa
- 17. simple conf calls doyou your conf call experience? 17 tomaz@vox.io § @tomazstolfa
- 18. distributable telephony take it where it matters most 18 tomaz@vox.io § @tomazstolfa
- 19. but this isnothing new they have been talking about it in 2005 saunderslog.com/voice-20/ telepocalypse.net 19
- 20. the future isnow? 20
- 21. infrastructure technology design 21
- 22. mobile | web |telephony 22
- 23. how does it please mind we are in beta tomaz@vox.io § @tomazstolfa
- 24. desktop ➽ browser email/ video / docs / music / telephony 24 tomaz@vox.io § @tomazstolfa
- 25. 25 tomaz@vox.io § @tomazstolfa
- 26. no downloads no installation 26 tomaz@vox.io § @tomazstolfa
- 27. 27 tomaz@vox.io § @tomazstolfa
- 28. 28 tomaz@vox.io § @tomazstolfa
- 29. 29 tomaz@vox.io § @tomazstolfa
- 30. desktop ➽ mobile apps rule 30 tomaz@vox.io § @tomazstolfa
- 31.
- 32. the graph phonebook /social networks 32 tomaz@vox.io § @tomazstolfa
- 33. 33 tomaz@vox.io § @tomazstolfa
- 34. ubiquitous reachability one URL to rule them all 34 tomaz@vox.io § @tomazstolfa
- 35. vox.io/tomaz 35
- 36. one URL torule them all social profiles email signatures business cards 36
- 37. vox.io/tomaz 37
- 38. 38 tomaz@vox.io § @tomazstolfa
- 39. 39 tomaz@vox.io § @tomazstolfa
- 40. content + context calls/ recordings / tags / notes / location 40 tomaz@vox.io § @tomazstolfa
- 41. collect calls quick call URLs 41 tomaz@vox.io § @tomazstolfa
- 42.
- 43. no downloads no installation no signup 43 tomaz@vox.io § @tomazstolfa
- 44. disposable expires after thefirst successful call 44 tomaz@vox.io § @tomazstolfa
- 45. vox.io/tomaz 45
- 46. super simple confcalls no numbers, no codes, just links 46 tomaz@vox.io § @tomazstolfa
- 47. let others playtoo identity / presence / billing 47 tomaz@vox.io § @tomazstolfa
- 48. and play withothers graphs / content / context 48 tomaz@vox.io § @tomazstolfa
- 49. what about thefuture? 49 tomaz@vox.io § @tomazstolfa
- 50. infrastructure technology design 50
- 51. the best wayto predict the future is to invent it. Alan Kay 51 tomaz@vox.io § @tomazstolfa
- 52. @tomazstolfa vox.io/tomaz made with
- 53. vox.io/r/supersecret 53 tomaz@vox.io § @tomazstolfa
Editor's Notes
- #2 \n
- #3 \n
- #4 \n
- #5 - 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
- #6 - ex MarandLAB\n- I build products\n- eComm Europe veteran\n- founder of vox.io\n
- #7 - trends\n- why now\n- what have we done so far\n- the future\n
- #8 - trends\n- why now\n- what have we done so far\n- the future\n
- #9 we have seen a lot of applications move into the browser.\n\nwhy?\nconvenience, sync, accessibility and reusability\neasy sharing and integration\n\n
- #10 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
- #11 we have seen a lot of applications move into the browser.\n\nwhy?\nconvenience, sync, accessibility and reusability\n\n
- #12 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
- #13 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #14 - 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
- #15 \n
- #16 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #17 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #18 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #19 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #20 \n
- #21 \n
- #22 - 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
- #23 - 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
- #24 \n
- #25 we have seen a lot of applications move into the browser.\n\nwhy?\nconvenience, sync, accessibility and reusability\n\n
- #26 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
- #27 \n
- #28 \n
- #29 \n
- #30 \n
- #31 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
- #32 \n
- #33 we have seen a lot of applications move into the browser.\n\nwhy?\nconvenience, sync, accessibility and reusability\n\n
- #34 - easy import from Google contacts & LinkedIn\n- synced across the service (web/mobile)\n- \n
- #35 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
- #36 \n
- #37 - 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
- #38 \n
- #39 google for vox.io tomaz\n
- #40 google for call tomaz\n
- #41 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #42 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #43 \n
- #44 \n
- #45 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #46 \n
- #47 - content is tied to a specific context\n- foursquare ties check-ins, tips, photos (content) to a location (context)\n- \n
- #48 - 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
- #49 - import existing graphs\n- embed content in the existing service, add context to calls\n- distribute call recordings as content \n
- #50 To understand the future we must look back into the past.\n
- #51 - 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
- #52 To understand the future we must look back into the past.\n
- #53 \n
- #54 \n
- #55 \n