<?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: The Death of the Mobile Website?</title>
	<atom:link href="http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/feed/" rel="self" type="application/rss+xml" />
	<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/</link>
	<description>Inspiration, Experimentation, Innovation</description>
	<lastBuildDate>Mon, 21 Nov 2011 20:30:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Score two for flexible design &#171; Art Beat Me!</title>
		<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/comment-page-1/#comment-388</link>
		<dc:creator>Score two for flexible design &#171; Art Beat Me!</dc:creator>
		<pubDate>Sat, 02 Jan 2010 18:16:39 +0000</pubDate>
		<guid isPermaLink="false">http://lab.vdl2.ca/?p=80#comment-388</guid>
		<description>[...] a comment &#187;  A few months ago I was writing a post on the Pheromone Lab entitled “The Death of the Mobile Website”. The basic point of it was, as the landscape of web-ready devices become less segregated between [...]</description>
		<content:encoded><![CDATA[<p>[...] a comment &raquo;  A few months ago I was writing a post on the Pheromone Lab entitled “The Death of the Mobile Website”. The basic point of it was, as the landscape of web-ready devices become less segregated between [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dwight Vietzke</title>
		<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/comment-page-1/#comment-283</link>
		<dc:creator>Dwight Vietzke</dc:creator>
		<pubDate>Tue, 08 Dec 2009 15:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://lab.vdl2.ca/?p=80#comment-283</guid>
		<description>Hi all,

Pardon, mais je ne suis pas courant en Francais...

I have been working on mobile website software for multilple screen display sizing for some time. I have a project on Google Code, if anyone is interested:

http://code.google.com/p/mobilesiteos/

It works well enough, but does require server scripting (I program in Perl). Anyone knowing of similar projects, please feel free to let me know (dwight_vietzke@yahoo.com).

Great article. I of coarse couldn&#039;t agree with you more about the movement of websites towards &#039;same content for all&#039; as a worthwhile trend. It does however make it difficult to create &#039;exciting&#039; content, when you are concerned about reaching all device types. Pages tend to be simple (not always a bad thing) and you always have the problem of know what capabilities the user&#039;s device can handle, ie: javascript, flash, xHTML as XML, etc.

Standards too are a problem, since it seems like there are almost none at all at times. The newer mobile devices (with near full-featured browsers) are making it easier to present pages across many devices, so it would seem there is hope.

Oddly enough, integrating things like Google Checkout and Adsense code into my software was a challenge as they are both not very &#039;mobile friendly&#039;. That is, you have either code that works for desktops, or code that works in mobile devices but not single source code that works in both. For example, I try to write all pages as xhtml Mobile Profile complaint. But Google code uses attributes and techniques which aren&#039;t MP compliant. Usually for no good reason other than they haven&#039;t bothered to change yet. So it causes you to filter and negotiate around these obstacles.

So for the web developer, making simple pages work for different size devices isn&#039;t the problem as much as it is integrating all the &#039;normal&#039; features code supplied by others that we consider standard for website function.</description>
		<content:encoded><![CDATA[<p>Hi all,</p>
<p>Pardon, mais je ne suis pas courant en Francais&#8230;</p>
<p>I have been working on mobile website software for multilple screen display sizing for some time. I have a project on Google Code, if anyone is interested:</p>
<p><a href="http://code.google.com/p/mobilesiteos/" rel="nofollow">http://code.google.com/p/mobilesiteos/</a></p>
<p>It works well enough, but does require server scripting (I program in Perl). Anyone knowing of similar projects, please feel free to let me know (dwight_vietzke@yahoo.com).</p>
<p>Great article. I of coarse couldn&#8217;t agree with you more about the movement of websites towards &#8216;same content for all&#8217; as a worthwhile trend. It does however make it difficult to create &#8216;exciting&#8217; content, when you are concerned about reaching all device types. Pages tend to be simple (not always a bad thing) and you always have the problem of know what capabilities the user&#8217;s device can handle, ie: javascript, flash, xHTML as XML, etc.</p>
<p>Standards too are a problem, since it seems like there are almost none at all at times. The newer mobile devices (with near full-featured browsers) are making it easier to present pages across many devices, so it would seem there is hope.</p>
<p>Oddly enough, integrating things like Google Checkout and Adsense code into my software was a challenge as they are both not very &#8216;mobile friendly&#8217;. That is, you have either code that works for desktops, or code that works in mobile devices but not single source code that works in both. For example, I try to write all pages as xhtml Mobile Profile complaint. But Google code uses attributes and techniques which aren&#8217;t MP compliant. Usually for no good reason other than they haven&#8217;t bothered to change yet. So it causes you to filter and negotiate around these obstacles.</p>
<p>So for the web developer, making simple pages work for different size devices isn&#8217;t the problem as much as it is integrating all the &#8216;normal&#8217; features code supplied by others that we consider standard for website function.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thinking about trends on the mobile web &#171; Art Beat Me!</title>
		<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/comment-page-1/#comment-15</link>
		<dc:creator>Thinking about trends on the mobile web &#171; Art Beat Me!</dc:creator>
		<pubDate>Sat, 05 Sep 2009 17:42:05 +0000</pubDate>
		<guid isPermaLink="false">http://lab.vdl2.ca/?p=80#comment-15</guid>
		<description>[...] revolutionary yet, but I have started with an article over at the Pheromone lab (my employer) on “The Death of the Mobile Website?” and interface/device [...]</description>
		<content:encoded><![CDATA[<p>[...] revolutionary yet, but I have started with an article over at the Pheromone lab (my employer) on “The Death of the Mobile Website?” and interface/device [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stéphane Deschamps (notabene) 's status on Wednesday, 02-Sep-09 14:10:29 UTC - Identi.ca</title>
		<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/comment-page-1/#comment-13</link>
		<dc:creator>Stéphane Deschamps (notabene) 's status on Wednesday, 02-Sep-09 14:10:29 UTC - Identi.ca</dc:creator>
		<pubDate>Wed, 02 Sep 2009 14:10:38 +0000</pubDate>
		<guid isPermaLink="false">http://lab.vdl2.ca/?p=80#comment-13</guid>
		<description>[...] vachement bien le dernier article de @olivierthereaux http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/ [...]</description>
		<content:encoded><![CDATA[<p>[...] vachement bien le dernier article de @olivierthereaux <a href="http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/" rel="nofollow">http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stéphane Deschamps</title>
		<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/comment-page-1/#comment-12</link>
		<dc:creator>Stéphane Deschamps</dc:creator>
		<pubDate>Wed, 02 Sep 2009 14:08:31 +0000</pubDate>
		<guid isPermaLink="false">http://lab.vdl2.ca/?p=80#comment-12</guid>
		<description>Il y a une troisième voie, à base de versions mobiles des mêmes sites : là c&#039;est moins cher en RD et tout à fait dans la philosophie de la &quot;mobilization&quot;. Voir ce que font plein de sites avec leurs sous-domaines &lt;code&gt;m.*&lt;/code&gt; ; voir aussi l&#039;idée de fixer un cookie sur la base de la demande expresse du client et de là, faire de la micro-adaptation (j&#039;aime bien cette option-là), par exemple chez &lt;a href=&quot;http://www.mezzoblue.com/&quot; rel=&quot;nofollow&quot;&gt;Mezzoblue&lt;/a&gt;.

En tout cas merci pour cet article. Food for thought (tiens pas de &lt;code&gt;span lang&lt;/code&gt; dans le XHTML autorisé, dommage).</description>
		<content:encoded><![CDATA[<p>Il y a une troisième voie, à base de versions mobiles des mêmes sites : là c&#8217;est moins cher en RD et tout à fait dans la philosophie de la &#8220;mobilization&#8221;. Voir ce que font plein de sites avec leurs sous-domaines <code>m.*</code> ; voir aussi l&#8217;idée de fixer un cookie sur la base de la demande expresse du client et de là, faire de la micro-adaptation (j&#8217;aime bien cette option-là), par exemple chez <a href="http://www.mezzoblue.com/" rel="nofollow">Mezzoblue</a>.</p>
<p>En tout cas merci pour cet article. Food for thought (tiens pas de <code>span lang</code> dans le XHTML autorisé, dommage).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier Théreaux</title>
		<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/comment-page-1/#comment-7</link>
		<dc:creator>Olivier Théreaux</dc:creator>
		<pubDate>Mon, 31 Aug 2009 15:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://lab.vdl2.ca/?p=80#comment-7</guid>
		<description>Coût en UX &lt;strong&gt;et&lt;/strong&gt; en développement. Les librairies (et langages) de développement sont complètement différents d&#039;une plate-forme à une autre: le NY Times, par exemple, a dû doubler le temps de développement pour donner exactement la même expérience pour leur app sur Android et iPhone.

Quant aux services iMode et assimilés au Japon, il semble qu&#039;ils survivent bien pour certains services (musique, ringtones etc) mais la tendance dans l&#039;utilisation des navigateurs et la vente énorme de terminaux puissants devrait en sonner le glas dans les 2-3 années à venir.</description>
		<content:encoded><![CDATA[<p>Coût en UX <strong>et</strong> en développement. Les librairies (et langages) de développement sont complètement différents d&#8217;une plate-forme à une autre: le NY Times, par exemple, a dû doubler le temps de développement pour donner exactement la même expérience pour leur app sur Android et iPhone.</p>
<p>Quant aux services iMode et assimilés au Japon, il semble qu&#8217;ils survivent bien pour certains services (musique, ringtones etc) mais la tendance dans l&#8217;utilisation des navigateurs et la vente énorme de terminaux puissants devrait en sonner le glas dans les 2-3 années à venir.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: belanger</title>
		<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/comment-page-1/#comment-6</link>
		<dc:creator>belanger</dc:creator>
		<pubDate>Sat, 29 Aug 2009 03:10:02 +0000</pubDate>
		<guid isPermaLink="false">http://lab.vdl2.ca/?p=80#comment-6</guid>
		<description>Intéressant. Il y a risque de balkanisation, mais en même temps, le développement en mobile iphone vs blackberry exige des expertises en UX similaires et les contraintes Apple et BB sont très grandes. C&#039;est donc plutôt un coût en UX qu&#039;en développement. 

Question: au Japon, les WAP et autres adaptations mobiles, c&#039;est terminé?</description>
		<content:encoded><![CDATA[<p>Intéressant. Il y a risque de balkanisation, mais en même temps, le développement en mobile iphone vs blackberry exige des expertises en UX similaires et les contraintes Apple et BB sont très grandes. C&#8217;est donc plutôt un coût en UX qu&#8217;en développement. </p>
<p>Question: au Japon, les WAP et autres adaptations mobiles, c&#8217;est terminé?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: olivier Thereaux (olivierthereaux) 's status on Thursday, 27-Aug-09 14:04:11 UTC - Identi.ca</title>
		<link>http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/comment-page-1/#comment-4</link>
		<dc:creator>olivier Thereaux (olivierthereaux) 's status on Thursday, 27-Aug-09 14:04:11 UTC - Identi.ca</dc:creator>
		<pubDate>Thu, 27 Aug 2009 14:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://lab.vdl2.ca/?p=80#comment-4</guid>
		<description>[...] Freshly posted: &quot;The Death of the Mobile Website?&quot; http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/ [...]</description>
		<content:encoded><![CDATA[<p>[...] Freshly posted: &quot;The Death of the Mobile Website?&quot; <a href="http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/" rel="nofollow">http://lab.pheromone.ca/2009/08/26/the-death-of-the-mobile-website/</a> [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

