<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2009:/1/tag:www.readwriteweb.com,2009://1.14476-</id>
  <updated>2009-11-22T00:30:40Z</updated>
  <title>Comments for The Future of Mobile (Live from the Web 2.0 Expo)</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.23-en</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=14476" title="The Future of Mobile (Live from the Web 2.0 Expo)" />
    <published>2009-04-02T19:32:20Z</published>
    <updated>2009-04-03T00:08:10Z</updated>
    <title>The Future of Mobile (Live from the Web 2.0 Expo)</title>
    <summary>This morning at the Web 2.0 Expo in San Francisco, Jason Grigsby of Cloud Four, a mobile and web development firm, presented at a session about the mobile web&apos;s future. Specifically, he focused on the different types of mobile applications we have today - native apps, mobile web apps, and hybrid apps - and the...</summary>
    <author>
      <name>Sarah Perez</name>
      <uri>http://www.sarahintampa.com</uri>
    </author>
    
    <category term="Mobile Services" />
    
    <category term="Trends" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img src="http://www.readwriteweb.com/images/iphone.png">This morning at the <a href="http://www.web2expo.com">Web 2.0 Expo</a> in San Francisco, Jason Grigsby of <a href="http://cloudfour.com/">Cloud Four</a>, a mobile and web development firm, presented at a session about the mobile web's future. Specifically, he focused on the different types of mobile applications we have today - native apps, mobile web apps, and hybrid apps - and the challenges of developing across multiple platforms.</p>]]>
      <![CDATA[
<p>The question that Grisby raised during his presentation is an important one: <em><strong>are native applications really the future of the mobile web?</strong></em> Applications built specifically for one device, such as the iPhone, aren't necessarily any more capable than those built using web technology. In fact, they can even tap into the functionality of the phone's hardware itself like the accelerometer and geolocation features. <em>(Really!)</em> </p>

<p>In fact, the ability for mobile web developers to get their apps on a number of platforms without having to start from scratch each time has been made even easier as of late thanks to a new project called <a href="http://phonegap.com/">Phonegap</a>. This open source development tool is actually a web-based platform that lets developers build apps in HTML and JavaScript while also allowing those apps to take advantage of the core features in the iPhone, Android, and Blackberry. </p>

<p><embed src="http://blip.tv/play/xAzxwhuDxWs" type="application/x-shockwave-flash" width="320" height="240" allowscriptaccess="always" allowfullscreen="true"></embed> </p>

<p>When you <a href="http://www.phonegap.com/projects">look at the type of applications built using this technology</a>, you may be surprised. If you didn't already know they were made using PhoneGap, you may have thought that they were native applications. Take the <a href="http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=304052077&amp;mt=8">Blok-Buster game</a> (iTunes URL) for example, a Tetris-inspired game that involves clearing similarly-colored blocks from the screen. You can tilt the phone horizontally, vertically, or even flip it upside down and it behaves just as a native application would. Yet it is just a web app using the PhoneGap's functionality. </p>

<p>Technology like this can speed up the process of getting applications deployed across a number of platforms. That's something that is more critical than ever as we move forward with mobile web development. Today, there are just too many languages and platforms to code for and in the future there could be even more. So, perhaps we shouldn't be focused solely on native applications as the future of the mobile web after all. <strong><em>Maybe the future of the mobile web will just be the future of the web</em></strong>. </p>

<p>There are a number of fascinating figures and observations from Grigsby's presentation (embedded below) about the state of the mobile web and the challenges ahead. It's definitely worth a look.</p>

<p><div style="width:425px;text-align:left" id="__ss_1233981"><a style="font:14px Helvetica,Arial,Sans-serif;display:block;margin:12px 0 3px 0;text-decoration:underline;" href="http://www.slideshare.net/grigs/native-vs-web-vs-hybrid-mobile-development-choices?type=presentation" title="Native vs. Web vs. Hybrid: Mobile Development Choices">Native vs. Web vs. Hybrid: Mobile Development Choices</a><object style="margin:0px" width="425" height="355"><param name="movie" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=w2e-sf-090401105715-phpapp02&stripped_title=native-vs-web-vs-hybrid-mobile-development-choices" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=w2e-sf-090401105715-phpapp02&stripped_title=native-vs-web-vs-hybrid-mobile-development-choices" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"></embed></object><div style="font-size:11px;font-family:tahoma,arial;height:26px;padding-top:2px;">View more <a style="text-decoration:underline;" href="http://www.slideshare.net/">presentations</a> from <a style="text-decoration:underline;" href="http://www.slideshare.net/grigs">grigs</a>.</div></div></p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:131882</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c131882" />
    <title>Comment from Gareth on 2009-04-02</title>
    <author>
        <name>Gareth</name>
        <uri>http://www.linkedIn.com/in/garethwong</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.linkedIn.com/in/garethwong">
        <![CDATA[<p><br />
This is brilliant, <br />
seems to me Phonegap is the way to go, </p>

<p>There are just too many standards/factions across Web/mobile/telecoms sector. </p>

<p>Not since GSM/ETSI success of the 90s (some might argue it was too successful), and the fragmentations of standards that led to now the failures of likes of Nortel. </p>

<p>Java/open source are way to go.. </p>

<p>Lets focus on what really matters, namely: what consumers/users need and their perceive (real) benefits and what they are happy to pay for that service..</p>

<p>Future is bright for the right people with the right tool & services. </p>

<p>@GarethWong</p>]]>
    </content>
    <published>2009-04-02T21:27:04Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:131885</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c131885" />
    <title>Comment from Todd on 2009-04-02</title>
    <author>
        <name>Todd</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Cannot mention PhoneGap without mentioning the far more powerful Oil Can:</p>

<p><a href="http://oilcan.jsharkey.org" rel="nofollow">http://oilcan.jsharkey.org</a></p>

<p>Special note: It is fairly trivial to convert the millions of existing GreaseMonkey scripts to Oil Can scripts!</p>]]>
    </content>
    <published>2009-04-02T21:46:40Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:131902</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c131902" />
    <title>Comment from Josiah on 2009-04-02</title>
    <author>
        <name>Josiah</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>I agree that PhoneGap's vision is the way to go - but they are lightyears behind the QuickConnect framework.  I've been working with these frameworks for the past 4 months and there is simply no comparison. QuickConnect is everything PhoneGap should be and more.</p>

<p>Develop apps in QuickConnect and they will port into iPhone, Android, Nokia, Mac, Linux, & Mac Dashboard widget with very little (if any) extra work.  You develop in HTML, Javascript, and CSS.</p>

<p>The author also responds to questions pretty quickly.  I've seen him add new features for people requesting.</p>

<p>@ReadWriteWeb: if you believe that web/hybrid applications are the future - QuickConnect is worth a good hard look.  Thanks for this article. I'm glad to see someone else (especially here) say what I've been trying to say for months.</p>

<p>Download: <a href="http://sourceforge.net/projects/quickconnect/" rel="nofollow">http://sourceforge.net/projects/quickconnect/</a><br />
Blog: <a href="http://tetontech.wordpress.com/" rel="nofollow">http://tetontech.wordpress.com/</a><br />
Wiki: <a href="http://quickconnect.pbwiki.com/" rel="nofollow">http://quickconnect.pbwiki.com/</a><br />
Google Group: <a href="http://groups.google.com/group/quickconnectiPhone?pli=1" rel="nofollow">http://groups.google.com/group/quickconnectiPhone?pli=1</a></p>]]>
    </content>
    <published>2009-04-03T00:17:21Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:131918</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c131918" />
    <title>Comment from Jason Grigsby on 2009-04-02</title>
    <author>
        <name>Jason Grigsby</name>
        <uri>http://cloudfour.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://cloudfour.com">
        <![CDATA[<p>@josiah thanks for the link. I'm definitely going to look at QuickConnect.</p>]]>
    </content>
    <published>2009-04-03T04:16:14Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:132069</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c132069" />
    <title>Comment from homepage on 2009-04-04</title>
    <author>
        <name>homepage</name>
        <uri>http://sthrt.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://sthrt.com">
        <![CDATA[<p>What about dotMobi?</p>]]>
    </content>
    <published>2009-04-04T14:04:46Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:132161</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c132161" />
    <title>Comment from Peter J Cooper on 2009-04-05</title>
    <author>
        <name>Peter J Cooper</name>
        <uri>http://www.coopersydney.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.coopersydney.com">
        <![CDATA[<p>Great to hear about PhoneGap, the need for this is only going to grow. Strategically this will be around for a while, just need to get the community support up front.</p>

<p>Cheers, Peter.</p>]]>
    </content>
    <published>2009-04-06T02:34:45Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:133121</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c133121" />
    <title>Comment from neon on 2009-04-12</title>
    <author>
        <name>neon</name>
        <uri>http://www.drmneon.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.drmneon.com">
        <![CDATA[<p>The been working with these frameworks for the past 4 months and there is simply no comparison. QuickConnect is everything PhoneGap should be and more.<br />
</p>]]>
    </content>
    <published>2009-04-12T19:00:05Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:135032</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c135032" />
    <title>Comment from victor  on 2009-04-24</title>
    <author>
        <name>victor </name>
        <uri>http://www.8kmiles.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.8kmiles.com">
        <![CDATA[<p>Thanks to mobilereflex we are now able to build native applications across multiple devices.native must be the standard for enterprise apps where security, control and max usage of real estate of the pda is key</p>]]>
    </content>
    <published>2009-04-24T08:04:31Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:149923</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c149923" />
    <title>Comment from nusret on 2009-07-31</title>
    <author>
        <name>nusret</name>
        <uri>http://www.yuregininsesi.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.yuregininsesi.com">
        <![CDATA[<p>seslieviniz.com</p>]]>
    </content>
    <published>2009-07-31T10:26:50Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2009://1.14476-comment:156207</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2009://1.14476" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/the_future_of_mobile_web_20_expo.php#c156207" />
    <title>Comment from seks on 2009-09-06</title>
    <author>
        <name>seks</name>
        <uri>http://www.seks.gen.tr</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.seks.gen.tr">
        <![CDATA[<p>I agree that PhoneGap's vision is the way to go - but they are lightyears behind the QuickConnect framework. I've been working with these frameworks for the past 4 months and there is simply no comparison. QuickConnect is everything PhoneGap should be and more.</p>]]>
    </content>
    <published>2009-09-06T21:47:40Z</published>
  </entry>

</feed>