Tomaz Stolfa - Presentation at Emerging Communications Conference & Awards (eComm 2011)
•Als KEY, PDF herunterladen•
0 gefällt mir•549 views
Please see blog http://blog.eComm.ec
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Andere mochten auch
Andere mochten auch (10)
Mehr von eCommConf
Mehr von eCommConf (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
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. trends 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 no matter 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 play too platform / API 13 tomaz@vox.io § @tomazstolfa
- 14. a few concepts 14
- 15. collect calls please call me, I beg you! 15 tomaz@vox.io § @tomazstolfa
- 16. disposable phone I don’t want you to keep calling me 16 tomaz@vox.io § @tomazstolfa
- 17. simple conf calls do you 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 is nothing new they have been talking about it in 2005 saunderslog.com/voice-20/ telepocalypse.net 19
- 20. the future is now? 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. 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 to rule 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. vox.io/qc/pvXTv8 42
- 43. no downloads no installation no signup 43 tomaz@vox.io § @tomazstolfa
- 44. disposable expires after the first successful call 44 tomaz@vox.io § @tomazstolfa
- 45. vox.io/tomaz 45
- 46. super simple conf calls no numbers, no codes, just links 46 tomaz@vox.io § @tomazstolfa
- 47. let others play too identity / presence / billing 47 tomaz@vox.io § @tomazstolfa
- 48. and play with others graphs / content / context 48 tomaz@vox.io § @tomazstolfa
- 49. what about the future? 49 tomaz@vox.io § @tomazstolfa
- 50. infrastructure technology design 50
- 51. the best way to 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
Hinweis der Redaktion
- \n
- \n
- \n
- - 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
- \n
- \n
- \n