Early attempts at bringing the Internet experience to the mobile phone were dependent on microbrowser technologies, such as WAP, to compensate for the lack of capability in contemporaneous devices, and the low bandwidth and high latency of the GPRS networks at the time. This situation is now changing with leading browsers from the likes of S60, Opera, Access and Apple supporting many of the Web technologies used in the desktop space today. Opera Mobile for S60 passed the Acid2 test in 2006 making it the very first mobile browser to pass the Acid2 test. Preservation of the original page layout Pointer navigation Easy navigation of Web pages through page miniatures or sophisticated zooming Visual History (an easy-to-use back function, showing miniature views of previous pages) Text Search (which works as you type, taking you directly to the interesting part of the page) Landscape mode Web Feeds (ability to subscribe to RSS feeds from Web sites, blogs, and news services) Etc.
Browser functionality separated from the core rendering and scripting engine
In some respects it no longer matters what the underlying platform is; in order to stimulate mobile application development we need something which can ride across the top of all the different platforms
An example is MobileScript developed by VF Group R&D which extends the scripting capabilities of a Web Runtime to bind to the APIs provided by the underlying platform; by modelling a mobile handset by means of a Document Object Model it provides developers with: access to Device properties ability to invoke services and Handle events
In reality all these technologies will be complementary…. Animated slide 1. Start with a blank graph 2. First name and show the 3 axis: Rapid development, Rich set of APIs, Reach (deployment) 3. Show where native lies - rich set of APIs but steep learning curve and reach dependent on developing to multiple platforms although TPP seeking to address this by reducing number of platforms 4. Show where Java lies - easier to develop to but inconsistent set of APIs across different implementations 5. Web runtime (S60, Opera) - leverages Web for easy development and browser-based enables cross-platform deployment but restricted API set 6. Avoids steep learning curve by leveraging familiar Web technologies and existing tools 7. What we need to do is extend the Web runtime approach with a richer set of platform APIs 8. And the key to maintaining the ubiquitous reach of Web runtimes is to open up and standardise these enhancements
But what is certain is that… Web Experiences will become an increasing part of how we use phones and interact with friends & family - RSS feeds such as weather forecasts or sports fixtures embedded into the calendar - eBay auction notifications displayed directly on the idle screen - And flickr photos and blog entries embedded into the address book
Traditional Telco model OpCo drives bulk of services via Portal Content providers and some ASPs partner with OpCo to deliver content via portal Other ASPs attempt to deliver their own services off-net but hampered by fragmented application framework space on the terminal Evolved Telco model As Terminal space becomes less fragmented, ASPs able to deliver services more easily and compete with Portal OpCo opens up network APIs and partners with ASPs to mitigate against disintermediation and hopefully also grow mobile data revenues BUT arrival of additional platform choices threatens to fragment the mobile apps space again Web 2.0 model Web Runtime provides consistent execution environment across all devices Rapid development and deployment using Web technologies fosters a myriad of beta services hence pushing out the Long Tail diminishing relevance of OpCo Portal Web Runtime evolves with access to device APIs – Network APIs lose value to 3rd parties
Web Runtimes – evolving beyond the browser David Pollington Vodafone Group R&D Feb 2008 MoMo London
Increasing support for Web technologies WAP iMode S60 Opera
Web Runtime benefits <ul><ul><li>Lowers the entry barriers </li></ul></ul><ul><ul><li>Reduces development time </li></ul></ul><ul><ul><li>Lowers the entry barriers </li></ul></ul><ul><ul><li>Reduces development time </li></ul></ul><ul><ul><li>Decouples application development </li></ul></ul><ul><ul><li>Allows dynamic update </li></ul></ul>
Enhancing the Web Runtime with device APIs <ul><li>Device APIs: </li></ul><ul><ul><li>File system access to pictures, music and video clips </li></ul></ul><ul><ul><li>PIM data (contacts, calendar) </li></ul></ul><ul><ul><li>Messaging (SMS, MMS, email) </li></ul></ul><ul><ul><li>Call handling </li></ul></ul><ul><ul><li>System data (battery, coverage, roaming, location) </li></ul></ul><ul><ul><li>Camera (get new picture) </li></ul></ul><ul><li>Adds context </li></ul><ul><li>Mashups </li></ul>Terminal functionality & user data Web information Web app
Comparing Runtimes Rapid development Reach Rich set of APIs Web pages Widgets Games Complex apps using low level APIs Industry initiative Native Proprietary device API implementation
Web Experiences Will Become An Increasing Part Of How We Use Our Phones
Shifting service landscape Ghost of Xmas past Ghost of Xmas present Ghost of Xmas yet to come? Network Network APIs On-net 3 rd party ASPs Portal Off-net Multitude of different application frameworks necessitates multiple ports of the same application Web services Network Network APIs On-net 3 rd party ASPs Portal Off-net Web Runtime Beta services Device APIs Network Net APIs On-net 3 rd party ASPs Portal Off-net S60 Java Network Net APIs On-net 3 rd party ASPs Portal Off-net S60 Java Android iPhone LiMo
T + 44 1635 685504 [email_address] David Pollington Vodafone GROUP R&D.UK Vodafone House The Connection Newbury, Berkshire RG14 2FN http://www.vodafonebetavine.net/web/MobileScripting/ https://forge.vodafonebetavine.net/projects/mobilescript/
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.