<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Firefox will be eat&#8217;n alive by Opera and the iPhone</title>
	<atom:link href="http://blog.bima.co.uk/mozilla-on-mobile-web/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.bima.co.uk/mozilla-on-mobile-web/</link>
	<description>BIMA's weblog</description>
	<pubDate>Thu, 11 Mar 2010 16:44:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Paul Walsh</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-234</link>
		<dc:creator>Paul Walsh</dc:creator>
		<pubDate>Wed, 30 May 2007 14:36:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-234</guid>
		<description>Yikes! It amazes me how mobile web can draw you into making huge conversational comments.</description>
		<content:encoded><![CDATA[<p>Yikes! It amazes me how mobile web can draw you into making huge conversational comments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Walsh</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-233</link>
		<dc:creator>Paul Walsh</dc:creator>
		<pubDate>Wed, 30 May 2007 14:36:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-233</guid>
		<description>Brendan - thanks for the clarification and I’m sorry I was a little harsh with my commentary! Friends  I’m delighted we had this discussion! 
Regarding your comment about the W3C MWI BPs (which I helped to write and now we’re going off topic), where do you think they lack clarity/feasibility/implementability?
My take is that they’re for traditional desktop developers to help them better understand how to build sites that work on desktop computers as well as mobile devices. They’re not specifically for mobile application developers that you’d expect to find on WURFL.
Further to this, I see the MWI as one actor on stage, other actors include browser vendors who need to standardise how they render content, handset vendors who need to improve the input methods and restrictive technology and operators who need to reduce tariffs and not hide the XHTML(blah) browser…
So, I see MWI as a stepping stone in the right direction. It’s a bit like starting off with WCAG in 1995 with a light weight document with guidelines - i.e. much easier to digest and easier to implement than the slightly more bloated document in 1999 and the even more bloated WCAG 2.0 document currently being written.
Also, the MWI has content adaptation, operators, vendors, search engines, content providers and standards compliance specialists involved - that’s just about everyone. OMA is involved and I own the relationship between GSMA and W3C (which is non-existent as the GSMA never got involved). So I’m not sure it addresses only the needs of its members. Naturally this is a perception that may need to be addressed…</description>
		<content:encoded><![CDATA[<p>Brendan - thanks for the clarification and I’m sorry I was a little harsh with my commentary! Friends  I’m delighted we had this discussion!<br />
Regarding your comment about the W3C MWI BPs (which I helped to write and now we’re going off topic), where do you think they lack clarity/feasibility/implementability?<br />
My take is that they’re for traditional desktop developers to help them better understand how to build sites that work on desktop computers as well as mobile devices. They’re not specifically for mobile application developers that you’d expect to find on WURFL.<br />
Further to this, I see the MWI as one actor on stage, other actors include browser vendors who need to standardise how they render content, handset vendors who need to improve the input methods and restrictive technology and operators who need to reduce tariffs and not hide the XHTML(blah) browser…<br />
So, I see MWI as a stepping stone in the right direction. It’s a bit like starting off with WCAG in 1995 with a light weight document with guidelines - i.e. much easier to digest and easier to implement than the slightly more bloated document in 1999 and the even more bloated WCAG 2.0 document currently being written.<br />
Also, the MWI has content adaptation, operators, vendors, search engines, content providers and standards compliance specialists involved - that’s just about everyone. OMA is involved and I own the relationship between GSMA and W3C (which is non-existent as the GSMA never got involved). So I’m not sure it addresses only the needs of its members. Naturally this is a perception that may need to be addressed…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Jacobson</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-232</link>
		<dc:creator>Paul Jacobson</dc:creator>
		<pubDate>Wed, 30 May 2007 14:35:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-232</guid>
		<description>Well, he’s passionate about his stuff …</description>
		<content:encoded><![CDATA[<p>Well, he’s passionate about his stuff …</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-231</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Wed, 30 May 2007 14:34:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-231</guid>
		<description>Wow, typos. Need to get some coffee. Obviously I meant “member-company-driven”, not “memory-company-driven”. And “de-facto standards”. Yeesh. I’ll pipe down now for a while ;-).
/be</description>
		<content:encoded><![CDATA[<p>Wow, typos. Need to get some coffee. Obviously I meant “member-company-driven”, not “memory-company-driven”. And “de-facto standards”. Yeesh. I’ll pipe down now for a while ;-).<br />
/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-230</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Wed, 30 May 2007 14:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-230</guid>
		<description>I am sure that Chaals and Opera would view my comments with alarm, and as I wrote elsewhere, Mozilla and Opera are working together on several fronts. We don’t compete as much as some of the spreadfirefox vs. spreadopera fanboys make out.
But my point remains: mobile is hard compared to desktop. Hence Flash Lite, WICD, SVG and many other would-be or de-factor standards that already have fragmented the mobile and non-mobile webs. I want to heal the rift, but I don’t buy the w3c memory-company-driven approach. It leaves out developers; it tends to make more and bigger standards than are strictly necessary. Just look at all the defunct ones!
Mozilla is not forsaking mobile, but we do not plan to wedge Firefox in full on phat phones. We hope to use leverage, work smarter. Opera Mini is smart (so was danger.com), but again the proxy hosting is a problem.
/be</description>
		<content:encoded><![CDATA[<p>I am sure that Chaals and Opera would view my comments with alarm, and as I wrote elsewhere, Mozilla and Opera are working together on several fronts. We don’t compete as much as some of the spreadfirefox vs. spreadopera fanboys make out.<br />
But my point remains: mobile is hard compared to desktop. Hence Flash Lite, WICD, SVG and many other would-be or de-factor standards that already have fragmented the mobile and non-mobile webs. I want to heal the rift, but I don’t buy the w3c memory-company-driven approach. It leaves out developers; it tends to make more and bigger standards than are strictly necessary. Just look at all the defunct ones!<br />
Mozilla is not forsaking mobile, but we do not plan to wedge Firefox in full on phat phones. We hope to use leverage, work smarter. Opera Mini is smart (so was danger.com), but again the proxy hosting is a problem.<br />
/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-229</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Wed, 30 May 2007 14:33:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-229</guid>
		<description>Paul Walsh: sorry, idiots was harsh. I was reacting mainly to trolls on operawatch.com.
/be</description>
		<content:encoded><![CDATA[<p>Paul Walsh: sorry, idiots was harsh. I was reacting mainly to trolls on operawatch.com.<br />
/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Walsh</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-228</link>
		<dc:creator>Paul Walsh</dc:creator>
		<pubDate>Wed, 30 May 2007 14:32:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-228</guid>
		<description>Brendan - reading your comment again on Dan’s blog, who are the idiots to which you refer?</description>
		<content:encoded><![CDATA[<p>Brendan - reading your comment again on Dan’s blog, who are the idiots to which you refer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Walsh</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-227</link>
		<dc:creator>Paul Walsh</dc:creator>
		<pubDate>Wed, 30 May 2007 14:31:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-227</guid>
		<description>Brendan - “I’m curious why you think Firefox can compete with Opera Mini, though”
In short, you’re both browser vendors, so you’re competitors. I’m not being sarcastic of course, just articulating my thoughts. That said, with Opera’s market share at less than 2% on the desktop, you’re hardly competing and with Mozilla’s share of mobile at less than 1% you’re hardly competing there either.
The way in which you serve content is irrelevant to users. Although, if you can improve on the bastardisation that Opera does currently to improve the user experience (which they need to do and do well), I’m all ears.
Ok, so users aren’t going to download their choice of browser on mobiles for a long time to come. However, Opera mini is recognised within the mobile industry as the most compelling browser for mobile devices today.
Mozilla revolutionised the desktop browsing experience whilst putting the shivers down Microsoft’s back (which I applaud). I wait and hope you can do the same on mobile…
I’ve received numerous emails from companies showing their support for my post. I can only ask that they post their comments to the blog and not be afraid to have an opinion in public. Charles at Opera posted a comment on another blog of mine so I can say publicly that Opera share my thoughts. Ok, so they’re not great on the desktop but they’re doing something right on mobile - where the vast majority of new users are going to come from in the future.
BTW, as one of the very first employees of AOL in Europe in 1995 coupled with decent mobile experience, I’d like to think I’m not at the end of the spectrum you place Dan in (re your comment on his blog). I consider myself impartial.</description>
		<content:encoded><![CDATA[<p>Brendan - “I’m curious why you think Firefox can compete with Opera Mini, though”<br />
In short, you’re both browser vendors, so you’re competitors. I’m not being sarcastic of course, just articulating my thoughts. That said, with Opera’s market share at less than 2% on the desktop, you’re hardly competing and with Mozilla’s share of mobile at less than 1% you’re hardly competing there either.<br />
The way in which you serve content is irrelevant to users. Although, if you can improve on the bastardisation that Opera does currently to improve the user experience (which they need to do and do well), I’m all ears.<br />
Ok, so users aren’t going to download their choice of browser on mobiles for a long time to come. However, Opera mini is recognised within the mobile industry as the most compelling browser for mobile devices today.<br />
Mozilla revolutionised the desktop browsing experience whilst putting the shivers down Microsoft’s back (which I applaud). I wait and hope you can do the same on mobile…<br />
I’ve received numerous emails from companies showing their support for my post. I can only ask that they post their comments to the blog and not be afraid to have an opinion in public. Charles at Opera posted a comment on another blog of mine so I can say publicly that Opera share my thoughts. Ok, so they’re not great on the desktop but they’re doing something right on mobile - where the vast majority of new users are going to come from in the future.<br />
BTW, as one of the very first employees of AOL in Europe in 1995 coupled with decent mobile experience, I’d like to think I’m not at the end of the spectrum you place Dan in (re your comment on his blog). I consider myself impartial.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-226</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Wed, 30 May 2007 14:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-226</guid>
		<description>Paul Walsh: see Dan’s blog for some fresh comments from him to which I reply. We are not as far off from one another as some rabid bloggers want to represent.
I’m curious why you think Firefox can compete with Opera Mini, though — Mini uses a proxy to transcode the web to fit in a very small J2ME client. It’s a cool approach, used for years by danger.com too. We’ve found it a hard sell to carriers, who don’t want to run proxy farms (but Opera runs the farm, I gather). Still, it’s not as if Firefox can be easily hollowed out into a proxy transcoder and a little J2ME client. Could be done; lot of work. Unclear whether Mozilla could host the proxy for carriers.
Tom Rafferty: I attack misquoting of my words, yes. Get over it.
Paul Littlebury: “How they use those handsets is down to the quality of the software on the phone, the size/quality of the screen, and the quality of websites (their ability to display on different devices).”
Don’t forget input device bandwidth/pain — I know some fast Blackberry thumb typists, but they still go faster on desktops. My point at the panel was that the form factors and interaction designs differ enough between mobile and desktop that usage patterns differ significantly — and should.
This is not to say web content formats should differ, of course. The issue that sparked this was Dan’s asking about when WICD would be supported in Firefox. I was skeptical of the value to Firefox’s almost entirely desktop user base.
/be</description>
		<content:encoded><![CDATA[<p>Paul Walsh: see Dan’s blog for some fresh comments from him to which I reply. We are not as far off from one another as some rabid bloggers want to represent.<br />
I’m curious why you think Firefox can compete with Opera Mini, though — Mini uses a proxy to transcode the web to fit in a very small J2ME client. It’s a cool approach, used for years by danger.com too. We’ve found it a hard sell to carriers, who don’t want to run proxy farms (but Opera runs the farm, I gather). Still, it’s not as if Firefox can be easily hollowed out into a proxy transcoder and a little J2ME client. Could be done; lot of work. Unclear whether Mozilla could host the proxy for carriers.<br />
Tom Rafferty: I attack misquoting of my words, yes. Get over it.<br />
Paul Littlebury: “How they use those handsets is down to the quality of the software on the phone, the size/quality of the screen, and the quality of websites (their ability to display on different devices).”<br />
Don’t forget input device bandwidth/pain — I know some fast Blackberry thumb typists, but they still go faster on desktops. My point at the panel was that the form factors and interaction designs differ enough between mobile and desktop that usage patterns differ significantly — and should.<br />
This is not to say web content formats should differ, of course. The issue that sparked this was Dan’s asking about when WICD would be supported in Firefox. I was skeptical of the value to Firefox’s almost entirely desktop user base.<br />
/be</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Littlebury</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-225</link>
		<dc:creator>Paul Littlebury</dc:creator>
		<pubDate>Wed, 30 May 2007 14:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-225</guid>
		<description>Well said Paul!  Making assumptions on the user is a precarious position.  I am finding it frankly bizarre of the prevalent opinions on industry blogs, that browsing the web on a mobile is not something the general public want.  Where are they getting their statistics from?  You cannot judge public opinion from asking them at this point in time if they would surf the web on their mobile.  As with any technology, the public (I include myself here) would access the web on any device, as long as it’s appropriate and reasonably easy to use, and not porhibitively expensive.  Obviously, on a traditionally sized screen, this is not practical.  If someone asked me now, with my current handset, if I would surf the web on my phone, I would say no.  But that is not a valid measure, as I would browse the web if I had a phone with a larger screen.  And have done so, as last hadnset was Nokia e61, which was a pleasure to use for web surfing.
With the surge of the Blackberry, and similar devices, surfing the web on your mobile with 3g speed is a reasonably pleasant experience.  Its all about hardware and software meeting usability requirements - not a new idea, part of the standard software design principles.  The user has been left at the bottom of the requirements pile the last few years.  In my capacity in test management, I have noticed a downturn in this area.  There needs to be a re-focus on the user experience within the technology community, rather than imposing our judgements and second-guessing what the public perception of technology is.  Give people a toy, and they will play.  How long they will play is down to the quality of the device, phone software, and website quality.
It wasnt so long ago people were very sceptical of the idea of being able to check your  emails on mobiles.  Or further back, the scepticism of mobile phone themeselves.  To deny the possibility of popularity mobile web browsing is nonsense, as it is an inevitable conclusion, and in keeping with the progressives moves in web standards.  We are reaching a point where what device you are accessing the web from, shouldnt matter.  This is not user problem, it is an industry problem, an industry which is used to dictating directions, and now discovering that maybe they could have been wrong in their market assumptions. 
The public will always fall for the hard-sell mobile marketing and stylish handsets.  How they use those handsets is down to the quality of the software on the phone, the size/quality of the screen, and the quality of websites (their ability to display on different devices).</description>
		<content:encoded><![CDATA[<p>Well said Paul!  Making assumptions on the user is a precarious position.  I am finding it frankly bizarre of the prevalent opinions on industry blogs, that browsing the web on a mobile is not something the general public want.  Where are they getting their statistics from?  You cannot judge public opinion from asking them at this point in time if they would surf the web on their mobile.  As with any technology, the public (I include myself here) would access the web on any device, as long as it’s appropriate and reasonably easy to use, and not porhibitively expensive.  Obviously, on a traditionally sized screen, this is not practical.  If someone asked me now, with my current handset, if I would surf the web on my phone, I would say no.  But that is not a valid measure, as I would browse the web if I had a phone with a larger screen.  And have done so, as last hadnset was Nokia e61, which was a pleasure to use for web surfing.<br />
With the surge of the Blackberry, and similar devices, surfing the web on your mobile with 3g speed is a reasonably pleasant experience.  Its all about hardware and software meeting usability requirements - not a new idea, part of the standard software design principles.  The user has been left at the bottom of the requirements pile the last few years.  In my capacity in test management, I have noticed a downturn in this area.  There needs to be a re-focus on the user experience within the technology community, rather than imposing our judgements and second-guessing what the public perception of technology is.  Give people a toy, and they will play.  How long they will play is down to the quality of the device, phone software, and website quality.<br />
It wasnt so long ago people were very sceptical of the idea of being able to check your  emails on mobiles.  Or further back, the scepticism of mobile phone themeselves.  To deny the possibility of popularity mobile web browsing is nonsense, as it is an inevitable conclusion, and in keeping with the progressives moves in web standards.  We are reaching a point where what device you are accessing the web from, shouldnt matter.  This is not user problem, it is an industry problem, an industry which is used to dictating directions, and now discovering that maybe they could have been wrong in their market assumptions.<br />
The public will always fall for the hard-sell mobile marketing and stylish handsets.  How they use those handsets is down to the quality of the software on the phone, the size/quality of the screen, and the quality of websites (their ability to display on different devices).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom Raftery</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-224</link>
		<dc:creator>Tom Raftery</dc:creator>
		<pubDate>Wed, 30 May 2007 14:27:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-224</guid>
		<description>&lt;blockquote&gt;The mobile web, assuming it’s just the web we all know and love, will succeed *in spite of*, not *because of*, the kind of special-pleading and inaccurate quoting you are practicing.
&lt;/blockquote&gt;
Wow! In one sentence you have suceeded in destroying the extremely positive impression I had of you!
First off, why do you assume that the mobile web will be the “web we all know and love” - that is a very shortsighted view and secondly, you then attack  the person who wrote this article.</description>
		<content:encoded><![CDATA[<blockquote><p>The mobile web, assuming it’s just the web we all know and love, will succeed *in spite of*, not *because of*, the kind of special-pleading and inaccurate quoting you are practicing.
</p></blockquote>
<p>Wow! In one sentence you have suceeded in destroying the extremely positive impression I had of you!<br />
First off, why do you assume that the mobile web will be the “web we all know and love” - that is a very shortsighted view and secondly, you then attack  the person who wrote this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Walsh</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-223</link>
		<dc:creator>Paul Walsh</dc:creator>
		<pubDate>Wed, 30 May 2007 14:25:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-223</guid>
		<description>Hi Brendan – thanks for stopping by to provide your account of the conversation. I must admit that I was surprised to hear Mozilla would make such comments. Although, it wouldn’t have been t_h_a_t surprising given the comments I hear from equally impressive organisations at seminars that I’ve presented at. They simply have a different view to me. 
I was happy to quote Dan of all people. If you know him, you’ll also know that he’s an extremely well respected member of the mobile community with a great vision of what the Web will probably look like on mobile. He’s founder of Mobile Monday, founder of Mobile 2.0, Chair of the W3C MWI BP group and importantly, a senior strategist at Voda Group. So, he doesn’t walk on water and some opinions aren’t more equal than others, but I trust his unbiased commentating. I also believe in soliciting the opinion of people I talk about – hence why I asked Ian Hayward (good friend of mine and known to you) to kindly ask if you would stop by. I’m delighted you did!
I agree and disagree with your view. In fact, I think too many people are making assumptions about what users want when it comes to the mobile web. The answer is, none of us know for sure. If we were talking about people who travel from Slough to London, I’d expect them to use a mobile for twitter. However, as technology improves at such an accelerated rate along with other stake holders making improvements (of which MWI is just one), I can only see more of the desktop coming to mobile – at least that’s what Nokia and Apple are saying too.
Some users do sit, think, surf, type, edit, review, and post. Moreover, I see this trend moving up. Perhaps you’re basing your opinion on current US trends? The US market is way behind Europe where mobile data consumption is concerned. We will all fall behind developing countries in the near future. 
I’m pretty confident that Firefox could be a serious competitor for Opera mini. Firefox is my favourite browser – heck, my company has an extension that demonstrates how future search could work. So, I’m behind Mozilla 100% and I hope it realises the full potential of delivering a proper Web experience on mobile devices.</description>
		<content:encoded><![CDATA[<p>Hi Brendan – thanks for stopping by to provide your account of the conversation. I must admit that I was surprised to hear Mozilla would make such comments. Although, it wouldn’t have been t_h_a_t surprising given the comments I hear from equally impressive organisations at seminars that I’ve presented at. They simply have a different view to me.<br />
I was happy to quote Dan of all people. If you know him, you’ll also know that he’s an extremely well respected member of the mobile community with a great vision of what the Web will probably look like on mobile. He’s founder of Mobile Monday, founder of Mobile 2.0, Chair of the W3C MWI BP group and importantly, a senior strategist at Voda Group. So, he doesn’t walk on water and some opinions aren’t more equal than others, but I trust his unbiased commentating. I also believe in soliciting the opinion of people I talk about – hence why I asked Ian Hayward (good friend of mine and known to you) to kindly ask if you would stop by. I’m delighted you did!<br />
I agree and disagree with your view. In fact, I think too many people are making assumptions about what users want when it comes to the mobile web. The answer is, none of us know for sure. If we were talking about people who travel from Slough to London, I’d expect them to use a mobile for twitter. However, as technology improves at such an accelerated rate along with other stake holders making improvements (of which MWI is just one), I can only see more of the desktop coming to mobile – at least that’s what Nokia and Apple are saying too.<br />
Some users do sit, think, surf, type, edit, review, and post. Moreover, I see this trend moving up. Perhaps you’re basing your opinion on current US trends? The US market is way behind Europe where mobile data consumption is concerned. We will all fall behind developing countries in the near future.<br />
I’m pretty confident that Firefox could be a serious competitor for Opera mini. Firefox is my favourite browser – heck, my company has an extension that demonstrates how future search could work. So, I’m behind Mozilla 100% and I hope it realises the full potential of delivering a proper Web experience on mobile devices.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brendan Eich</title>
		<link>http://blog.bima.co.uk/mozilla-on-mobile-web/comment-page-1/#comment-222</link>
		<dc:creator>Brendan Eich</dc:creator>
		<pubDate>Wed, 30 May 2007 14:24:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.bima.co.uk/2007/04/14/mozilla-on-mobile-web/#comment-222</guid>
		<description>Dan paraphrased me, he didn’t quote me word for word. You parrot him at your peril.
I have a fat smart phone. I browse the web on it. Mozilla has the minimo project, which has tens of thousands of users. They do likwise. So what?
My point is simple: most phone users do not sit, think, surf, type, edit, review, and post. They find maps, pizza, twitter updates, etc. etc.
The phone is not the desktop. Doesn’t mean it should not support web standards. Does mean desktop browsers may not give a damn about Dan’s w3c pay-for-play compound document format stuff, which is far from the holy writ blogs like this make out.
The mobile web, assuming it’s just the web we all know and love, will succeed *in spite of*, not *because of*, the kind of special-pleading and inaccurate quoting you are practicing.
/be</description>
		<content:encoded><![CDATA[<p>Dan paraphrased me, he didn’t quote me word for word. You parrot him at your peril.<br />
I have a fat smart phone. I browse the web on it. Mozilla has the minimo project, which has tens of thousands of users. They do likwise. So what?<br />
My point is simple: most phone users do not sit, think, surf, type, edit, review, and post. They find maps, pizza, twitter updates, etc. etc.<br />
The phone is not the desktop. Doesn’t mean it should not support web standards. Does mean desktop browsers may not give a damn about Dan’s w3c pay-for-play compound document format stuff, which is far from the holy writ blogs like this make out.<br />
The mobile web, assuming it’s just the web we all know and love, will succeed *in spite of*, not *because of*, the kind of special-pleading and inaccurate quoting you are practicing.<br />
/be</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.335 seconds -->
